I’ve now consulted to about half a dozen environments where we have leveraged the feature update approach for windows servicing. I’m seriously considering every upgrade forward to be done this way instead of using highly complex in place upgrade task sequences. There are some drawbacks for reporting but we can PowerShell to capture data, and perform many custom actions. These last few months have been very focused on windows migrations specifically implementing the feature update approach. I’ve also started to focus more on on cyber-security both offensive/defensive. I will blog some of that stuff when I get approval from the customer
OxC190010A
Error Not Found
This means one of your commands are misspelled in the setupconfig.ini. Make sure your commands are typed out correctly per this document below.
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options
0x80070490
Element Not Found
If you run into this badboy the problem exists in your setupconfig.ini this was either malformed or your header information is messed up like you have brackets missing.
0xC190010D
Error Not Found.
Stop windows update agent, delete the C:\windows\softwaredistribution folder and restart the agent, Rerun the software update deployment eval scan cycle, and should be resolved. If still not resolved make sure you delete the C:\$Windows.bt\ folder.
0x80070003
System Cannot Find the file path specified.
FInally, we have an error code that can tell you something immediately w/o having to dig into logs. If you run into this make sure your directories are created that you cite in your setupconfig.ini. I’ve implemented a hidden TS that runs in advance which creates directories, stages required content like my driver packages, setupconfig.ini, custom run scripts, setupcomplete.cmd and other PowerShell scripts. One thing I recommend to environments is that they leverage a custom compliance item to verify folders/files are in place to avoid failures. This will also go into your collection design as a safety mechanism to keep the wrong systems from seeing the advertisement. I’ll blog the full end to end solution in August.
0x80244022
Same as HTTP Status 500 – the service is temporarily overloaded.
ok so this isn’t completely feature update exclusive. This is patching related, but I was trying to test feature updates and this problem occurred. Take a look at your sccm infrastructure as this site system cpu was pegging at 99%. I’ll write a post on how we troubleshoot that problem and how to recover so your environment can be stable again.
0x87D00705
Pause State Required
Check the registry and verify paused key is not set to 1 as it should be 0
HKLM\Software\Microsoft\SMS\Mobile Client\Software Distribution\State
In my case this was set correctly all I did was restart the sms host agent and I was able to clear the issue.
0x87D00664
Time-out error. Make sue you go into the windows sevicing node > open the feature update > open properties > max run time tab > change this from the default of 120 minutes to a greater number. I typically put this to 240 or 480
Key Troubleshooting Locations: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs
NOTE: In 0xC190010A, 0x8007049A the error was so early in the process that the key log file locations in C:\$Windows.bt\ and the C:\windows\panther\unattendgc did not have updated log files covering the info. That might be a take away from the feature update product group to investigate.
0x87D00656
I’ve seen this 0x87D00656 error before and it means the update handler was unable to continue due to some internal generic error.
Typically the end user will see the error displayed in software, but setup host will still be running in the background. If the end user tries to “Retry” in software center while the setup host is still running in the background they will get 0x87D00705 meaning setuphost was already running when trying to restart the upgrade. This error usually will self-resolve by itself allowing for a successful upgrade by waiting a few hours for setuphost to finish. What the end user would see at this point they “restart” the update, but it will evaluate and determine the update is installed and ready for a restart, once the restart occurs the device will upgrade and be on the next OS.
To view setuphost running Start > task manager > Processes Tab > “Setup host” or “Modern setup host”
Add comment