Here at Tech With a Hammer we have found a few of our clients use volume licensing from Microsoft for their Office 2016 installations and were affected by the notorious update KB4011039, which was supposed to be a security update for Word 2016. The following hammer can be used to automate the uninstall process.
The bug that was first produced in KB3213656 is back, this time in KB4011039. In Word 2016 this bug will cause any vertically merged cells to not display their contents and not allow you to click on the cell to edit. It can be tabbed into from an adjacent cell, though without being able to see what is being entered might as well forget it. As Outlook 2016 also relies on the same code that Word uses to draw the page, this bug also affects Outlook.
With our clients there is a mixture of architecture of installations, we normally recommend hammering in 32-bit Office due to compatibility, though compatibility issues with other applications are the reason 64-bit is installed in a few places.
To uninstall manually using command line, you can use the following snippets
|
1 |
"C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\Oarpmany.exe" /removereleaseinpatch "{90160000-0011-0000-0000-0000000FF1CE}" "{A36375BB-E79D-411D-BF1E-C7E8120A08A9}" "1033" "0" |
|
1 |
"C:\Program Files\Common Files\Microsoft Shared\OFFICE16\Oarpmany.exe" /removereleaseinpatch "{90160000-0011-0000-1000-0000000FF1CE}" "{37811086-784B-4EB8-B009-09DF9278ED9F}" "1033" "0" |
For unattended uninstalls of the KB the following commands can be used
|
1 |
msiexec.exe /package "{90160000-0011-0000-0000-0000000FF1CE}" /uninstall "{A36375BB-E79D-411D-BF1E-C7E8120A08A9}" /qb |
|
1 |
msiexec.exe /package "{90160000-0011-0000-0000-0000000FF1CE}" /uninstall "{37811086-784B-4EB8-B009-09DF9278ED9F}" /qb |
Most uninstalls we would automate with a /qn instead as it implies quiet with no UI, it has been reported that this fails without much of a reason though success was found using /qb, a basic UI that states it is being uninstalled.
For the install and uninstall of updates for volume licensed Office products this can be done with either executable, though documentation for Oarpmany.exe does not exist at this time so I would recommend using msiexec if you do not have a way to manage your installed products across your network, though we recommend that you hammer in an SCCM, System Center Configuration Manager, into your network if you are managing only a single enterprise.
To use msiexec the package is the GUID of the target application, and then the /install or /uninstall is the GUID of the patch itself. The GUID for x64 and x86 systems will differ, as can be seen above.
|
1 |
msiexec.exe /package "{Office_Application_GUID}" /install|/uninstall "{Update_GUID}|Update.MSI|Update.MSP" /qb |
By browsing to the uninstall node for your version of installed software you can find the GUID for many installed Microsoft applications and their updates
|
1 |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ |
|
1 |
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ |
The uninstall keys for the patches were found in these keys by performing a search for the KB number 4011039. Each patch will contain a string labeled UninstallPath which can be run, though for many of the Office 2016 patches they use the Oarpmany.exe patcher provided with volume licensed Office 2016.
The uninstall key for the patch on 32-bit Word was found at
|
1 |
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90160000-001A-0409-0000-0000000FF1CE}_Office16.PROPLUS_{A36375BB-E79D-411D-BF1E-C7E8120A08A9} |
While the uninstall key for the 64-bit patch was found at
|
1 |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90160000-0011-0000-1000-0000000FF1CE}_Office16.PROPLUS_{37811086-784B-4EB8-B009-09DF9278ED9F} |
Hi, I tried the unattended command and it says I do not have a valid product. 0armany.exe command however works. Am I missing something?
When would we use /uninstall and when should we use MSIPATCHREMOVE with msiexec?
Thank you in advance for reading my comments.
Found we had a similar issue on a few workstations, for the msiexec command to work we had to manually install the KB and then we were able to uninstall using msiexec.
As for MSIPATCHREMOVE, we have found that recent patches for click-to-run Office 2016 failed to uninstall and sometimes causes issues where it will remove information for the offending patch/KB from the registry but not the files themselves. If you do not mind the prompt that comes up, stick with using 0armany.exe, it is not an unattended method but for one-off circumstances where a patch gets stuck.
Thanks man, you save me a lot of time!
Worked perfectly. Thank you!