No worries at all. Thanks for the thanks :-)
Found below for KB3114409 from another list.
I can't vouch for the full registry path due to various versions of Office 2010
out there.
HKEY_LOCAL_MACHINE/SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall{90140000-003D-0000-0000-0000000FF1CE}Office14.SingleImage{14CDCBF7-3CCC-42E2-A5BB-2D4926E16FAA}
msiexec.exe /package {90140000-003D-0000-0000-0000000FF1CE} /uninstall
{14CDCBF7-3CCC-42E2-A5BB-2D4926E16FAA} /qn /norestart
Have also seen {90140000-0011-0000-0000-0000000FF1CE} (2010 Pro Plus)
Shane
Date: Fri, 11 Dec 2015 13:04:19 -0600
Subject: Re: [mssms] Best way to uninstall KB3114409?
From: [email protected]
To: [email protected]
Just wanted to follow up to say thanks, that was very helpful.
Steve
On Wed, Dec 9, 2015 at 5:32 PM, Shane Alexander <[email protected]>
wrote:
Start with below to get info on how to uninstall an update to an Office
application.
http://eskonr.com/2015/01/how-to-uninstall-microsoft-office-security-updates-using-configuration-manager-2012/
http://blogs.technet.com/b/odsupport/archive/2011/04/21/how-to-automate-the-uninstallation-of-an-office-patch-programmatically.aspx
I personally wouldn't use a Task Sequence (one reason is as you said, how to
then target the deployment (a collection of machines with the update
installed)).
I'd create an Application for the uninstall, use a registry detection method
(you have to find where in the registry the update is registered as installed,
see below), and have an command line like from the above links.
Then deploy that to all clients, as the detection method (if set up right) will
determine if the update is installed (or not) and only run if it is detected. I
don't have any Office 2010 installs, but below gives you an idea that an update
to an Office app, in this instance KB3114349 for Outlook 2013, can put multiple
entries in the registry, and may help with your detection method (this is 32bit
Office on a 64bit OS). (Office 2013)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-0011-0000-0000-0000000FF1CE}_Office15.PROPLUS_{7111EAFF-4C0E-4A76-8795-6C2007126BD6}
DisplayName = Update for Microsoft Outlook 2013 (KB3114349) 32-Bit Edition
(Outlook 2013)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-001A-0409-0000-0000000FF1CE}_Office15.PROPLUS_{7111EAFF-4C0E-4A76-8795-6C2007126BD6}
DisplayName = Update for Microsoft Outlook 2013 (KB3114349) 32-Bit Edition
(Lync 2013)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-012C-0000-0000-0000000FF1CE}_Office15.LYNC_{7111EAFF-4C0E-4A76-8795-6C2007126BD6}
DisplayName = Update for Microsoft Outlook 2013 (KB3114349) 32-Bit Edition
Cheers,
Shane
Date: Wed, 9 Dec 2015 14:27:13 -0600
Subject: [mssms] Best way to uninstall KB3114409?
From: [email protected]
To: [email protected]
While I normally let updates go to a small test group for a few days before a
wide deployment, yesterday's updates were inadvertently deployed to all
clients. Now the newly recalled KB3114409 is causing issues.
I have found a couple of blog posts on creating a task sequence to remove an
update, but they didn't cover targeting the task sequence at clients with a
specific update installed.
What is the best way to go about uninstalling a problematic update?
Steve
