n-Able Patch Management is failing to install the Windows 10 21H1 feature upgrade. The only reason it gives is “Process exited with code –1047526904.”
This page from ManageEngine suggests that the issue is a program incompatibility. Tracking back through setup logs:
1. The n-Able Patch Management Engine (PME) log, C:\ProgramData\MspPlatform\PME\log\ActionManager.log, repeats the error, but helpfully points back to files in C:\$Windows.BT:
[11] 2021-09-27 03:02:23,236 OFF InstallFeatureUpdate => --- Installation media was prepared successfully. Start FU installation --- [11] 2021-09-27 03:02:23,237 OFF Check progress in Panther logs: [11] 2021-09-27 03:02:23,238 OFF C:\$Windows.~BT\Sources\Panther\setupact.log [11] 2021-09-27 03:02:23,239 OFF C:\$Windows.~BT\Sources\Panther\setuperr.log [11] 2021-09-27 03:02:23,241 DEBUG Starting process (time limit: 2021-09-27 06:00)... [11] 2021-09-27 03:03:36,781 OFF InstallFeatureUpdate.ParseResult => Installation action for [8c6a24e2-698b-4120-ae14-522c031b64af] finished with ExitCode = '-1047526904' [11] 2021-09-27 03:03:36,790 ERROR Previous action ended with error, stopping feature update workflow. Error: Process exited with code -1047526904
2. C:\$WINDOWS.~BT\Sources\Panther\setupact.log has this near the end:
SetupHost: Diagnostic results location: [C:\WINDOWS\logs\SetupDiag\SetupDiagResults.xml]
3. C:\WINDOWS\logs\SetupDiag\SetupDiagResults.xml is pretty useless:
<?xml version="1.0" encoding="utf-16"?> <SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag"> <Version>1.6.0.0</Version> <ProfileName>FindAbruptDownlevelFailure</ProfileName> <ProfileGuid>55882B1A-DA3E-408A-9076-23B22A0472BD</ProfileGuid> <LogErrorLine>2021-09-27 03:03:23, Error MOUPG CSetupManager::ExecuteInstallMode(868): Result = 0xC1900208</LogErrorLine> <FailureData>Error: SetupDiag reports abrupt down-level failure.Last Operation: FinalizeError: 0xC1900208 - 0x4000D</FailureData> <FailureData>LogEntry: 2021-09-27 03:03:23, Error MOUPG CSetupManager::ExecuteInstallMode(868): Result = 0xC1900208</FailureData> <FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData> <FailureDetails>ErrorCode = 0xC1900208, ExCode = 0x4000D, Oper = Finalize</FailureDetails> </SetupDiag>
4. Back in the C:\$WINDOWS.~BT\Sources\Panther folder, the ScanResult.xml file as well as the latest CompatData*.xml file both point to the same “hard” upgrade block, on PGP Desktop:
<Programs> <Program Name="PGP Desktop" Id="000022bd552434bca7082a872ef4dff5b0ad00000904" IconId="000022bd552434bca7082a872ef4dff5b0ad00000904"> <CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/> <Action Name="AutoUninstall" Link="wsc:wica:_000022bd552434bca7082a872ef4dff5b0ad00000904" DisplayStyle="Link" ResolveState="NotRun"/> </Program> </Programs>
PGP Desktop has blocked previous Windows 10 upgrades, so this isn’t too surprising. The only thing that seems odd is when I choose to Check for Updates, the 21H1 upgrade worked fine, without having to uninstall PGP Desktop first.
Why does an interactive upgrade work but an upgrade through Patch Management fail?