HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\ default\Update #Lists the policy locations for Windows Updates Open Task Scheduler and you will find the Microsoft Compatibility Appraiser task under Task Scheduler Library>Microsoft>Windows>Application Experience I’ll break down the pieces that I have put together, but I still feel like this a ‘black box’ that I don’t fully understand. Whether you are aware of it or not, your Windows 10 device is actively assessing your device’s compatibility with Windows releases (possibly other monthly updates as well). So, I mentioned the Microsoft Compatibility Appraiser in the previous section. Work is still being done with DA, so I think there’s hope for integrating more data in the future. It doesn’t include details specific to the blocking app. The shortcoming with DA is that is simply reports back what the Microsoft Compatibility Appraiser reports. We have been using this (And Windows Analytics before DA) since it was released and it has almost eliminated the need for testing ALL of our applications before deploying the latest Feature Update - we still test critical apps. If you are an enterprise customer and are fortunate enough to use ConfigMgr, you can leverage Desktop Analytics to assess device and app compatibility BEFORE attempting to install feature updates. It can appear in the setup UI if you are manually running setup.exe or in c:\$WINDOWS.~BT\Sources\Panther\ActionableReport.html. It is very generic and less than helpful. Presenting a message telling us that we are blocked, but providing no actionable information is less than helpful. Everyone was asking - ‘Why am I blocked?’. When Windshipped, the internet filled up with reports of people getting messages indicating that their devices couldn’t be upgraded. Automate the collection and assessment of Feature Update blocks using custom PowerShell module FU.WhyAmIBlocked.Understand how to manually convert Appraiser results to XML then compare to the Windows Compatibility Database (appraiser.sdb).Gain a better understanding of Feature Update blocks that prevent devices from upgrading - sometimes blocking the update from even showing up on the device as available.I want to highlight the main points to keep things from getting lost in the pile. Last things FirstĪfter writing this, I realized that I have crammed a lot if stuff in here. It will also contain some best guesses for how some things work where I may not have a 100% clear understanding. This post is a deep dive into my experience with identifying Hard Blocks and making sense out of generic error messages like the one below. When your boss has a Surface Pro 7 that can’t upgrade to the latest feature update, you’re not going to have a good time. When Windwas released, there was a block in place for certain hardware models including the Surface line. Microsoft has gotten a little better with this area by keeping this site updated, however from a client installation perspective, it is often difficult or even impossible to match up an error message/code with anything published on that site (or any other Microsoft site). The flaw in this feature is the lack of visibility into what is being blocked and how/when it should be unblocked. This is a pretty great feature since it helps prevent unnecessary failures for already known issues that Microsoft is possibly already working to address. For each release, Microsoft has the ability to block the update from being installed or even showing up in Widows Update for applications/drivers/devices that have known compatibility issues. Windows 10 Feature Updates are released twice per year. This information is provided for educational purposes only. The blocks exist for a reason and should be respected. Using SCCM Task Sequence Variables as Scriptsĭisclaimer - if you manually bypass Feature Update blocks, you risk causing issues with your device.Triggering ConfigMgr Client Actions from a Task Sequence.Dynamically Updating Unattend.XML during an OSD Task Sequence using MDT Variables and ZTI Scripts.Debugging SCCM/ConfigMgr Task Sequences on the Fly.Clearing Local Group Policies during an Windows 7 to 10 In-Place Upgrade Task Sequence.Part 5 – Dynamic Whitelisting using the Cisco ISE External RESTful Service.Part 4 – Integrating 802.1x Authentication into an In-Place Upgrade Task Sequence.Part 3 – Integrating 802.1x Authentication into a Bare Metal Task Sequence.Part 2 – Building an 802.1x Enabled WinPE Boot Image.Part 1 – Building an 802.1x Computer Authentication Script.Windows 10 Feature Updates – Using Setupconfig.ini to Manage Feature Updates in the Enterprise. Windows 10 Feature Updates – Using Custom Action Scripts.Windows 10 Feature Updates – The Challenge of Servicing in the Enterprise.Windows 10 Feature Updates – Leveraging SetupDiag for Better Reporting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |