𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺]

Beta Engineering | MSFT | ConfigMgr & Intune | Debug & Reverse Engineering.

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

Heads up...   
As part of fixing the issue the below update still remains unpublished.
July 8, 2025-KB5056580 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 and Windows 11, version 23H2 and it would be published soon after correction. 


[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

The 2 updates which caused this were belonging to the product Microsoft.NetFX.arm64 which comes under ���Windows 11” product category and “Updates” classification. Disabling that classification might still not help until the backend gets stabilized to handle catalog syncs.

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

@jarwidmark Yeah that and when WannaCry hit were two defining moments where the ticket floods got opened. :)

[Johan Arwidmark @jarwidmark]

Brings back memories from 2018 when a bad component (outdated appraiser.dll) forced every client to download the full catalog (which was massive for orgs that haven’t cleaned up)… I did not sleep much for a couple of weeks…

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

The public comms were sent at M365 admin portal a while ago. We have reports of some successful syncs happening including my lab as the backend is getting stabilized. If the perf error is gone but you still see the bad revision error then likely uncheck the updates classification

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

The 2 updates which caused this were belonging to the product Microsoft.NetFX.arm64 which comes under “Windows 11” product category and “Updates” classification. Disabling that classification might still not help until the backend gets stabilized to handle catalog syncs.

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

WSUS sync issues. Teams still investigating the cause. Preliminary findings likely point towards some bad revisions might have caused the delta sync to fail triggering full sync and making catalog servers unresponsive. #ConfigMgr #WSUS

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

WSUS sync issues. Teams still investigating the cause. Preliminary findings likely point towards some bad revisions might have caused the delta sync to fail triggering full sync and making catalog servers unresponsive. #ConfigMgr #WSUS

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

@lalanc01 PXE clients remain stuck in "Waiting for Approval" after upgrade to CB 2503
PXE task wizard doesn't work with 'no password' in 2503
It shared the same root cause which is fixed now.

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

This one has the PXE fix which was encountered in the Fast ring!

[The ConfigMgr Team @MSConfigMgrTeam]

📣 We are proud to announce the release of Microsoft Endpoint Configuration Manager 2503! 🎉

Slow ring rollout starts today - Keep an eye on your console for the update!

➡️ Learn more: https://t.co/kNPdEs6UA5

#ConfigMgr #MSIntune

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

Happened to be in India so glad to talk about UUP OnPrem internals , troubleshooting common issues and some pain points about windows scan source policies and changes coming in 2409. #ConfigMgr #SCCM

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

Happened to be in India so glad to talk about UUP OnPrem internals , troubleshooting common issues and some pain points about windows scan source policies and changes coming in 2409. #ConfigMgr #SCCM

[HTMD Community @htmdcommunity]

🎇We are delighted to welcome Umair Akhtar Khan, Senior Support Escalation Engineer and BETA Lead at Microsoft, to our event. Umair is a true champion of diversity and inclusion in endpoint management, Join us to learn from their unique perspective.

[The ConfigMgr Team @MSConfigMgrTeam]

Microsoft has released Update 2409 for Configuration Manager (CB). This update brings features and improvement but requires you to run an opt-in script to make it available in your environment. After few weeks it will be published GA.

https://t.co/rf87pFbIXd

#Configmgr

[Balasubramanian Delli @Bala_Delli]

What’s New in ConfigMgr Technical Preview 2411:
Windows 11/Server 2025 Support and CMG Enhancements

#configMgr

https://t.co/WmyFqdaJSF

[The ConfigMgr Team @MSConfigMgrTeam]

We have released 2403 HFRU today.

Update rollup for Microsoft Configuration Manager version 2403.
https://t.co/1YSQJ9dLUl

[Bryan Dam @bdam555]

Oh fun, another #ConfigMgr hotfix was released today, this one addressing CVE-2024-43468, a vulnerability with the Management Point's connection to the site server database
MS suggests using a service account instead of the machine account to access the DB
https://t.co/39KcqxoSFY

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

@znackattack No don’t think it is planned for 2309 as this is an interim fix. A better fix is planned in 2409 (or HFRU)

[Microsoft News and Stories @MSFTnews]

Read an update on what we’ve done to help Microsoft customers recover from the recent CrowdStrike outage. Learn about our actions from the start of the incident and our collaboration with customers, cloud providers and others in the tech community. https://t.co/7lS3zl32ww

[Rashid Siddiqui @rashid29]

We are looking for a Solid ConfigMgr troubleshooter.

https://t.co/MU381WO84G

[The ConfigMgr Team @MSConfigMgrTeam]

We have released an OOB fix applicable for CMG VMSS customers - KB 28290310. Please update so that the VM Build upgrades to 20348.2402.

CMG update for Microsoft Configuration Manager version 2403 - Configuration Manager | Microsoft Learn

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

@sassan_f @PerLarsen1975 I know the team was made aware of this and there were discussions but don’t think there is a fix as yet.

[𝚄𝚖𝚊𝚒𝚛 𝙺𝚑𝚊𝚗 [𝚄𝙺] @UmairMSFT]

The #ConfigMgr support team has been aware of an issue in the 2309 HFRU/2403 for comanaged clients managing defender from Intune are having the defenders settings cleaned up by ConfigMgr. The cause is understood and We are still working on this and current workaround include 1/2

[Windows Update @WindowsUpdate]

An Out-of-band (OOB) update is now available for Windows 10 Enterprise and IoT LTSC 2019 editions and Windows Server 2019 to address installation failures of the May 2024 security update.