Failure to install Windows 10 April Update(version 1803)

My computer was built from quality parts years ago. I've added over time. That system has a ASUS P6T Deluxe V2 motherboard with an i7 920 CPU, 12GB RAM and a couple SSDs. It has an NVidia 660TI video card with the latest drivers and a few years old Brother multi function printer. In one of the recent attempts we disabled those last two drivers, clean booted in safe mode from the ISO and it still hung the same way.

I suspect one of the Microsoft provided drivers related to the motherboard is probably hosed or MS hasn't done the various CPU mitigations properly. When I get a chance I'll see if I can use some of the other responses to get more helpful information.

"Incompatible Driver" - well I suppose that is why Microsoft in its description put the word "generally" as it is not in my case.

The drivers are all MICROSOFT drivers!!!! They work with 1709 fine!

I completely re-installed 1709 with nothing but the microsoft drivers, no additional software, just the bare Microsoft Win 10 Build 1709, and it DID NOT UPGRADE successfully to 1803. Although 1709 works fine by itself.

1803 is a complete basket case!

In my case even a power off, boot with win 10 Build 1803 image on USB will not even get to the initial screens asking for Keyboard language, Time/Date etc. This is a complete clean install - don't even get to see any install actions!

There is something VERY WRONG with the early install code of this update the pre-boot "SAFE_OS" environment is where it is failing! (Not very SAFE is it!)

I will not be upgrading to 1803 to provide logs for Microsoft. I don't have the time to waste on a poor OS upgrade that provides no additional benefit. My Windows 7 PC and my LINUX partition work 1000x better.

Go back and get your Test and Evalution Team back together and do it properly. Don't rely on the real world users to do your ALPHA testing!!!!

Sorry not a technical update here.

I'm sticking to 1709. ( metered connection set)  From talking to various friend,s there is a pattern emerging. Some machines have no problem and 1803 just goes on. For many others, once if fails there are hours of work to try and get it to work with a 50/50 chance of success. One friend has a computer software company he has also hit major problems with the 1803 software update.  I don't have the time for all this testing and rework. So as has been said earlier,  come on Microsoft fix your product, and stop sending out defective software.

"Incompatible Driver" - well I suppose that is why Microsoft in its description put the word "generally" as it is not in my case.

The drivers are all MICROSOFT drivers!!!! They work with 1709 fine!

I completely re-installed 1709 with nothing but the microsoft drivers, no additional software, just the bare Microsoft Win 10 Build 1709, and it DID NOT UPGRADE successfully to 1803. Although 1709 works fine by itself.

1803 is a complete basket case!

In my case even a power off, boot with win 10 Build 1803 image on USB will not even get to the initial screens asking for Keyboard language, Time/Date etc. This is a complete clean install - don't even get to see any install actions!

There is something VERY WRONG with the early install code of this update the pre-boot "SAFE_OS" environment is where it is failing! (Not very SAFE is it!)

I will not be upgrading to 1803 to provide logs for Microsoft. I don't have the time to waste on a poor OS upgrade that provides no additional benefit. My Windows 7 PC and my LINUX partition work 1000x better.

Go back and get your Test and Evalution Team back together and do it properly. Don't rely on the real world users to do your ALPHA testing!!!!

If anyone wants to troubleshoot this, you can ask a new question/reply to this thread with the Rollback logs so that I can have a look.

Via: https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures

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. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:

• The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp,
• Event logs: $Windows.~bt\Sources\Rollback*.evtx
• The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). To resolve a rollback due to driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a clean boot before initiating the upgrade process.