Windows 10 Build 9907 reboot at Windows logo

[Applegame12345]

I got Win10 Build 9907 in Russian and when I try to boot it up in VMWare it reboots after Windows logo appearing.
When I boot up in WinPE and inserting ISO file and opening it installation starts, but after restart at Windows logo it reboots several times and it gives me an error (0xc0000001). Any solutions?

[BetaVista]

Did you set the correct BIOS date because Windows 10 builds won't boot and set EFI because 99xx builds don't like legacy firmware aka "BIOS".

[Applegame12345]

Did you set the correct BIOS date because Windows 10 builds won't boot and set EFI because 99xx builds don't like legacy firmware aka "BIOS".

Yes. When I set current time it instantly gives me other error.
This happens after 1st part of setup

[BetaVista]

What error? Send a screenshot via the BA Image Uploader or PM me

[Applegame12345]

What error? Send a screenshot via the BA Image Uploader or PM me

[BetaVista]

The build either is corrupt or the bios date is not set properly it says a component of the operating system has expired.

[Applegame12345]

The build either is corrupt or the bios date is not set properly it says a component of the operating system has expired.

I purposely set current date for showing other error.
I need fix for first error.

[Windows OS]

Boot into a DOS/Windows 9x boot disk. We need to make 1000% sure that the BIOS date is changed, as some Virtual Machine programs automatically change the date to the current date and time.

So, find a Windows 98 boot disk (you can easily find one online), boot it up, and then run the "date" command. That'll report the date set.

[Applegame12345]

Boot into a DOS/Windows 9x boot disk. We need to make 1000% sure that the BIOS date is changed, as some Virtual Machine programs automatically change the date to the current date and time.

So, find a Windows 98 boot disk (you can easily find one online), boot it up, and then run the "date" command. That'll report the date set.

After changing the date

[BF10]

The boot disk states that the date was currently set to 11-22-2017 and it was later changed. That is a sign that the BIOS date for VMWare is still syncing to the current time. Note that if you change the date, it only change the date for the OS, not for the BIOS so Windows will still detect the date as 11-22-2017.

The Collection Book has instructions to getting the BIOS date not to sync: https://www.thecollectionbook.info/info ... ios_dates/

[Applegame12345]

The boot disk states that the date was currently set to 11-22-2017 and it was later changed. That is a sign that the BIOS date for VMWare is still syncing to the current time. Note that if you change the date, it only change the date for the OS, not for the BIOS so Windows will still detect the date as 11-22-2017.

The Collection Book has instructions to getting the BIOS date not to sync: https://www.thecollectionbook.info/info ... ios_dates/

Still gives the same error.
When OS appears at Windows logo it reboots several times and gives error 0xc0000001

[AlphaBeta]

If I recall correctly, bootmgr in Win10 patches itself if the system happens to boot up even once after the timebomb expiration date, rendering the system unbootable. No idea whether this applies to this exact build, somebody with proper knowledge could clear this up (cc courage)

[Courage]

If I recall correctly, bootmgr in Win10 patches itself if the system happens to boot up even once after the timebomb expiration date, rendering the system unbootable. No idea whether this applies to this exact build, somebody with proper knowledge could clear this up (cc courage)

I tried out two builds from this build range.

9900 does show the first error when the date is outside its acceptable range. Changing the date back to an acceptable one is enough to get the system working again. I couldn't seem to trigger that error in 9907 at all, however, for some reason.

As for the second error, here's a link which contains more details on the matter:
https://answers.microsoft.com/en-us/win ... 0df?auth=1

[Applegame12345]

I successfully booted ISO of this build from my main laptop, and no errors.