{"id":4266,"date":"2018-07-31T14:24:20","date_gmt":"2018-07-31T18:24:20","guid":{"rendered":"http:\/\/batchpatch.com\/?p=4266"},"modified":"2018-07-31T14:25:08","modified_gmt":"2018-07-31T18:25:08","slug":"removing-a-microsoft-office-update-from-multiple-computers","status":"publish","type":"post","link":"https:\/\/batchpatch.com\/removing-a-microsoft-office-update-from-multiple-computers","title":{"rendered":"Removing a Microsoft Office Update from Multiple Computers"},"content":{"rendered":"

This is one of those situations where something that seems like it ought to be very quick and simple is unfortunately not so quick and not so simple. The good news it’s also not *that* difficult, but there’s no question that it’s a pain and it takes a bit of effort.<\/p>\n

It used to be the case that if you needed to remove a Microsoft Office Update such as KBXXXXXX that you could remove it just like you can remove any other Windows Update. In BatchPatch we have a couple of built-in options for executing the update removal process of a particular Windows Update that you can access under ‘Actions > Windows Updates > Uninstall individual update…<\/em>‘ To use those menu items all you need is the KB number of the update that you want to remove.<\/p>\n

Unfortunately for a while now the above-mentioned built-in commands for removing individual updates is only successful for standard Windows operating system updates. Microsoft Office updates, on the other hand, require a different removal command that unfortunately involves some manual digging.<\/p>\n

The command line syntax options for removing a MSOffice update are as follows, but you have to substitute the correct Office GUID<\/em> and Patch GUID<\/em> values into your command, and this is what makes the process frustrating\/tedious:<\/p>\n\n

msiexec.exe \/package {Office GUID} \/uninstall {Patch GUID} \/QN<\/pre><\/td><\/tr><\/table><\/div>\n\n\n
msiexec.exe \/package {Office GUID} \/uninstall {Patch GUID} \/QN REBOOT=REALLYSUPPRESS<\/pre><\/td><\/tr><\/table><\/div>\n\n
This Microsoft Blog article<\/a> explains the process for locating the correct GUIDs in the registry for the patch that you wish to uninstall. <\/p>\n
After you find the appropriate GUIDs, you can form the actual command to use to remove the update.  So, for example, the following command is an example of what your command will actually look like, as I have inserted actual GUID values, but as previously mentioned, you’ll need to find the GUIDs for the product and patch that you are removing.<\/p>\n\n
c:\\windows\\system32\\msiexec.exe \/package {90140000-0012-0000-1000-0000000FF1CE} \/uninstall {B23AAF3E-F931-4C72-8D96-7E58363A3D12} \/qn<\/pre><\/td><\/tr><\/table><\/div>\n\n
Once you have determined the proper syntax and have run it successfully on your test computer, you may insert it into a ‘Remote Command’ in BatchPatch.  Highlight the desired target computer rows in the BatchPatch grid.  Then select ‘Actions > Execute remote process\/command > Create\/modify remote command 1<\/em>‘<\/p>\n
\"\"<\/a><\/p>\n
Paste your command into the field, as illustrated in the screenshot above.  Then either ‘Execute’ the command immediately or choose ‘Apply…’ to execute it later.  Another option for executing at a later time\/date is to hard-code the command into the BatchPatch menu by using ‘Actions > Execute remote process\/command > Create\/modify remote commands<\/em>‘  In this case I have used ‘Apply…’ to apply the commands to each of the highlighted rows, which you can see in the screenshot below.<\/p>\n
\"\"<\/a><\/p>\n
Now I can execute the applied command for each\/every row by just selecting the rows that I want to include, and then clicking ‘Actions > Execute remote process\/command > Execute remote command 1<\/em>‘<\/p>\n","protected":false},"excerpt":{"rendered":"
This is one of those situations where something that seems like it ought to be very quick and simple is unfortunately not so quick and not so simple. The good news it’s also not *that* difficult, but there’s no question that it’s a pain and it takes a bit of effort. It used to be […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1,17,3],"tags":[329,327,328,331,330],"class_list":["post-4266","post","type-post","status-publish","format-standard","hentry","category-blog","category-general","category-tutorials","tag-microsoft-office","tag-msoffice","tag-office","tag-remove-patch","tag-remove-update"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/4266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/comments?post=4266"}],"version-history":[{"count":4,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/4266\/revisions"}],"predecessor-version":[{"id":4272,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/4266\/revisions\/4272"}],"wp:attachment":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/media?parent=4266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/categories?post=4266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/tags?post=4266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}