N-central Troubleshooting
Windows 10 Feature Update to 1809 failed
Last Modified
Tue Mar 05 17:03 GMT 2019
Description
- When trying to upgrade a device to Windows 10 Version 1809 (October 2018 Update) via Patch Management, the update is failing.
- The error in c:\Program files (x86)\N-able Technologies\Windows Agent\Log\PatchInstall.log contains an entry like the below:
[91] 2019-03-04 14:11:07,096 <<*>> ************************ Start Installing Anniversary Updates ************************[91] 2019-03-04 14:11:07,097 INFO Detected 1 Anniversary Updates for install[91] 2019-03-04 14:11:07,097 <<*>> ===>>> Initiated Windows upgrade: (35e7721b-da04-440a-8553-a2a4c4cc55fe) Feature update to Windows 10, version 1809[91] 2019-03-04 14:11:07,097 INFO AnniversaryUpdatesInstaller => Initiating Anniversary Update install ([35e7721b-da04-440a-8553-a2a4c4cc55fe], Feature update to Windows 10, version 1809).[91] 2019-03-04 14:11:07,100 WARN AnniversaryUpdatesInstaller => Detected existing directory [C:\$WINDOWS.~BT\]. Installation may fail.[91] 2019-03-04 14:11:07,100 WARN Check registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images] - existing mount to [C:\$WINDOWS.~BT\] can cause failing upgrade with exit code 50.[91] 2019-03-04 14:11:07,148 ERROR Failed to read encryption data from ESD, ESD is possibly already decrypted, continuing. Exception: com.nable.agent.framework.PatchManagement.Installers.InstallerPhase.AnniversaryUpdate.EsdDecryptor.EsdReadException: Exception when reading ESD file: ---> System.SystemException: Failed to find ESD node in esd file body. at com.nable.agent.framework.PatchManagement.Installers.InstallerPhase.AnniversaryUpdate.EsdDecryptor.EsdDecryptor.GetEsdNode(XDocument body) at com.nable.agent.framework.PatchManagement.Installers.InstallerPhase.AnniversaryUpdate.EsdDecryptor.EsdDecryptor.DecryptEsd(String filename) --- End of inner exception stack trace --- at com.nable.agent.framework.PatchManagement.Installers.InstallerPhase.AnniversaryUpdate.EsdDecryptor.EsdDecryptor.DecryptEsd(String filename) at com.nable.agent.framework.PatchManagement.Installers.InstallerPhase.InstallerPhaseFunctionProvider.DecryptEsd(String esdFilePath)[91] 2019-03-04 14:11:56,766 ERROR Process failed with exit code -1047526904.[91] 2019-03-04 14:11:56,766 ERROR Anniversary Update Phase 10 failed. Initiating CleanUp.[91] 2019-03-04 14:11:57,153 ERROR Process failed with exit code 50.[91] 2019-03-04 14:11:57,460 ERROR Anniversary Update Failed[91] 2019-03-04 14:11:57,460 <<*>> ************************ End Installing Anniversary Updates **************************
Environment
- N-able N-central
- Windows 10
- Patch Management Enabled
Solution
- The important error in this situation is the "exit code 50" at the end of the above log snippet
- Per Microsoft, this code means ERROR_NOT_SUPPORTED
- To get some additional information about the problem, you can attempt the upgrade manually on the device. It will likely display a prompt like the following:
- This indicates that the upgrade cannot proceed until the user consents to this action - we do not consent to this kind of action automatically during a silent patch installation.
- To remedy the issue, you would need to determine what item is causing the incompatibility with the installation and correct it in order for Patch Management to install the patch silently.
- In the case above, there's an incompatible driver that would need to be removed or upgraded to fix the problem (but there could be other items that cause incompatibility with the feature update, such as incompatible software.
- Some reference to what can prevent the 1809 upgrade from running (or even being presented to devices) can be found here: