Let’s check how to fix SCCM WSUS Sync Failed issue. Today Morning, the ConfigMgr community started reporting WSUS Sync failed with UssInternalError SoapException Error 0x80131500.
Microsoft MVP Panu Saukko reports that the SUP server failed to sync after 04/08 01.00 am (his local time).
I tried to run WSUS Sync in my lab environment, and I couldn’t reproduce the sync issue. The issue is not there for all the SCCM/WSUS environments.
I think the impact is there when you have enabled some of the Dev Tools product categories from the products list. More details are in the below section of the post.
The following screenshot is taken from Panu’s tweet and gives you an idea about the WSUS sync error from Wsyncmgr.log.
- Intune Pivot Query Real-time Reporting Troubleshooting Capabilities
- Configure Azure Bastion Developer SKU for Low Cost Secure Connections
- Intune Policy to Enable Interactive Logon Do Not Display Last Signed-in
- Intune Anomaly Detection Device and Advanced Analytics
- Major Issue Printers Getting Renamed to HP LaserJet M101-M106 in Windows 10 11 and Server OS
Workaround SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500
The workaround solution was provided by Sr. Support Escalation Engineer Vinay Pamnani. You have to follow the steps mentioned below to work around this issue.
- Navigate to \Administration\Overview\Site Configuration\Sites
- Select the Standalone Primary server -> Configure Site Components -> Software Update Point
Click on Products Tab. You need to uncheck Visual Studio 2017 and 2019 from the Developer category of products.
- Click OK to save the setting.
Navigate to \Software Library\Overview\Software Updates\All Software Updates. Initiate a manual WSUS sync to check whether the WSUS sync is going to work or not.
Monitor the WSUSSyncMgr.log to confirm the sync status.
FIX SCCM WSUS Sync Error 0x80131500
Microsoft is yet to come up with a fix for SCCM WSUS Sync failed with UssInternalError SoapException Error 0x80131500. I will keep you posted if I see more updates on this topic.
Update 09 April 2021 – The issue is fixed as per David James tweet.
We believe this should be resolved now for everyone, without any manual workaround. If you experienced an issue before and didn’t do the workaround, just trigger sync and verify it is working. Customers that didn’t notice the issue should silently recover on the next sync.David James Tweet
David James shares another piece of news that begins next week (patch Tuesday), you can patch VS through WSUS and ConfigMgr (only security updates via SCCM). The backend changes related to these Visual Studio updates caused major issues with WSUS Sync.
You can deploy Visual studio updates with SCCM now. Feature Pack and regular updates of Visual studio are available in SCCM using the manual import method.
Let’s have a quick look at the WSUS Sync issue reported today morning.
Microsoft Released Fix for WSUS Sync Issue?
NO, they are still working on the fix.
Root Cause of WSUS Sync Issue?
There is no public information released about this issue.
Did Microsoft provide a Workaround for this issue?
Yes, that is to uncheck Visual Studio 2016 and 2019 products.
Is this WSUS Sync issue impacting all environments?
No, it impacts only the environments where Dev tool updates are selected.
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. 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.