Win 10 RS-4 not compatible with Intel DX58SO motherboard

johngalt said:

It still makes 0 sense though. Why would this affect your machine and not mine?

Heck, I just clean installed FCU twice in the last 2 weeks on this machine and upgraded to 17046 both times without a hitch....

I don’t know mate, I only came to that conclusion after reading everything I possibly could on the subject of:

Error 0xC1900101– 0x20017, the installation failed in the SAFE_OS phase with an error during BOOT operation.

Maybe I got it all wrong, but what other possible reason is there for my system to suddenly become incompatible with the new build updates, when prior to the RS-4s it was perfectly happy updating anything and everything MS decided to throw at us.

Maybe there are other changes made in the RS-4s that are affecting my system but who knows what they could possibly be?

I’m baffled; I know the problem is to do with the Motherboard and BIOS but what to?

Operating System - Windows 10 Pro 64-bit
CPU - Intel Core i7 920 @ 2.67GHz 46 °C Bloomfield 45nm Technology
RAM - 6.00GB Triple-Channel DDR3 @ 640MHz (8-8-8-19)
Motherboard - Intel Corporation DX58SO (J1PR) 45 °C
Monitor - DELL 2407WFP (1920x1200@59Hz)
Graphics - 2047MB NVIDIA GeForce GTX 1060 6GB (ASUStek Computer Inc) 33 °C
Storage - 279GB Maxtor 6L300S0 ATA Device (SATA) 29 °C
Storage - 931GB Western Digital WDC WD10EARS-00Y5B1 ATA Device (SATA) 24 °C
Optical Drives - PIONEER DVD-RW DVR-216D ATA Device
Audio - High Definition Audio Device

Thanks mate that’s what I’m hoping for:)

If the computer powers up, performs the Power-On Self-Test successfully, finds a Boot Device, and Loads the Operating System then transfers Control over to the operating system but the operating system then freezes.

Bearing in mind that any other operating system (including windows prior to RS-4) would take over and install perfectly

Is it the computers fault or is it the operating systems fault? :)

Thanks for responding mate, the problem with the Signing/verification process only started approximately December 1^st according to Microsoft’s support engineer. (Link below)

So I’m not sure if that would have affected me as my problem started from 13/10/2017 with the release of Build 17017.

Mind you he does also say it affects any current development branch build up-to and including 17046.

But having fewer drivers with the RS-4s being the problem would make perfect sense.

Let’s hope it’ll all get resolved with the new release tonight, if we get one. :)

https://answers.microsoft.com/en-us/...2525162&auth=1

0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation

0xC1900101
A frequently observed result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present.

https://docs.microsoft.com/en-us/win...rors#log-files

Code 0xC1900101 - 0x20017

Mitigation
Ensure that all that drivers are updated.
Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers.
For more information, see Understanding Failures and Log Files.
Update or uninstall the problem drivers.

Cause
A driver has caused an illegal operation.
Windows was not able to migrate the driver, resulting in a rollback of the operating system.
This is a safeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software.