Jump to content

Recommended Posts

Posted

Hi,

 

I cannot seem to find a solution to uninstalling Microsoft Word 2016 (KB4011039) 32-bit Edition update.

 

I have seen solutions where you type wusa /uninstall /kb:4011039 but the tool keeps reporting back saying that it does not exist, even though I checked it under the updates history.

 

This needs to be done in bulk, as it's causing a known issue where text is disappearing in text boxes - so it's not really do manually on every computer, and needs to be done quietly.

 

The Windows 10 Education build image is based on 10.0.14393 (Build 14393)

Posted

This worked for me (but very few W10 clients):

 

Go to WSUS>Updates and search for the update. If it's not there, maybe it's the earlier update (KB3213656) causing the problem? Right-click>Approve>Approve for removal and repeat to set the deadline in the past. Some clients had to manually force an update (to pull the removal) but these tended to be the "never turn my laptop off" types.

Posted

If you run

wmic qfe list brief /format:table

does it show it as installed still?

 

There were 2 patches that bugged it out, just the latest one was the 39 one. So might still have the other one installed

 

Steve

Posted
Thanks for the reply - but we have over 500 computers to do this on. We are looking for a command-line solution which we can then push out remotely through SCCM.
Posted
Thanks for the reply - but we have over 500 computers to do this on. We are looking for a command-line solution which we can then push out remotely through SCCM.

 

I think he was referring to WSUS server :p Not local updates. As in if you set it for removal server side it'll push out to clients.

 

Steve

Posted (edited)
If you run
wmic qfe list brief /format:table

does it show it as installed still?

 

There were 2 patches that bugged it out, just the latest one was the 39 one. So might still have the other one installed

 

Steve

Thanks Steve, I ran this - and the KB 4011032 didn't appear. It seems that the WUSA tool works, because it will work for any KB listed within that list. But this list contained just 5 updates, and in reality there are at least 20-30 updates installed if you go to the Update history section.

 

EDIT: just saw your reply - is there a command line version that can be run on the local machine (for example, on laptops which are off site)

Edited by vfong1982
Posted (edited)

Generic Powershell script I have in SCCM for stuff like this (*waves fist at Microsoft*)

 

$SearchUpdates = dism /online /get-packages | findstr "Somestring"
$updates = $SearchUpdates.replace("Package Identity : ", "") | findstr "KBXXXXXX"
DISM.exe /Online /Remove-Package /PackageName:$updates /quiet /norestart

 

Replace the "Somestring" with something unique in the update title, likely the KB or MS Security number. Only used this on Win10 as well.

Edited by Geoff
Posted

Came across this EDUGEEK solution, which references the update you want to remove...

 

[color=#333333]msiexec /package {90160000-0011-0000-0000-0000000FF1CE} /uninstall {A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qn /quiet /norestart

 

[/color]

  • 2 weeks later...
Posted

iI have declined the two updates in WSUS and set the deadline for yesterday.

That was a couple of hours ago and I have restarted my computer but the word doc is still missing stuff.

How do I know the update is definitely not there and if it isnt, what do i do next?

Posted

I don't think declining them actually removes them does it? (or did you approve for removal too?) They should just show up locally within the installed updates list on the client if they're still there

 

Steve

Posted (edited)

You are quite right - yes i did approve for removal as well (counter-intuitive to click on "approve" when you are trying to get rid of the damn thing!)

 

They are still on the client - now what?

 

*edit

 

The 32 bit version is on this computer - which is a 64 bit PC - so is that OK then?

Edited by witch
Posted
You are quite right - yes i did approve for removal as well (counter-intuitive to click on "approve" when you are trying to get rid of the damn thing!)

 

They are still on the client - now what?

 

Does it show them as having a built in remove option via WSUS? See them via SCCM so see different values, but it should show if they're removable via WSUS under additional details in the update list

 

I assume aswell that the machines are set to query WSUS after the time it was set to do? Just in case they were turned off etc at that time

 

Steve

Posted
You are quite right - yes i did approve for removal as well (counter-intuitive to click on "approve" when you are trying to get rid of the damn thing!)

 

They are still on the client - now what?

 

*edit

 

The 32 bit version is on this computer - which is a 64 bit PC - so is that OK then?

 

I've not installed the 64 bit Office anywhere yet, but "Approving for removal" (you're right - totally counter-intuitive) of the 32 bit version removed it from machines of both bitness.

 

P.S. what's you're update schedule? Might be worth manually updating the client, which should force the uninstallation.

Posted

I rolled the following command out via a package in SCCM and this has worked fine on our site:

 

msiexec.exe /package {90160000-0011-0000-0000-0000000FF1CE} MSIPATCHREMOVE={A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qb /norestart

Posted

It all worked eventually and I got described as a "savour" by the HT. Which was nice

 

He also said: "I never would have found that issue"...well, no, that's why you pay me the big bucks ( *irony)

Posted

Sorry late with this but the simple cmd i used for uninstalling updates

START "" /WAIT %WINDIR%\System32\wusa.exe /uninstall /KB:4011039 /quiet /norestart

Posted

I have used following in a batch file then ran as Startup Script via GPO

 

start "" /wait %systemroot%\system32\msiexec /package {90160000-0011-0000-0000-0000000FF1CE} MSIPATCHREMOVE={A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qn
start "" /wait %systemroot%\system32\msiexec /package {90160000-001A-0409-0000-0000000FF1CE} MSIPATCHREMOVE={A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qn
start "" /wait %systemroot%\system32\msiexec /package {90160000-001B-0409-0000-0000000FF1CE} MSIPATCHREMOVE={A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qn
start "" /wait %systemroot%\system32\msiexec /package {90160000-012B-0409-0000-0000000FF1CE} MSIPATCHREMOVE={A36375BB-E79D-411D-BF1E-C7E8120A08A9} /qn

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...