Content Modification: Patches for Windows published 2021-09-24

Release Announcements Patch (Release Announcements)
1

Content in the Patches for Windows site has been modified

New:

  • Major (ID:500562403) 5005624: Cumulative Update Preview for Windows 10 Version 1909 - Windows 10 Version 1909 - KB5005624
  • Major (ID:500562401) 5005624: Cumulative Update Preview for Windows 10 Version 1909 - Windows 10 Version 1909 - KB5005624 (x64)
  • Major (ID:500562505) 5005625: Cumulative Update Preview for Windows 10 Version 1809 - Windows 10 Version 1809 LTSC - KB5005625
  • Major (ID:500562501) 5005625: Cumulative Update Preview for Windows 10 Version 1809 - Windows 10 Version 1809 LTSC - KB5005625 (x64)
  • Major (ID:500562503) 5005625: Cumulative Update Preview for Windows Server 2019 - Windows Server 2019 - KB5005625 (x64)

Reason for Update:

  • New updates for windows 10 version 1809 and version 1909

Actions to Take:
None

Published site version:
Site Name: Patches for Windows
Version: 3850

Additional links:

Application Engineering Team
HCL BigFix

2

I am getting the below error on server 2019 when try to install the patch manually on the server:-1:

Windows update “Update for Windows (KB5005625)” could not be installed because of error 2147943409 “The configuration registry database is corrupt.” (Command line: "“C:\Windows\system32\wusa.exe” “C:\Temp\windows10.0-kb5005625-x64_9a7d6abe389d940e08d759243c981670c33c71f5.msu” ")

Any suggestions?

Ty

3

This is not typically a good message to be seeing. :frowning: The message is not anything specific to BigFix, but from the OS.

Usually you can identify and correct these types of errors by running the OS built-in tools SFC (System File Checker) and DISM (Deployment Image Servicing and Management).

As always, please use your best judgement before running any commands on a server. Only you know how it is configured and what might cause issues. This is purely a suggestion of what may help.

Start by performing a sfc scan of the system. From an Administrator command prompt:

C:\Windows\System32> sfc /scannow

Note, this scan could take some time and may require a reboot. DO NOT INTERRUPT this command while it is running.

Try and re-deploy the update at this point to determine if it resolved the matter. If not, you may need to use DISM. Due to the nature of how DISM works, I will leave it up to you to research this utility so you can fully understand the potential risks. The commands you will want to lookup are Cleanup-Image and ScanHealth.

2 Likes
4

This topic was automatically closed after 30 days. New replies are no longer allowed.