📎 AI Summary:
The forum thread discusses downloading and installing a Microsoft security patch (KB5004945) to address a recent vulnerability, with users confirming successful updates on Windows 10. The original poster inquires about patching Windows 7, but is informed that it is no longer supported and cannot be patched, though some mitigations are suggested. The overall sentiment highlights cautious optimism about the patch's effectiveness, with added concern that the vulnerability may still persist despite updates, leading to questions about safety in delaying printing until proper patches are implemented.
The forum thread discusses downloading and installing a Microsoft security patch (KB5004945) to address a recent vulnerability, with users confirming successful updates on Windows 10. The original poster inquires about patching Windows 7, but is informed that it is no longer supported and cannot be patched, though some mitigations are suggested. The overall sentiment highlights cautious optimism about the patch's effectiveness, with added concern that the vulnerability may still persist despite updates, leading to questions about safety in delaying printing until proper patches are implemented.
Solution
- Joined
- Jul 4, 2015
- Messages
- 8,995
The patch does not provide full protection from the CVE but the patch is here
You will need to download the correct patch for your particular build which you can identify by
You will need to download the correct patch for your particular build which you can identify by
- Press [Windows key + r]
- Type winver
- Make note of the version such as 1809, 1903, 20H1,21H1
- Download and install the appropriate patch
Thanks. I followed the link and found appropriate download column. I click on it and another window opens. I clicked on that and no download starts. Again, must I be on administrator account to do this download?
Well someone on Newsmax should quit telling people to get it for win7. Not your issue obviously. Anyway, I just read a rundown on this thing and it still has vulnerabilities. There are mitigations that may help but it sounds like it's only temporary. A few of the fixes are going into the registry and inserting 0's - anyway, sounds like MS has not really patched this properly., Thanks again.
- Joined
- Jul 4, 2015
- Messages
- 8,995
If you disable the print spooler yes. This would need to be run from an elevated Powershell prompt.
Work-around to protect yourself from the issue
Work-around to protect yourself from the issue
Code:
Stop-Service -Name 'Spooler'
Set-Service -Name 'Spooler' -StartupType Disabled
Re-enable the service
Start-Service -Name 'Spooler'
Set-Service -Name 'Spooler' -StartupType AutomaticI found a site that took me thru the steps to disable it which I did. They also said to go to properties and a tab for service status - here you are to click STOP in order to disable. Very confusing - it is disabled but I couldn't do the 2nd part (STOP) as the tab didn't show up in the properties menu. Anyway, I checked the printer status this morn and it says DISABLED. So hopefully, this took care of problem vulnerability. The following site is what I followed: security.uchicago.edu/printnightmare. Thanks.
Similar threads
- Article
- Article
- Article
- Article