Registry('HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\AppCompatFlags\\TargetVersionUpgradeExperienceIndicators\\*\\') | where Property = 'GatedBlockId' and Value != 'None' In our case, we look for 30103339 CMPivot query to return GatedBlockIDsĪgain, thanks to Adam Gross, here’s the CMPivot Query to find the GatedBlockID value. Searching this page with the GatedBlockID code will lead to the description of the problem. Those are centralized under the known issues of the Windows 10 release. Finding GatedBlockID meaningĮach number in that registry key refers to a specific problem. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\20H1. On the device that failed to run the Feature Update, those can be found in the registry under : A feature to avoid installing feature updates while some key component on a system would break Windows 10 in a way or another. With the precious help of fellow SCD Adam Gross, here are other ways to reach and find what is going on with some Windows 10 hard blocks.
End result, changing the local administrator account back to its default name as described in the article resolved the Windows 10 feature Update error.SIDs and RIDs for built-in user accounts are well-known as documented here and must be unique on a given device. This issue is caused by duplicate built-in user accounts being created with the same security identifiers (SIDs) and relative identifiers (RIDs) during the update to Windows 10, version 20H2.
For more details, see the full KB release This article was released about a month ago.I didn’t have a lot of fate via the Learn More Microsoft link, but to my surprise, it ended up being spot on! In this particular case, the result isn’t exactly clear on what is preventing this Windows 10 20h2 Feature Update to happen.Open up the CompatData file having the most recent date with a browser, since those are XML, it’s easier to read.Browse to C:\$WINDOWS.~BT\Sources\Panther and look for CompatData files.The first place to look is in the Windows Panther folder: Troubleshoot Windows 10 Update hard block
In this blog post, we’ll describe how to troubleshoot Windows 10 Update hard blocks using various methods. We restarted the machine without success. Our previous post was not helping, since running Setup.exe manually returned a restart error. We start to test the Feature Updates from Windto 20h2 at a client site. We followed the instruction in the blog post to find what’s preventing the Feature Update to run. This is still accurate and possible that it happens for a Feature Update to Windows 10 20h2. In a previous post, we covered the Windows 10 Feature update error 0XC1900208. The trick is to find relevant information about what’s causing the Windows 10 Feature Update to fail. Windows 10 Feature Updates can be tricky to troubleshoot.