Windows 10 build 10074 expiration

[PeterSt]

Hey all,

I think a link to this page has been posted previously, but today it looks more "complete" :

http://www.pagestart.com/win10tpbuildexp041215.html

There is no doubt in my mind that it will really work out like that. So ... time to come up with a version for ...
well ... at this moment still that poor 10240.

3 weeks left for Microsoft to come up with something better, but I don't think it is going to happen within this time. Anyway, before October 1 you will have an XXHighEnd version which will work on the official version of that time.

And oh, when you open a command prompt (cmd) (when on build 10074) and in there type
winver [enter]
you will see something like you see below.

Regards,
Peter

[christoffe]

Found this:

http://www.askvg.com/new-update-build-of-windows-10-technical-preview-now-available-for-download/

[PeterSt]

Hi Joachim,

Yes. But see the page I linked too - that is again not an official version and it will expire as well (but in 2016).

Thank you ...
Peter

[christoffe]

Hi Joachim,

Yes. But see the page I linked too - that is again not an official version and it will expire as well (but in 2016).

Thank you ...
Peter

Hi Peter,

the link I gave is about build 10532, and that is an update for build 10240. Hope this build 10532 is better than .... .

Joachim

[PeterSt]

10525 looked the same to me as 10532. What's in a name ... ehm, number.

Regards,
Peter

[PeterSt]

This is how this f*'ing sh*t works :

10532 is also an Insider Preview. That too will expire (July 15, 2016). So as soon as you upgrade your official(ly released) 10240 with such a preview, it's subject to expiration again.
This expiration can only be undone by means of upgrading to an official build.
Or to downgrade to the latest official Build (10240 as how are things today).

On the other hand, when you keep on upgrading with newer Insider Preview versions, the expiration date will be further and further in the future (well, it will always be about one year).

Sh*tty Spider Web, it is.

Peter

[Scroobius]

Anyway, before October 1 you will have an XXHighEnd version which will work on the official version of that time.

Hey Peter - does that mean that it will *work* with W10 or does it mean that it will work AND sound good with the then latest W10?

Paul

[Robert]

Well Peter, you could just do away with Windows altogether and design your own dedicated, integrated Xxhighend and OS audio playback package with a NOS add on for those who need it.

This integrated package can then all be run in Ram by anyone who pays!!!

I realise this is lot's off effort on your part and you are multi tasking in lots of different areas already.

Recognising that W10 is supposed to be the last version.

This I suspect could have less user playback problems.

Since W10 10074 my system is now a dedicated audio playback so I don't want or need most of the W10 OS anyway.


Robert

[music33]

Well Peter, you could just do away with Windows altogether and design your own dedicated, integrated Xxhighend and OS audio playback package with a NOS add on for those who need it.

"

More and more companies are doing this.  'Geek Wave',  is a company doing this.  They have raised over a million dollars from crowd funding.  Some of the people who are working on this worked on the high-end DAC DaVinci.

https://www.indiegogo.com/projects/geek-wave-a-no-compromise-portable-music-player#/story

Of course the next step after the integrated OS and player is the using Rasberry Pi.

[coliny]

Back to the Future !

How about FreeDos http://www.freedos.org/

Colin

[coliny]

maybe also https://www.reactos.org/

[Scroobius]

Peter,

You did not respond to this - it was a genuine question any chance of a response?

http://www.phasure.com/index.php?topic=3322.msg35893#msg35893

Cheers

Paul

[PeterSt]

Paul, will it be clouded on that day ?

Peter

[Scroobius]

Paul, will it be clouded on that day ?

I think it will be a sunny day with no clouds and Peter will sort all problems 

[christoffe]

Paul, will it be clouded on that day ?

I think it will be a sunny day with no clouds and Peter will sort all problems 

on the terrace under a parasol and Peter's son is preparing the barbecue

[PeterSt]

Haha, of course I will try, but I can't tell yet. Maybe it takes a few rounds. Problem of course is : that 10074 is just too good (in comparison to all what was out prior to that). But for example : W8.1 was such a drag SQ wise, that I never even started working on that (and announced to better wait for the next version - which is what I did, or ? ).

