Forum Discussion
Software updates stuck at 0% Downloading
We have new SCCM environment 1910 version. Testing software updates on some test machines. On all Win 8.1 test machines, patches got installed. On all Win 10 machines updates are stuck at 0% downloading. All these Win 8.1 and Win 10 machines are in same subnet and checked for boundary and boundary groups. Please let me know what else i have to check or verify.
you may also want to check to see if you have "Allow clients to download delta data when available" in the client settings. to help narrow down the issue.
- Shane KrummenCopper Contributor
you may also want to check to see if you have "Allow clients to download delta data when available" in the client settings. to help narrow down the issue.
- chandrabusaCopper Contributor
Shane Krummen Thank you very much. The setting was set. Once i changed the setting to No, I was able to install patches on Win 10 machines. I am not sure why this would cause the issue only on Win 10 machines not on Win 8.1 machines.
- Michael_CuretonMicrosoft
chandrabusa just curious, are you installing o365 updates?
- robMgCopper ContributorThanks! this fixed my issue.
- Simon_HoCopper ContributorHi Chandrabusa,
Have you checked the Certificates are correct on the client?
While upgrading the SCCM Server the Public Key Cert changes.
You need to reflect the change on the Agent install scripts for the clients.
Cheers
Simon - Akshay_ManeIron Contributor
We have recently been experiencing this issue on seemingly random devices as well.
Not sure exactly why this happens, but the following seems to resolve the issue in our environment without having to uninstall the client:
Stop the SMS Agent service
Stop the Windows Update service
Rename C:\Windows\SoftwareDistribution to something else (i.e. SoftwareDistribution.old)
Start the SMS Agent service again
- JRoman2067Copper Contributor
Akshay_Mane , Thank you for the recommendation. I applied what you did and add; the following steps as well.
1.Stop Background Intelligent Transfer Service
2. Stop Cryptographic Servicesand this works for our environments.
Thank you
- midhunkollamCopper ContributorI have faced same issue for only one machine. Just created a separate boundary with IP address range for that server and assigned to the group. Make sure that boundary is not overlapping between the groups. Its worked fine..