Thanks!!!!!!
Your method enabled me to finally clean out the KB2952664 mess. I had left a couple of machines on automatic update and they received the update by mistake.
wusa.exe /norestart /uninstall /kb:2952664
On our computers this command doesn't help. The command runs and finishes without error, but KB2952664 is not uninstalled. Perhaps because so many different versions of KB2952664 were installed on top of each other? The other KBxxxxxxx uninstall commands
worked well, so it seems to be a specific KB2952664 problem
dism /online /get-packages | findstr KB2952664
Very helpful, with this line I could see all the different KB2952664 versions. Some machines had 9 of them!
dism /online /remove-package /PackageName:Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3
This removes version 6.1.1.3 only. On machines that also have versions 6.1.0.12, 6.1.3.0, 6.1.7.4, 6.1.8.2, etc. etc. this command must be repeated with the appropriate version numbers
On some of my machines three specific versions cause an "invalid package" error:
/remove-package /PackageName:Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.0.12
/remove-package /PackageName:Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.0.12
/remove-package /PackageName:Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.0.12
Oddly enough they were removed anyway!
Run a final Get-HotFix -id KB2952664 command , and the output should be something like:
Get-HotFix : This command cannot find hot-fix on the machine 'localhost'. Verify the input and Run your command again.
At line:1 char:11
- Get-HotFix <<<< -id KB2952664
+ CategoryInfo : ObjectNotFound: (:) [Get-HotFix], ArgumentException
+ FullyQualifiedErrorId : GetHotFixNoEntriesFound,Microsoft.PowerShell.Commands.GetHotFixCommand
Which translates to: "KB2952664 not found"; Success!!!