Microsoft released the latest Windows 10 cumulative update KB5005611 in preview. It seems there are some potential Fixes for Intune SCCM with Windows 10 Cumulative Update KB5005611. Let’s see whether I can check those fixes announced with KB5005611 are impacting Intune and Autopilot.
Microsoft released new Windows 10 patches for Insiders who can’t upgrade to Windows 11. The Cumulative Update patch KB5005611 is released for both Windows 10 versions 21H1 and 21H2. There are several fixes included in this KB.
The two fixes are interesting in terms of MDM device management and unattended out of box experience. I don’t know whether both are for known issues or not. In this post, we will check both of these fixes in detail.
Fixes Released with Windows 10 Cumulative Update KB5005611
The following are the two fixes related to SCCM Task Sequence and Intune MDM, as per my understanding. I had not seen or heard about these known issues before this KB article. This could be a Windows Autopilot known issue as well.
- Fixed an issue that changes the device’s current UI language. This occurs during an unattended out-of-box experience (OOBE) language pack installation scenario on a desktop.
- Fixed an issue that always reports the update build revision (UBR) as zero (0) on a device during enrollment to mobile device management (MDM) service.
I have checked the known issues with the SCCM task sequence because that is one of the workloads that help perform unattended OOBE language packs installation. Even though I initially thought this could be a known issue with Windows Autopilot. But I couldn’t find any resources online to prove that there are known issues. Let me know in the comments section if you know about this type of issue.
- Fix Windows Cumulative Updates are not Showing up in SCCM
- Windows 10 KB5005565 September Cumulative Update Released
- SCCM Patch Deployment issue with Windows 10 KB5004237 July Cumulative
- SCCM Patching Issue with Windows 10 KB5003637 June CU
- How to Fix Zero Day PrintNightmare Update Issue Uninstall Registry Group Policy
Fixed an issue that always reports the update build revision (UBR) as zero (0)
The issue “always reports the update build revision (UBR) as zero (0)” that Microsoft fixed with Windows 10 Cumulative Update KB5005611 (preview). This issue was clearly for MDM service enrolled devices. I went ahead and checked Intune enrolled devices to see whether there was an issue or not? Before getting into that details, let’s understand what update build revision is?
You might be wondering what UBR is? Well, UBR is the revision number of the Windows operating system. The revision number will get updated after each hotfix or LCU installation on Windows operating system. You can get more details bout Windows 10 Major, Minor, Build, and Revision numbers.
I have checked the following registry key to confirm the UBR version number and the MEM admin center (Intune) portal. The revision number for the KB5005611 is 1263, and the Windows 10 revision number for the reporting device in MDM is 1237. Hence that device is not installed with the latest preview KB; however, it’s reporting the correct revision number in the MDM portal.
- Registry -> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR
Conclusion
I couldn’t confirm the known issues and fixes highlighted in the KB500611 are related to Windows Autopilot, SCCM task sequence, and Intune MDM management. I may be missing something here. Or there could be a possibility that these issues are related to other workloads or products from non-Microsoft vendors.
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with over 17 years of experience (calculation done in 2018). He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…..…
thanks, that sure is a tad gooofy. I will install it based on some of the things you pointed out… just hope it doesn’t bite me in the posterior later…