Product Version: 6.5.0.0
Overview
Ensuring the resolution of Windows Update issues is imperative, as Saner CVEM relies on Windows Update-related services and APIs to download and install patches effectively. This article outlines several troubleshooting steps and solutions to address Windows Update issues on affected devices.
Troubleshooting Steps
1. Remove WSUS Registry Entries
Devices configured with WSUS registry entries may experience communication issues with the Microsoft Update server. To resolve this, deploy or manually execute the following registry script:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"=-
"WUStatusServer"=-
"EnableWindowsUpdateAutoUpdate"=-
For additional information, refer to the KBA: Deploy reg files to disable WSUS in the registry editor
2. Reset Windows Update Components
Resetting the Windows Update components can help resolve common update errors. Run the following commands sequentially:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Tip: Save the above commands as a .bat file and execute it manually or deploy it via Endpoint Management (EM).
3. Alternate Reset Method
If the above script does not resolve the issue, use the alternate method below:
Stop the update services:
net stop wuauserv
net stop cryptSvc
Rename the update folders:
Restart the services:
net start wuauserv net start cryptSvc
4. Verify GPO and Local Policies
Ensure that no Group Policy Objects (GPOs) or local policies are applied that interfere with Windows Updates. All related settings should either be Not Configured or Disabled. Refer to the attached screenshots or documentation for further clarification.
Conclusion
Following the above steps helps restore Windows Update functionality and ensures seamless patch deployment through Saner CVEM. If the issue persists, collect the relevant logs and contact SecPod Support for further assistance.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article