If your Windows 10 fails at installing a feature update, with error code 0XC19001E2; then you are at the right place to find the fix;
But first, let’s explain briefly what is a Windows 10 feature update;
A feature update is a new Windows 10 version that Microsoft releases twice a year (roughly every six months) during spring and fall. These are also known as “semi-annual” releases.
How to fix a windows feature update failing with error 0xc19001e2?
- First, download SetupDiag tool from Microsoft Website;
- Create a “C:\Tools” folder and copy the SetupDiag.exe file to that location;
- Run SetupDiag.exe; it will read the Windows update log and generate a report under “C:\Tools\SetupDiagResults.log“. The report contains the problems found and a proposition of a fix.
Your SetupDiagResults.log file will look like this:
Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD SetupDiag version: 1.6.0.0 System Information: Machine Name = Offline Manufacturer = Model = HostOSArchitecture = 1033 FirmwareType = BiosReleaseDate = BiosVendor = BiosVersion = HostOSVersion = 10.0.17134 HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804 TargetOSBuildString = 10.0.18362.418 (19h1_release_svc_prod1.191005-1654) HostOSLanguageId = HostOSEdition = Professional RegisteredAV = FilterDrivers = UpgradeStartTime = 12/4/2019 11:19:49 AM UpgradeEndTime = 12/4/2019 11:23:43 AM UpgradeElapsedTime = 00:03:54 CV = Uz7DkzXQqEK+G/Ry ReportId = 0f7f41b2-1464-4654-8f48-ab69b307c66c Error: SetupDiag reports abrupt down-level failure. Last Operation: Finalize Error: 0xC19001E2 - 0x40024 LogEntry: 2019-12-04 11:20:14, Error MOUPG CSetupManager::ExecuteCustomScript(11048): Result = 0xC19001E2 Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information. Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD SetupDiag version: 1.6.0.0 System Information: Machine Name = Offline Manufacturer = Model = HostOSArchitecture = 1033 FirmwareType = BiosReleaseDate = BiosVendor = BiosVersion = HostOSVersion = 10.0.17134 HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804 TargetOSBuildString = 10.0.18362.418 (19h1_release_svc_prod1.191005-1654) HostOSLanguageId = HostOSEdition = Professional RegisteredAV = FilterDrivers = UpgradeStartTime = 12/4/2019 11:19:49 AM UpgradeEndTime = 12/4/2019 11:23:43 AM UpgradeElapsedTime = 00:03:54 CV = Uz7DkzXQqEK+G/Ry ReportId = 0f7f41b2-1464-4654-8f48-ab69b307c66c Error: SetupDiag reports abrupt down-level failure. Last Operation: Finalize Error: 0xC19001E2 - 0x40024 LogEntry: 2019-12-04 11:20:14, Error MOUPG CSetupManager::ExecuteCustomScript(11048): Result = 0xC19001E2 Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.
At the end of the report, you will find information on the error and sometimes a suggested fix if the error is well-known.
For the error 0xC19001E2, SetupDiagRsults give just information about a setup instruction resulting in the error code 0xC19001E2.
This setup instruction is CSetupManager::ExecuteCustomScript().
This means that the Windows Setup failed to execute a custom action scripts that ran from subfolders in %windir%\System32\update\
So, to fix the Windows 10 update error code 0xC19001E2, delete the content inside “%windir%\System32\update\” path.
If you love this post, please leave a comment.
Share this post on your favorite social media platform, and let other people benefit.
Oh my God! I’ve been searching for this hint for two years! I updated my VM from Parallels to VMWare and could no longer update Windows. Windows update always claimed 0xC19001E2 and the Windows Media Creation Tool did the same thing all without any clue as to what script actually produced the error. ALL of the other web sites suggest completely useless tips always leading up to the typical “Re-install Windows and lose everything” approach so often cited as ‘the solution’ in the Windows world.
Yes, Parallels left something in place. Does VMWare shove things into the OS like Parallels does? I sure hope not.
I’m happy that my article helped you solve your 2-year-old problem 🙂
So just delete everything inside that particular sub folder?
Yes, But first create a restore point in case you need to roll back
SetupDiag creates a report sized 0 byte for me. My laptop runs with Win10 v1909. Any idea?
Didn’t work for me. Any second option?
what’s the error message shown by the SetupDiag tool?
This worked great. Thanks. In my case Parallels had an entry in the preinstall.cmd file. I no longer use Parallels in this vm but the entry was still there.
I’m glad that this article helped you solve your issue 😉