So ... working on it.

Peter

[Michel]

O Dear...
I know you working on it..But damn this su...!

I know you can make w10 Unattended..
But thats a hell of a job. Never done it tho..

Regards, Michel

[PeterSt]

Michel,

Yes, as expected (for one of these days).
My PC was set to Sept. 1 and I try to keep it at that (didn't do it today, so now it says Sept. 2). But no such screen here yet ...

Regards,
Peter

[Michel]

Peter,

So that's the trick For how long?. Do not read anything about it or maybe I read over it.
Thx for the tip.

The problem now is that Windows10 10074 is no longer working properly. This is because I installed software to remove the watermark.However, it has caused more damage .. So I can not go into min operating system anymore. And the player will see the windows as windows xp or lower. With all its consequences.

The sound that I had is completely gone. It sounds okay, but it's not what it was.

Oh yeah , and a restore point , I never made .. :-( my stupid!

I suspect that a clean install is the only option ?

Regards,
Michel

[coliny]

Michael

Your problem is probably that windows service - "Windows Management Instrumentation" is not running. This can happen when Windows does not shut down properly.

Via control panel - admin tools - services, double click "Windows Management Instrumentation" select start "Automatic" then click Apply then click Start Service. Start XXHE now it should be OK but you may need to set memory type back to "Straight Contiguous".

I have my system clock set back exactly 2 years, this should allow W10074 to keep running 2 more years.

Colin

[BertD]

I have my system clock set back exactly 2 years, this should allow W10074 to keep running 2 more years.

Are you sure? Did you reboot after changing the date? I did and it did not work anymore... but changing the time in BIOS cured it again.

Better set it back a few months and make a batch-file to reset the date after you reboot.

Cheers,

Bert

[PeterSt]

I think Bert is right. 2 years back, for me gave the same problem.
To me it looks like we shouldn't attempt to run the OS prior to its birth date.

Regards,
Peter

[Michel]

Colin ,

Thx for the help , but it din't work..
And i also try to go back in time :-).
System din't boot..

Regards,
Michel

[PeterSt]

The problem now is that Windows10 10074 is no longer working properly.

Hi Michel,

Colin is right, but possibly you can't get it done or it does not help. Also (now start crying) : I suspect that exactly that Winmgmt service has been eliminated by that piece of software you installed, because it would be typical for that service to check for the (watermark) data you had removed by that software.

Please notice that in your XX folder there are files like OSIsW8.tss, which when renamed to .tst let your system behave like it is implied by the file name. BUT, for W10 I did not make that yet for the XXHighEnd version you all use (it's there in 2.03 - not ready yet).
In your case you can try the OSIsW81 (for Windows 8.1) which will resemble W10 the best. But I think it won't work all the way ... You'd have to try it.

Regards,
Peter

[juanpmar]

I set also the date from two years back in the  bios and so far no problem at all,  even if I reboot or shut down the pc. Perhaps it is due that I always do it from XXHighEnd (right click on the stop button)

Juan

[Michel]

Hi Peter,

I've tried it(OSIsW81 ), but no luck for me today.

Thx for the fast respons.

Regards,
Michel

[PeterSt]

But what happens ?
The empty Playlist Area should now show Windows 8.1.
Does it ?
If not, I'd say your rename didn't work out as intended. Thus, has to be :

OSIsW81.tst

And only one at the time may be in there with .tst as extension.

Peter

[coliny]

W10074 has been working fine for a couple of months now with date set back 2 years. Also its set not to sync with internet time although I have not connected it to internet. It survived going in and out of min OS as well. My pc is dual boot with W7 so that also picks up the date as 2013, even so W7 updated itself OK.

Just tried on another pc with w10074 but with current date set, it booted with the expiry message. I set date back 2 years, rebooted & works fine.

On these pc's w10074 has not been activated, perhaps setting date back does not worked if w10074 has been activated.

Maybe a fresh install of w10074 with system date already set back will work.


Colin

[BertD]

Perhaps it will work (new install W10) if you set the date of the PC a few months back before installing the OS?

It should not get any data from the internet anyhow for a minimalistic not updated OS...

Bert

[PeterSt]

My PC is not activated (it doesn't accept any of the Keys I could find).

Peter

[Michel]

But what happens ?
The empty Playlist Area should now show Windows 8.1.
Does it ?
If not, I'd say your rename didn't work out as intended. Thus, has to be :

OSIsW81.tst

And only one at the time may be in there with .tst as extension.

Peter

Peter,

I'm not at home, and will later change this evening extension again.
Perhaps I did wrong, but for now nothing had changed in the Playlist Area. Its the same as before.

Regards,
Michel

[PeterSt]

Michel, you can very wll be right. Your screenshot of it already shows different than the situation Colin actually described for you. In that case it "should" show WinNT or something like that. You have completely nothing. ... No, worse, you have "Microsoft" in that place. I don't think I have ever seen that.

You can't uninstall that anti-watermark stuff ? (I don't think so because it's probably a "patch" that changes a file)

So yes, start thinking about a fresh install.
Do not forget to use an older date, in your BIOS already.

Regards,
Peter

[AlainGr]

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

[juanpmar]

This is how I did it: First I installed W10 from a cd without connecting the Music PC to Internet at any time. With Windows10 present date I started XXHighEnd like the usual way. Then in Minimized mode I restarted from the stop button. From there I accessed to the  bios where I changed the date to 2012. I saved the  changes and exit. Started again XXHighEnd and from then on I always used the stop right click button to restart or shut down the pc. This way and so far it preserves the 2012 date. I never connected the Music PC to Internet neither changed the Minimized mode. I haven't registered W10 either.
Juan

[dsm]

I've kept build 10074  minimized since soon after the install, have not changed the date and it never connects to the internet. I have not yet seen a screen that says it will expire soon. is there a chance that I will never see the screen but come October first, it will not boot up correctly?

Best,

David

[AlainGr]

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

[juanpmar]

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.

Hey Alain,  does it mean that there is a clock in the SO that is running without taking into consideration the date but instead a certain amount of days? What is the sense to change the date in that case?

Regards,
Juan 

[AlainGr]

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.

Hey Alain,  does it mean that there is a clock in the SO that is running without taking into consideration the date but instead a certain amount of days? What is the sense to change the date in that case?

Regards,
Juan 

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

[PeterSt]

Hi Alain,

What Juan was hinting at (I think, because I noticed the same suggestion in your text) is that you seem to imply that as soon as you're in Normal OS Mode something else deals with the date. Giving a message indeed is something else, but how can you tell the difference. And I think that in MinOS you just might not get the message (but system will start to reboot and eventually stop anyway).

But what you did not tell (I think) is whether what you saw in Normal OS was just coincidental because you (coincidentally) rebooted into Normal OS, or that you could really see a difference.

I know, my questions are super vague ...

But for example :
Set date two years back in MinOS. Reboot - all fine.
Now reboot into Normal OS. Now there's the message but ALSO the date is back to today. So is it this what you mean ?
Supplementary, reboot into MinOS in this stage, and the date is still back to today (but this is hardly related any more).


I think Juan wondered whether you meant something like this ... (which I feel is hard to believe, so you must have meant something else).

Regards,
Peter

[Michel]

Hi All

Last night I did a fresh install of w10. Before the installation i put back de date one month through  the bios.Once windows installed directly put back the date two years through cmd (admin rights). A few times rebooted and played some music (waiting for an activation code), but the date remains at 2013 and that in normal OS.

I must say i have disable the windows time service. And not connection to the internet.

I hope it helps!

Regards,
Michel

[AlainGr]

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

[AlainGr]

Hi Alain,

What Juan was hinting at (I think, because I noticed the same suggestion in your text) is that you seem to imply that as soon as you're in Normal OS Mode something else deals with the date. Giving a message indeed is something else, but how can you tell the difference. And I think that in MinOS you just might not get the message (but system will start to reboot and eventually stop anyway).

But what you did not tell (I think) is whether what you saw in Normal OS was just coincidental because you (coincidentally) rebooted into Normal OS, or that you could really see a difference.

I know, my questions are super vague ...

But for example :
Set date two years back in MinOS. Reboot - all fine.
Now reboot into Normal OS. Now there's the message but ALSO the date is back to today. So is it this what you mean ?
Supplementary, reboot into MinOS in this stage, and the date is still back to today (but this is hardly related any more).


I think Juan wondered whether you meant something like this ... (which I feel is hard to believe, so you must have meant something else).

Regards,
Peter

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

[juanpmar]

Alain, once I read today the question I asked you yesterday I realized that it was not easy to understand. Your previous post seems to explain quite well the different ways for the OS to control the date.
What I wanted to say is that if we change the date in MinOS, are we stopping the command that counts the dates? If the only thing we are changing when we change the date in MinOS is the notification of the expiration date but not the real countdown, then we are not solving the issue.
I´m afraid that it will be difficult to know until October 1th.

But let´s think that we can´t stop the countdown, which it seems to me quite probable. Then, the real problem it´s not only to make the final W10 to sound as good as the v10074, the problem also will be if we can or can not to stop the automatic OS updates. If we can´t stop the updates we´ll have a permanent instability for what is important to us: the XXHE sound quality. That was the reason to stop the updates in the previous OS. In that case, probably Peter will be forced to work in a specific OS for XXHE. That could be a titanic task but... who said fear?

Regards,
Juan

PS. Take a look in this link to Are the automatic updates good or bad?:
http://www.hardwaresecrets.com/windows-10-update-everything-you-need-to-know/

[AlainGr]

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

[christoffe]

Then, the real problem it´s not only to make the final W10 to sound as good as the v10074, the problem also will be if we can or can not to stop the automatic OS updates. If we can´t stop the updates we´ll have a permanent instability for what is important to us: the XXHE sound quality.

Hi Juan,

within the W10 pro (build 10240) you can stop/avoid any update.
(for an audio PC not connected to the internet)

Joachim

[AlainGr]

PS. Take a look in this link to Are the automatic updates good or bad?:
http://www.hardwaresecrets.com/windows-10-update-everything-you-need-to-know/

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

[AlainGr]

Then, the real problem it´s not only to make the final W10 to sound as good as the v10074, the problem also will be if we can or can not to stop the automatic OS updates. If we can´t stop the updates we´ll have a permanent instability for what is important to us: the XXHE sound quality.

Hi Juan,

within the W10 pro (build 10240) you can stop/avoid any update.
(for an audio PC not connected to the internet)

Joachim

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

[juanpmar]

Then, the real problem it´s not only to make the final W10 to sound as good as the v10074, the problem also will be if we can or can not to stop the automatic OS updates. If we can´t stop the updates we´ll have a permanent instability for what is important to us: the XXHE sound quality.

Hi Juan,

within the W10 pro (build 10240) you can stop/avoid any update.
(for an audio PC not connected to the internet)

Joachim

Joachim, then the problem would be "only" to make it sound as good as the v10074.

PS. Take a look in this link to Are the automatic updates good or bad?:
http://www.hardwaresecrets.com/windows-10-update-everything-you-need-to-know/

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

Alain, I also have those W8 and W7 backups but the sound of the v10074 is so good...

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

Alain, where can I find how "to use the "date" command under the command line - that in Normal OS mode". I missed it.

Regards,
Juan

[AlainGr]

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

[AlainGr]

Just an additional note... You may see a message telling that it can't help you in your region, but at the right left of that window, there is another "lens" to search. Click on it. Then you will be able to type "cmd.exe"...

Alain

[juanpmar]

Alain, I have to do it in Normal mode, right?

Juan

[AlainGr]

Hi Juan,

All I can say is that I don't know, but since we will always pass some time in Normal OS, with all the processes that are normally workng, it would be better to do it in Normal OS

Alain

[AlainGr]

I will rephrase this...

If I do something in Normal OS, it should hold when I will go in Min OS.

But if I do something in Min OS, there are chances that some of what I did will be reverted once I go back in Normal OS.

Not sure it this makes sense, but...

Alain

[juanpmar]

Thank you Alain 

Juan

[PeterSt]

Alain,

I would say that all what can be reverted in Normal OS is the saved states from when you boot from Normal into Minimized. But this is XXHighEnd causing this. So for example, when your Network Connection is On in Normal OS and you tell to shut it off for MinOS, then the state for Normal OS is On and that will be saved; when booting back into Normal OS later, that state is re"set".

All other things you run into can not be related to MinOS itself.
Yes, this too sounds vague, but it is easier to think that all what's reset is reset because I tell it to. So no mysteries there; it is only that you don't know what that all is. But example again : if you would be able to set the color of Explorer in the Registry, and you do/change that in MinOS, then at going back to Normal OS that color will NOT be set back to how it originally was. This is because I (XXHighEnd) does not Save the Registry settings (and/or Restore those at going back to Normal OS).
If you think "the state of the running services" only, then you will be thinking quite well in the reality of matters. Nog 100% but the exceptions will be rare.

Peter

[christoffe]

Then, the real problem it´s not only to make the final W10 to sound as good as the v10074, the problem also will be if we can or can not to stop the automatic OS updates. If we can´t stop the updates we´ll have a permanent instability for what is important to us: the XXHE sound quality.

Hi Juan,

within the W10 pro (build 10240) you can stop/avoid any update.
(for an audio PC not connected to the internet)

Joachim

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

Hi Alain,

we can stop the updates of W10 when connected to the internet too.  (but that's not wise due to possible malware etc.)

Joachim

[christoffe]

Answer to Reply#47 by Juan

Hi Juan,

i can't compare the two builds.

One question: how many processes remains in build 10074 in minOS?
(to be checked via the Task Manager)
Thanx

Joachim

[juanpmar]

J

Answer to Reply#47 by Juan

Hi Juan,

i can't compare the two builds.

One question: how many processes remains in build 10074 in minOS?
(to be checked via the Task Manager)
Thanx

Joachim

Joachim, in min OS and with Unattended there is no process on. With the XXHE Gui only XXHighEnd appears.

Juan

[christoffe]

Hi Juan,

thank you. By opening the task manager with STRG+Alt+Delete you will see this screen, and under performance we see the amount of processes just running.

Joachim

[juanpmar]

Ok, sorry Joachim. I was using my phone to send the pictures. Let me do it as you say and I´ll post it here.

Juan

[christoffe]

Ok, sorry Joachim. I was using my phone to send the pictures. Let me do it as you say and I´ll post it here.

Juan

Thank you Juan. No hurry, we have all the time.

Joachim

[juanpmar]

Joachim, there are 26 processes running in MinOS

Juan

[christoffe]

Joachim, there are 26 processes running in MinOS

Juan

thank you Juan.
That's a pretty good result, in other words, Peter made a damn good job. The program I'm using (to minimize the OS) with build 10240 is leaving 36 processes running during replay in attended mode.

Thanx again

Joachim

[acg]

More processes probably shut down when you press play. 

[juanpmar]

More processes probably shut down when you press play. 

It was playing at that moment but with Unattended off

Juan

[michaeljeger]

Hi all

Not sure I understand what to do now.
Basically one week to go with that built. 

Set back the clock, or will we get something from Peter in time?

Regards, Michael

[AlainGr]

Hi Michael,

If I recall correctly, Peter will make a version that will function with the "official" Windows 10 version, but if someone would like to keep with Windows 10 build 10074 because he is comfortable with that, he can put the date backward.

Juan was able to do so through BIOS, while his system was in Minimized OS. Going back to Normal OS indicates that the date is kept equal to the BIOS date.

For someone who would do the same but with the Normal OS state, it may work through BIOS also, but for me it did not. I had to exectute the "Date" command to overcome the OS tendency of bringing back the actual date each time.

If you wish to keep the actual build (10074), you can either try through BIOS or the "date" command from the Windows DOS command line.

Regards,

Alain

[Robert]

You must all accept the fact that W10074 will be improved upon soundwise anyway. Nothing stays the same especially in the digital world.

I wouldn't be worrying too much about extending dates, even if Peter's new version is not quite as good as W10074 it will be improved by further innovation.

We will of course always be limited by Microsoft using Windows!!!!

Robert

[christoffe]

You must all accept the fact that W10074 will be improved upon soundwise anyway. Nothing stays the same especially in the digital world.

I wouldn't be worrying too much about extending dates, even if Peter's new version is not quite as good as W10074 it will be improved by further innovation.

We will of course always be limited by Microsoft using Windows!!!!

Robert

Hi,

did anyone has the time to compare 10074 with 10240?

Joachim

[juanpmar]

We will of course always be limited by Microsoft using Windows!!!!

II agree totally, probably a majority of us are agree with  it. I  wonder if Peter has decided to stay forever with Windows or, on the contrary,  there is some hope to afford this issue using other OS,  including the possibility to build a specific OS for XXHighEnd.

Regards,
Juan

[PeterSt]

All,

At this moment I refuse to do anything with 10240 because it is worse than 10074. And any not-official (of the so called "fast ring") build will expire again. So we are waiting for a next "slow ring" build.

If you don't like to set back the date (which seems to work as how things are now), then better go back to Windows 8.
Or find another hobby. haha

Best regards,
Peter

[JohanZ]

If you don't like to set back the date (which seems to work as how things are now), then better go back to Windows 8.

Hi Peter,

Today I want to set back the date by one year. First thing I did was to set back the date in the bios. After saving the bios settings, no Windows 10 but I had a blue screen with a message: "PC/Device needs to be repaired. OS couldn't be loaded because a critical driver is missing or contains errors. File:\Windows\system32\drivers\wdf01000.sys You'll need use recover tools......"
I could not solve this problem. After setting the date back in the bios all was working again.

Next attempt was to change the date in normal os in command promt mode via date command. After setting the date one year back I did a reboot. Guess what, the same error as before. No Windows but a blue screen. Now what? after some reboots back in the bios. I saw that the date was set back automatically in the bios by one year. I changed the date back to today and did a reboot again and all was working again.

So one week to go before expiration. What is the procedure to solve this problem?

PS. http://www.file.net/process/wdf01000.sys.html

Best regards,
Johan

[Jud]

All,

At this moment I refuse to do anything with 10240 because it is worse than 10074. And any not-official (of the so called "fast ring") build will expire again. So we are waiting for a next "slow ring" build.

If you don't like to set back the date (which seems to work as how things are now), then better go back to Windows 8.
Or find another hobby. haha

Best regards,
Peter

Though I am pining away hoping for a better "permanent" build, I did have to laugh at this.   

[AlainGr]

If you don't like to set back the date (which seems to work as how things are now), then better go back to Windows 8.

Hi Peter,

Today I want to set back the date by one year. First thing I did was to set back the date in the bios. After saving the bios settings, no Windows 10 but I had a blue screen with a message: "PC/Device needs to be repaired. OS couldn't be loaded because a critical driver is missing or contains errors. File:\Windows\system32\drivers\wdf01000.sys You'll need use recover tools......"
I could not solve this problem. After setting the date back in the bios all was working again.

Next attempt was to change the date in normal os in command promt mode via date command. After setting the date one year back I did a reboot. Guess what, the same error as before. No Windows but a blue screen. Now what? after some reboots back in the bios. I saw that the date was set back automatically in the bios by one year. I changed the date back to today and did a reboot again and all was working again.

So one week to go before expiration. What is the procedure to solve this problem?

PS. http://www.file.net/process/wdf01000.sys.html

Best regards,
Johan

Hi Johan,

Is it possible for you to go back maybe a few months from now ? Something like July, yet still in 2015 ? Maybe trying things with smaller steps will work ?

Not that I have tried it, since I was in Normal OS and it worked with the date instruction... It seems to be very variable, but I can't determine a common denominator...

Regards,

Alain

[PeterSt]

Hi Johan,

At least you got the very same message as I received when I tried to set mine back with 2 years (this was 2 months or so ago). Thank you for that detailed description.

I started to set back my date at Sept. 14 to Sept. 1 and I try to keep it at that (but e.g. yesterday I forgot so at this moment it will be at Sept. 3).

I did it in MinOS Mode at first with the Date command and later with PowerShell, which was just in order to find something general for you all which could be build in. Btw I failed on that because it was too difficult for the time I gave it to find an automatic means of the proper format (various formats exist for various countries).
I gave up on that and decided to just change the date by normal means - with mouse in the bottom right corner.
I now apply this every day (if I don't forget).

A few days ago I tested all kind of reboots, because my system is more complicated, booting from RAM. Anyway, I always looked at the BIOS date meanwhile, and it always sticked.
Side note : when I set back my date with two years, I did this in the RAM version, and the RAM version did not want to boot any more with the same error you described. Go figure. The normal base version (for it) booted (I only tried this a week later) and the date was back to "today". After that the RAM version (which copies from the base version) booted again as well.

Summarized ... all I did not test (I forgot it) was going to Normal OS ...

It should just work, but as was told by others ... maybe only go back a little ?

Additional problem by now could be that in your case it will already have entered the "state of expiration" that might have registered special data in the registry etc. The effect of that (if so at all) I don't know ...
Similar will be when it doesn't boot any more (Oct. 15 ?) ... then I suppose it really never will because of a set "flag" somewhere.

Peter

[Robert]

Oh my god you are chasing a dream.

Gosh sounds like you are trying to turn back time!!!!

Peter you need St Peter's OS!!!!!

Unless you can unravel Microsoft's Da Vinci Code!!!!

Robert not the saint

[PeterSt]

Hahaha

Maybe you are right. But "dream" = "nightmare".
At least for some, it is.

Peter

[PeterSt]

I have a most interesting addition :

I am shutting off (down) all to bring it to this weekend's show; For that I need to mount the "base file" for the Windows 10 RAM bootable OS version. This goes automatically with the Shut Down (by XXHighEnd) but it did not want to work this time.
And just prior to this I set back the earlier today mentioned date of Sept. 3 to Sept. 1 ...

But I now recall that I did similar the last time, and that then too the "base file" would not mount. And after that it did not want to boot any more ...

And so I set back the date to Sept. 3 et voilá, it mounted again.
Whether it still boots ? I guess so, but we will see that on the Show ...
hum

Peter

[AlainGr]

I certainly wish you the best Peter ! Hope that time travelling will not make you another "Dr Who" and all the adventures that surround him

I will be in spirit with you all there But don't talk in my back ok ? ha ha !

I will be happy to read the report you will make about it, but in the meantime, keep smiling even if things do not always turn like we hope and expect Life is short !

Kind regards,

Alain

[michaeljeger]

So I set back the date 3 months.
Works fine

Please note that if you set back the date one year, the system will not boot any more and will go into recovery mode. Quite strange.

Anyway, very happy with the SQ, now even in minimized OS.
Great stuff!!!

Michael

[coliny]

Here's something to try if you can't get W10074 to boot with date set back. I can't test it because my pc's all boot happily in 2013.

wdf01000.sys is involved with verifying hardware drivers. We have different hardware so probably different different drivers installed. One or more of these is probably failing the verification process during boot because the date is set and confusing the process.

 Something similar happens when I try to use a browser with date set to 2013, I get message "there is problem with website security certificate - it has expired or is not yet valid". Time travel is rather confusing isn't it"

So you could try this solution to disable the Verification process, its Option 2 :- http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Good luck
Colin

[PeterSt]

Hi Colin,

I just read through that and I don't think there is anything to shut off. To me it looks like that this is to activate when wanted (check your drivers for good operation) and when all is fine, shut it off again (or otherwise huge overhead ?).

If you read through the posts it also looks like that this is nothing to play with for fun, because I see people report that their systems won't boot any more. I think this is not what we want to accomplish.
haha

But thanks, because the idea looks good.
At least it brings me to the idea of the certificates and the checking against those. And indeed, when a certificate expires, you can't use the driver. And if it is not officially active yet (you can run into that with set-back dates) - the same I suppose.
Now I am not sure how this is / can be related to the Driver Signing we (as Phasure NOS1a users) disable (is a formal option in XXHighEnd). And just saying ... in my base W10 version (the one which is used to boot from RAM) I never shut off that Driver Signing (checking) - at least that is what I think (my W10 RAM version existed earlier than the Driver Signing option in XXHighEnd ?).

Maybe never mind (my paragraph above), because I too get confused somewhat.

Peter

[juanpmar]

Hi all,

This morning appeared for the first time the message in the picture when I turned on the Audio Pc. It seems that the real problem starts from now on, at least for me. I hope I´m wrong as I don´t have time rigth now to look for some solution but I restarted the pc several times and the message appeared again. Never before it appeared when turned the Audio Pc on.

Traslation (aprox):

Recovery

Expired one component of the operating system.

File: Windows/system32/winload.exe
Error Code: 0xc0000605

You must use the recovery tools. If you have not an installation media (such as a cd or a USB device), contact the computer administrator or the manufacturer of the computer or device.

Press enter to try again
Press F8 to the startup configuration


Regards,
Juan

[PeterSt]

Hi Juan,

And what is the date in your PC ?

Peter

[juanpmar]

Hi Juan,

And what is the date in your PC ?

Peter

Peter,  I can't see it with that window but yesterday it was September 2012

Juan

[PeterSt]

Hmm ...
Maybe you can observe the date in the BIOS ?

So actually you can't do anything now any more ?

Peter

[juanpmar]

Hi Peter, I wasn't at home and couldn't see the bios. The date there was 2019 and why has been changed there I don't know. Now changing it again to 2012 the problem is solved. Sorry for the alarm, now I cross the fingers for tomorrow as it seems to be the end date.

Regards,
Juan

[PeterSt]

Hey Juan,

No ... no worries. we (can) all run into such problems and it is only good that "we" have the experience. Sharing this is nothing much about false alarms, as long as it is useful to know.

Btw, tomorrow (Oct. 1) is not the date that all stops; instead messages will appear and reboots will take place regularly (no, not nice for playing music). At Oct. 15 the system won't boot any more. At least that is what is claimed.

Regards,
Peter

[juanpmar]

Thanks Peter

Juan

[Robert]

Well I have just reset the date using right hand desktop icon back to 1.9.15 and no problems with playback etc. At this point I have no warning messages.

I did this in min OS.


Robert

[Scroobius]

This morning I could not boot 10074, there was an error message stating the computer needed repair as there was a problem with a windows start up file IIRC. So I rebooted and went into BIOS where I changed the time back to the start of this year. Reboot worked fine but then Windows allocated todays date and time. So out of interest I rebooted and (surprise surprise!!) the reboot failed again with the same error message. So I rebooted again went into BIOS and changed the date back to the start of the year rebooted and no problems started up OK. When Windows came up I changed the date and time (via control panel) back to the start of the year and I also stopped the time being updated automatically via the internet. So the date and time now will not be changed unless it is by me!!.

Have I missed something? I am sure it cannot be that easy but anyway so far everything is working fine. 

The only very very minor thing is that when I RDC connect I get a "certificate" query presumably because of a date discrepancy but just click that way no problems.

If you want to change date/time in "unattended" mode use the following command from the command line "control timedate.cpl"

Cheers

Paul

[PeterSt]

Hi Paul,

Did you miss something ? ehm, this whole topic perhaps ?

And obviously, when you sync the date/time with something on the Internet ... what to say.

Back to the beginning of the year is not good. Make it Sept. 2 2015 (earlier and indeed (PayPal) certificate problems emerge.

Peter

[Scroobius]

Did you miss something ? ehm, this whole topic perhaps ?

Its a fair cop - I have read it now!!

[PeterSt]

Ok Paul, good. If you have any questions, don't hesitate ...

Peter