Windows 10 Feature updates can be tricky for many reasons. Fellow SC Dudes, Adam Gross, created a free and easy-to-implement solution to help debug and track down Feature Update logs. This solution will describe how to send SetupDiag Result in your SCCM Inventory during a Windows 10 Feature Update. Along with our previous post to track down Windows 10 Feature Update hard blocks, will greatly ease Windows 10 Servicing. Windows 10 SetupDiag SCCM Inventory Benefits Centralized log for any on-prem Feature Update attempt SetupDiag details stored in Hardware Inventory, which can be monitored by SQL query/reports and PowerBI While we recommend sticking to Feature Update to deliver new Windows 10 builds, this solution will work the exact same if a Task Sequence is used to do an upgrade. In this post, we’ll detail how to implement the Windows 10 Feature Update script to include it in your SCCM Inventory. This … Read More
Troubleshoot Windows 10 Update hard block
Windows 10 Feature Updates can be tricky to troubleshoot. The trick is to find relevant information about what’s causing the Windows 10 Feature Update to fail. In a previous post, we covered the Windows 10 Feature update error 0XC1900208. This is still accurate and possible that it happens for a Feature Update to Windows 10 20h2. We followed the instruction in the blog post to find what’s preventing the Feature Update to run. We start to test the Feature Updates from Windows 10 1809 to 20h2 at a client site. Our previous post was not helping, since running Setup.exe manually returned a restart error. We restarted the machine without success. This was not the problem. In this blog post, we’ll describe how to troubleshoot Windows 10 Update hard blocks using various methods. Troubleshoot Windows 10 Update hard block The first place to look is in the Windows Panther folder: Browse … Read More