Failure to install Windows 10 April Update(version 1803)

Anonymous
2018-05-04T03:55:09+00:00

I am unable to install The Windows 10 Feature update to OS version 1803(from version 1709) on my PC.

It is giving 0xc1900101 error. I have all the latest drivers on my PC. The current OS build of my PC is 16299.371.

After each failure, the update gets downloaded again and it has failed 5 times.

I would be grateful if someone could please help.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

178 answers

Sort by: Newest
  1. Anonymous
    2018-06-24T03:32:23+00:00

    I've tried a mountain more things and the results are always the same. Reboot into 1803, the keyboard freezes and I'm forced to power off.

    Always with the same failure mode:

    I've uninstalled all sorts of things. Updated my keyboard drivers. Done a lot more cleaning.

    Disabled pretty much everything I can and still boot. I clean boot and of course it blows chunks.

    I have the SetupDiagResults log and a zip of logs but I'm not seing how I post those here.

    Please find the log below. Any idea what is causing it?

    Matching Profile found: FindFatalPluginFailure - E48E3F1C-26F6-4AFB-859B-BF637DA49636

    System Information:

        Machine Name = [removed]

        Manufacturer = System manufacturer

        Model = System Product Name

        HostOSArchitecture = x64

        FirmwareType = PCAT

        BiosReleaseDate = 20101222000000.000000+000

        BiosVendor = BIOS Date: 12/22/10 17:47:29 Ver: 08.00.15

        BiosVersion = 1202

        HostOSVersion = 10.0.16299

        HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908

        TargetOSBuildString = 10.0.17134.1 (rs4_release.180410-1804)

        HostOSLanguageId = 1033

        HostOSEdition = Professional

        RegisteredAV =

        FilterDrivers =

        UpgradeStartTime = 2018-06-23 22:41:44

        UpgradeEndTime = 2018-06-23 23:01:34

        UpgradeElapsedTime = 00:19:50

        ReportId = 87eea5b9-11b7-4cfb-9521-a1f3818b4f77

    Error: SetupDiag reports fatal migration plug-in failure. Plug-in Name = %windir%\system32\IasMigPlugin.dll, Migration Operation = IPostApply->PostApply, Plug-in Error: 0x0000007

    Refer to https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-error-codes for error information.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-06-23T05:18:42+00:00

    I made the mistake, (hindsight) of accepting the insistent update. I am now stuck in a loop. If you want us to continue to trust you with our digital experiences, your updates need to be solid. Please and thank you, truly.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-06-22T16:39:49+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-06-22T09:06:31+00:00

    "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.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-06-22T06:11:19+00:00

    "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!!!!

    Was this answer helpful?

    0 comments No comments