This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 3%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
Hello,
I have a problem with updating .NET SDK 8 on many server since June, apparently May's patch were installed as last, and from June servers don't report that they requires patch for this application.
We use SCCM for patching. I investigated it a bit and this is what I found:
BUT it works for .NET runtime 8.X, it updates properly each month for many servers:
What is the issue? For me it looks like MS bug, but anyone has similar problems and experience?
I don't see any another product in WSUS products which would cover .NET SDKs patching.
Hi, @Kuzik
Thank you for posting in Microsoft Q&A forum.
What's the version of the server that have the issue? Does this issue happen on all servers? Or most of the servers?
Can you see the 2024-08 .NET 8.0.8 Security Update for x64 Server (KB5042132) on your SCCM console?
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
Hi AllenLiu, thanks for reply,
Servers are 2019 (17763) and Windows 10 and 11 (VD) (19045, 22000 & 22631)
.net update is visible and downloaded and deployed to proper collection, but VMs are not visible as Required for this patch. Other host are there, but other hosts have installed other version than SDK package of .net 8
There is also no such BlockMU keys in registry:
https://devblogs.microsoft.com/dotnet/net-core-updates-coming-to-microsoft-update/
Have we tried to manually install the latest update to see if it can be installed successfully?
Now I did, below are results:
unfortunately after that server has two versions instead of one
SCCM has proper files on board:
the same files I've downloaded and installed on one of problematic servers from Windows Catalog
I also found another server and apparently .net SDK has been installed there via SCCM
So I think we should focus to find reason inside the problematic VMs, all of them are Azure VM, I don't know if that matters, probably not. What can block updating .net sdk locally on a server?
SCCM has the patch on board and its the same file which I've downloaded from Windows Catalog and manually Installed on one of problematic servers, but now there are two versions
SCCM directories:
Local server Downloads:
After manual installation:
In the meantime I found another server when apparently SCCM patching is working fine, so maybe we should focus on servers and how they are configured, and what can block this patching. Problematic servers are hosted in Azure, but probably it's not relevant.
It sounds very strange, SCCM shouldn't care if it's Azure VM or not.
Hi, so how can I investigate it? what is verifying to check .net package by sccm/wsus? registry? what keys?
Do other software updates can be installed on the Azure VM clients?
Yes, only this .net sdk is not reporting to be patched.
You may try to send a frown in SCCM console.
https://learn.microsoft.com/en-us/mem/configmgr/core/understand/product-feedback#send-a-frown