You are viewing a single comment's thread.

view the rest of the comments →


[–] elixxx 0 points 3 points (+3|-0) ago  (edited ago)

aegis v1.4 didn't removed kb2952664 from my win7 home premium 64bit. manual uninstall using control panel didn't help either -- kb2952664 was was re-installed on pc reboot. workaround was found with help of though:

at elevated console prompt following command otputs exact name of related KB package

dism /online /get-packages | findstr KB2952664

in my case otput was "Package Identity : Package_for_KB2952664~[lot_of_random_chars/digits]~amd64~~".

next command

dism /online /remove-package /PackageName:Package_for_KB2952664~[lot_of_random_chars/digits]~amd64~~

have removed kb2952664 completely.

[–] [deleted] 0 points 2 points (+2|-0) ago 



[–] iunlock 0 points 2 points (+2|-0) ago 

I've just checked my update history log and did not find: kb2952664.

elixxx, you've mentioned Windows 7, therefore, could this possibly be a Windows 7 specific update?

I'm on 8.1.


[–] 2402420? 0 points 1 points (+1|-0) ago  (edited ago)

On review, I had the same issue, and manually removed a slightly different package than elixxs's


edit - after reboot it's still there, although when I ran the uninstall, it said it completed 100% instead of giving an error. Several other packages were also listed, so I'll try some of the others and edit this again with updated results.

edit - /get-packages this time only showed one package: Package_for_KB2952664~31bf3856ad364e35~amd64~~ and /remove-package for that package resulted in an error in dism.

In any case, I don't think anything untoward will happen and will leave it as-is. Windows 10 isn't attempting to install and this doesn't seem to be having any effect on my system, installed or uninstalled, since it may depend on other components that have already been uninstalled.