AJK Posted March 10, 2021 Share Posted March 10, 2021 I'm trying to run just a simple wusa /uninstall /kb:5000802 script in a task but the task just hangs forever and never makes progress on the machines. I don't have too much experience running any type of scripting through an RMM so any help would be greatly appreciated. Link to comment Share on other sites More sharing options...
AJK Posted March 10, 2021 Author Share Posted March 10, 2021 Came across this which seems to work if anyone else is having the same issues still: # "19041.867.1.8" = KB5000802 # "18362.1440.1.7" = KB5000808 $UpdateArray = @("19041.867.1.8", "18362.1440.1.7") foreach ($UpdateVersion in $UpdateArray) { $SearchUpdates = dism /online /get-packages | findstr "Package_for" | findstr "$UpdateVersion" if ($SearchUpdates) { $update = $SearchUpdates.split(":")[1].replace(" ", "") write-host ("Update result found: " + $update ) dism /Online /Remove-Package /PackageName:$update /quiet /norestart } else { write-host ("Update " + $UpdateVersion + " not found.") } } exit 0 Paul 1 Link to comment Share on other sites More sharing options...
ArrowNM Posted March 13, 2021 Share Posted March 13, 2021 Perhaps this could help, This may prevent it from being pushed out in the future. Assuming Microsoft will release a permanent fix soon. Under Patch Management select Policies you can edit your policy under OS Rules by adding two new rules then move them to the top of your list. If Name contains kb:5000802 then Don't Install If Name contains kb:5000808 then Don't Install Please view the attached screenshot. Link to comment Share on other sites More sharing options...
colsen Posted March 23, 2021 Share Posted March 23, 2021 Hello, does anyone know how to trigger the optional update to fix this issue? I've tried changing my Policies to contain the KB number and allow and install but it hasn't triggered the update. Link to comment Share on other sites More sharing options...
Administrators Paul Posted March 23, 2021 Administrators Share Posted March 23, 2021 Hi @colsen, We've released today an update to the Windows Agent (v8.6.6) which detects the optional update released by Microsoft. It should reach your systems within 36 hours. -Paul Link to comment Share on other sites More sharing options...
colsen Posted March 24, 2021 Share Posted March 24, 2021 Thank you for your response Paul, I greatly appreciate hearing this. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now