/build/static/layout/Breadcrumb_cap_w.png

Script to uninstall a Windows update is not working.

Attempting to remove kb4560960, Kace SMA will say the script ran successfully but the update is still installed.  When running the command locally it works fine.  I found I had to use C:\Windows\Syswow64 or %WINDIR%\SysNative for it to not show an error on the deskop.

Here is what I'm running. 

%WINDIR%\SysNative\wusa.exe /uninstall /KB:4560960 /quiet /norestart

and

%WINDIR%\SysNative\DISM.exe /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.836.1.6 /quiet /norestart

Asked 3 years ago 1129 views
3 Comments   [ + ] Show comments
  • Did you try rolling back by using the patch engine, can the patch be rolled back? - Hobbsy 3 years ago
  • I'll try that - bharper 3 years ago
  • we are experiencing the same. It crapped out our PCL5 printers. If I run the wusa command by hand it just spits out the help screen like the arguments are invalid.

    I had to RDP into a handful of critical machines and uninstall via the gui to actually remove it. - roy.urick@koorsen.com 3 years ago

Answers (2)

Posted by: JLankford 3 years ago
White Belt
0
The /quiet switch may be suppressing your error, if you're getting one. Try adding the /log switch to write the job results to a file - that might help provide a clue as to why it's failing to uninstall.
Posted by: rad33k 3 years ago
Fourth Degree Brown Belt
0

As I remember the /quiet option cannot be used in combination with "/uninstall /kb:xxxx" on Windows 10:

npZlOp2duGy9TJMp+pzyuMrgCuSushEkAQC4RJsMkuZNNvp7fDe4WGFJmypOutnGW6aUIGmXJXdqezhjWElVK1ElZySTyhCqJ0ESAIBLtMEg2YpKDnsJkqaet4wgCQDApdpQkAxdx3fAklWVcRZyY8YztwRJAAAu0UaC5Jy0qWJCEgAA2DCCJAAAAIoQJAEAAFCEIAkAAIAiBEkAAAAUIUgCAACgCEESAAAARQiSAAAAKEKQBAAAQBGCJAAAAIoQJAEAAFCEIAkAAIAiBEkAAAAUIUgCAACgCEESAAAARYYg+f+Vkg3zj3VHewAAAABJRU5ErkJggg==

Have you checked the DISM log file? By default, if you do not specify /LogPath: switch, it is saved in %WINDIR%\Logs\Dism\dism.log

For the local tests, have you tried to uninstall it using psexec (-s), to make sure it works as a SYSTEM account?

I do not remember if all the updates are removed from the list right after the uninstall command is completed or after a reboot - worth to check too.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