-
Title
Failed Windows Feature Update (WFU) for Windows 10: How to find blocking components? -
Description
Windows Feature Update deployment from the Kace SMA failing due an incompatible component on the target machine.
The information below is gathered from 3rd party resources.
Feature update for Windows 10 failed: find blocking components
Quest is providing these details to assist with troubleshooting and they have not been tested by our QA department. If there are any questions or concerns, KACE Technical Support can assist with log gathering and reading.
-
Cause
Windows Feature Update could fail if it encounter a hardware of software component on the machine that is not compatible with the version of Windows that is being deployed to the machine. Usually there is not enough info on the Kace SMA or in the agent logs to find exactly why the upgrade failed.
Common errors:
- “This PC can't be upgraded to Windows 10. Your PC settings aren't supported yet on this version of Windows 10.”
- “Your PC may not be supported yet on this version of Windows 10. Makes sure that you are connected to the internet, then try installing the update again.”
-
Resolution
Windows Update writes different log files in different formats in several places, and it could be difficult to find what is causing the failure.
Additional logs and details can be found on the following directory:
"C:\$windows.~bt\sources\panther"
There are several files in different formats. The most important ones are:
- CompatData (The most recent one usually have more info about why the update failed).
- setup-etl
- setupact.log
- setuperr.log
Look for entries on the CompatData file saying BlockMigration=”True”. If nothing is found on this log, try with the other logs mentioned before to try to find a possible root cause.
The same process could be done using a PowerShell command to search in all the files at the same time:
- gci CompatData*.xml | Select-String 'BlockMigration="True"'
In this example, there are two compatibility issues, referring to the files "oem45.inf" and "oem46.inf". The next step is to examine these files to find out which components are causing problems. To do this, go to the directory %systemroot%\inf or C:\Windows\INF.
On this machine “Oem45.inf” is “Microsoft Print to PDF” and “Oem46.inf” is "Microsoft XPS Document Writer".
- The removal of these Windows optional features is required before the next feature update attempt.
If the entry shown is a third party component, confirm with the vendor if the component is compatible with the version of Windows deployed. If the component is not compatible, you might need to remove it to complete the update.
As an additional measure, delete "compatscancache.dat" and run the Windows Feature again.
External USB devices, memory cards connected to the device could also affect the Windows Feature Update process. A Hard disk drive (HDD), pen drive, SD card, etc. could cause a compatibility issue as well.
To resolve this issue, just remove all external media from the computer and restart the machine. After reboot, try to run Windows Feature Update again.
You can also use Microsoft's tool "SetupDiag " which is a diagnostic tool that can be used to get details about why a Windows 10 upgrade failed.
SetupDiag works by examining Windows installation log files. It attempts to analyze these log files to determine the root cause of a failed update or upgrade of the computer to Windows 10. SetupDiag can be run on the computer that could not be upgraded. up to date, or you can export the computer logs to another location and run SetupDiag offline.