Juan,

On the task bar, you may see a "lens" to search.
Click on it, then type this:
cmd.exe

A small window will appear.
In that window, just type:
date

It will ask you to enter the desired date.

You can close the window after.

I will wait for your answer

Alain

Hi Joachim,

You are right As long as we stay away from internet with our music PC, we should be protected from these automatic updates

Regards,

Alain

I just read the link you provide. I am unsure about the privacy and what lies behind MS "showed intentions" for the moment. That is why I prefer to wait for a time and see what others will say about standard Windows 10 before jumping into it for good with my music PC and my all purpose PC... Even it I decide to go with it, I still have backups of my previous Windows versions (Windows 7 and Windows - just in case.

Alain

Hi Juan,

From what I understand now, you changed the date in the BIOS and Windows was in Min OS when you booted after ? It could very well be that Windows is unable to verify the system date through that hypothetical file that I assume to exist. But like you say, we will know this when October 1st arrives This may explain why the date change in BIOS worked for you

Maybe if you go back in Normal OS mode, you will have your answer ? Then, going back to Min OS and then changing the date again in BIOS, all will work like the first time ?

Even so, I would suggest to use the "date" command under the command line - that in Normal OS mode. This will ensure that the changing to the latest date will not occur. Normal OS would seem to be a stronger way, but I could be wrong of course...

Regards,

Alain

Hi Peter,

I am sorry if my answer was implying a different mechanism between Min OS and Normal OS. I only was curious to see if I would also see the ending message by going back into Normal OS. It was not a coincidence.

So to your question: I am not saying that the date would only be reset by Windows in Normal OS mode. I was not aware that my answer could imply this conclusion. I was not really testing for this.

IOW: I have always preferred to do some stuff in Normal OS mode.

All I can say is that one day or the other, one would decide to go back in Normal OS. That is why all my attempts were done in Normal OS.

After discovering that the "date" program (in command mode) was allowing the date to change and be kept as is by Windows 10, I rebooted many times, either after a shutdown or through many restarts. I also went back and forth between Normal OS and MinOS a few times, to be sure that all was stable (date not changing again).
....

I can only assume that Windows has a limited way of knowing what the real date/time is:
- By connecting to a server on the internet (nntp)
- By checking with the BIOS
- By having a limited reference through some internal file that it updates throughout a session.

Knowing that we are not connected to internet (...), we can assume that Windows frame of reference can only be from the BIOS and a reference file that Windows controls.

If I put a later date in the BIOS, I doubt that Windows can really validate it without the internet.

But if I put an earlier date in the BIOS, I suppose that Windows can validate it (and discard it) (still without the internet).

All of what I wrote is speculation. I don't know how it is implemented, but if I was to validate a date that was showed to me, the only way I can imagine a limited validation would be through some kind of a reference file I would have to compare.

?

Regards,

Alain

Hi Michel,

Good news I hope it will work that way for a long time ! I don'T know why Windows does not necessarily accept the date and time from the BIOS, but at least we have the "date" program that works

Regards,

Alain

Hi Juan

I am not sure of your question, but I will try to suggest a possible answer...

When my attempts through BIOS did not work, I supposed there was some information hidden somewhere, read (an written) by the OS. For example, since today is Septermber 20th, 2015, the OS would write this in a file. Even if I fool around with the date in BIOS, the OS will determine by reading that file that it can't be earlier than this. So it would restore the latest recorded date.

This is a simplistic attempt to explain why it was not accepting the BIOS change of date.

On the other hand, why did it work when I used the "date" program from the command line ? A bug ? Some kind of workaround ? Could be. But why did it work for others through BIOS, while not for me... If I go on with my attempt to explain, I would guess that the "date" program erases the previous hidden information, resetting it to the date I entered...

With tens of millions lines of code in the OS, depending on how each one installed Windows 10, the explanation lies somewhere...

I am still surprised it worked... For the moment, all seem to hold...

Regards,

Alain

Hi David,

The reason why you do not see the message is because you are in Minimized OS... I checked yesterday by going back in Normal OS and then I saw the message.

My Music PC is not connected to the internet neither and the only time I do is when there is a real need for it...

Regards,

Alain

Edit: Now that I am back in 2013, I even feel a little younger

I did a test just minutes ago. Connected a screen, keyboard and mouse to my music PC, that is not connected to Internet. Have Win 10 pro x64, build 10074.

First I tried changing to date through BIOS (UEFI). The date was holding, but as soon as I was booting into Windows, it was reverted to todays's date. I did this attempt 3 times. Not working.

Then I accessed the "date" from the cmd.exe icon I created from Peter's suggestion (that was suggested some months ago).
Typing:
date
Then entering today's date, but in 2013, it worked.

Now my system is showing 2013-09-19.

I have made a shutdown, then booted a few times. It is keeping the date (2013-09-19).

I will check for a few days to see if it holds and report back.

There seems to be many different behaviors depending on factors that I do not know.

My Windows 10 installation was done in the beginning of July, from Windows 8 plain vanilla. I did not ask to "scr*p" Windows 8, but started from it. I can't say if that explains why everything is going fine here, but I am happy with the results. Of course I have removed all references to Windows 8 ("old files") with the disk cleaning MS application.

Alain

This is still something I would like to apply to my audio PC, since I believe that correcting problems right at the source may eliminate the need to apply "band aids" further down the chain...

Regards,

Alain

I do understand the the multiplier seems too high, but I fail to understand how it varies depending upon my usage of the main volume at the time I ask for the track normalization...

For example:
- Main volume is at -6. I play the track normalized and it shows +6 in the normalization window.
- Main volume is at 0. I play the track normalized and it shows +0 in the normalization window.

I erase the XXAnalysis before each adjustment to ensure that the program redo its normalization.

But if my choice of album to start the comparison in the Settings for Volume Normalization is too low, I suppose that this also may bring some problems ? If so, should I put an album that is louder to begin with ?

Thanks again.

Alain
PS: It is not really a problem for me, since I have been using Normalization Volume for the last 2 weeks only. I have to admit I like the concept

Peter,

Well I finally managed to normalize the whole album like you suggested (Album normalization) and all is fine, as long as I do not use the "Track normalization" (but that was expected).

I noticed what you mean by +6db with the 4th track. To test something, I put the main volume at 0db instead prior to track normalization: it works now.

So it seems that there is an interaction with the main volume at the moment the normalization is calculated and saved in the XXAnalysis.dat file ? I must have been doing it all wrong...

The reason why I use "track" instead of "album" is that I do not  listen often to a whole album. 

Regards,

Alain

Hi Peter,

Thanks. I will digesst your answer and will report back. I am not even sure what the "Library area" is, since there are many aspects of XXHE (mostly concerning Galleries and such) that I do not use...

Alain

Hi Peter,

This morning I was listening to an album that I haven't listened to for a long time.

All of my music is in wav format and I usually do not use Normalized Volume. That changed a few weeks ago and I appreciate its usage now.

I am actually using Windows 10 build 10074 with only XXHighEnd 2.02 on it. Plain vanilla. No connection to the internet.

The album is "The Corrs" entitled "Forgiven Not Forgotten" and the song is "Along With The Girls" (the 4th song on the album). It is a very short song, lasting 49 seconds.

I am using Minimize OS as I do all the time. It has been working fine with all I have been listening to until that song.

The previous songs were playing fine, but when this specific one started, all I heard was a series of "tick" of a certain amplitude that had me jump on the mute button of my preamp. It does this in "unattended" and "attended".

If I try the same but with "Album" instead of "Track" (still under NV) nothing happens - the song does not play. All I can see (in attended mode) is that the leftmost yellow light shows one of the CPU cores is working on it, but it does not go further. When after a minute I press Stop then a window message appears, saying "The thread has been abandoned" (this is a translation from French).

Without NV on, the song plays fine.

The behavior is that same with Normal OS (tried attended only). 

I can send you the song in question if it can be of some help. If required, I could also send some pics of my settings.

I have included the XXAnalysis.dat file with this post.

Regards,

Alain

Hi Joachim,

Thanks for opening the way to many of us From what I read about Windows 10, there still seems to be obscure aspects where some questions are still present.

The fact that the Windows update was not in the plans for Win10 is concerning and the fact that the upgrade is free adds mystery (for me). For years now I do not have my audio PC connected on the internet and I believe that many of us have it the same way. I wonder though how Windows will react when updates cannot be done. There is supposed to be a program that can be downloaded to help regain some control on the updates, but the fact that they have removed this control initially is strange...

It seems to me that the more we advance in time, the less control we have over the OS. I am not sure if I am putting this with the right words...

Alain