V2004 Error 0xc19001e1 But Macrium Saves the Day

Turned on one of my PCs this morning and discovered that there was no wired Ethernet connection, yikes! I discovered that Feature Update V2004 had tried to install and failed with 0xc19001e1. I had it blocked but likely I let the the time period expire without extending it.

I rebooted to the Macrium Rescue Partition and in 5 minutes restored a recent Macrium image of the OS that was made a few days before the failed update occurred. Ethernet connection restored, problem solved.

The moral of the story is to have an external storage device, always run updated images either full/differential/incremental, (I run an updated image at the end of every day) and have a working USB Rescue key or a bootable Macrium partition. Keep your data separate from the OS, a separate partition is good but a separate disk is better. That way you only need to restore your OS and you'll be back up quickly.

Hi, good example. I'm curious, as I'm running 1903 still on 2 (EOS Dec 2020) - did you defer feature updates or use some other means to delay upgrading, and what's your current build? Thanks.

dalchina said:

Hi, good example. I'm curious, as I'm running 1903 still on 2 (EOS Dec 2020) - did you defer feature updates or use some other means to delay upgrading, and what's your current build? Thanks.

Hi dalchina. It was on V1909 and I had deferred feature updates under the advanced options on Windows update but I think I let the time run out. Too many PCs to keep up with. I had the same thing happen yesterday on a 3 week old Alienware gaming rig but 2004 installed on that without any issues. Go figure! V2004 is looking a bit like spinning the Wheel of Fortune.

Odd that it happened- the theory is that feature upgrades are now opt-in.. not automatic unless end of service life.

dalchina said:

Odd that it happened- the theory is that feature upgrades are now opt-in.. not automatic unless end of service life.

I lost sight of the fact that we supposedly had an opt-in choice. I was fixated on my election to defer by x number of days. Now that you’ve reminded me of the opt-in choice, I can definitely tell you that I did not opt-in to download and install 2004 on either PC because I’m wary of the issues that I’ve seen. So it would appear that MS has unleashed 2004 on us in spite of telling us we have a choice. This really makes me wary of MS.

Update: Might it be that in MS’s way of thinking if you’ve allowed the deferral period for Feature Updates to expire then you’ve tacitly given them your approval to download and install whatever Feature Update is pending?

zbook said:

0XC19001e1 = MOSETUP_E_PROCESS_SUSPENDED = The installation process was suspended.

Now that’s interesting. Could it be that 2004 had downloaded and was in the process of installing without giving me a notification not to shut down? Seems a bit odd that could happen. I definitely wouldn’t shut down in the middle of an upgrade. What do you make of all this?

zbook said:

The error code and message were displayed in this link: modern setup (mosetup) error codes
https://docs.microsoft.com/en-us/win...n-setup-errors

It may require troubleshooting Panther logs.

Consider these trial and error steps:

1) create a bootable windows 10 iso 2004
2) place the computer in clean boot
3) uninstall any non-Microsoft antivirus
4) select updates after a successful upgrade

https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Hi zbook, thank you for the trouble shooting steps. For now I’m going to continue to defer 2004 for a few months and try again when more of the bugs are worked out.