ConfigMgr Frontline

Why do my Windows 10 2004, 20H2, and 21H1, and 22H2 systems continue to show compliant even though I've deployed the Feature Update to 22H2, and they are clearly NOT 22H2!? Make sure you are also deploying the Windows 10 22H2 Enablement Package! Enablement package? Each time a monthly cumulative update gets installed, it includes files from the upcoming Feature Update. These files are stored on the drive and include the updates for the next Feature Update. In October 2022, all the pieces were in place for Windows 10 22H2. Microsoft then released "Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package". (One for each CPU architecture.) So, in ConfigMgr add the enablement package to your deployment (it is language agnostic) and let it fly. The enablement package is about 2mb and takes only a few minutes and a reboot. Here is some more information about the enablement package. Note: Any Windows 10 version prior to 2004 can't use the e

 While attempting to upgrade SSMS to version 18.11.1, it kept failing with a very odd error I'd never run across before.  "MainViewModel.OnBundleAction: Bundle action failed: Fatal error during installation (0x80070643)" After trying many of the tips on the web like updating Visual C++ Redistributable, running a .NET repair, etc., I finally found the solution. I fired up trusty old Procmon64 and let it capture while I attempted to install SSMS 18.11.1. Once it failed, I went to Tools \ Count Occurrences and chose "Result".  The count showed 222 "Access Denied" results. I double-clicked that line which took me to the list of "Access Denied". I found the ones that were the culprit. Evidently, SSMS 18.11.1 needs to install some help files and it couldn't access the HelpLibrary2 folder. My assumption was the permissions were incorrect, so I addressed that by running the following command from an elevated CMD prompt: icacls.exe C:\ProgramData\