I posted this before and no one answered so thought I would try it in an 8.1 thread. I was wandering if these copy files to DVD are relevant to the full Windows 8.1 Pro DVD purchased, not an upgrade/Windows 8 Update to... The reason I ask is because all except 2 are installed dynamically during the upgrade process as part of the actual 8 to 8.1 installation-contained in the upgrade files. Spoiler Included in latest changelog as still relevant KB2892082DVD KB2898464DVD KB2895233DVD KB2891213DVD KB2890139DVD KB2882342DVD KB2896394DVD KB2894179DVD KB2891300DVD KB2883900DVD Also, could some kind soul point me to the download page for the HotfixExtractor-were you copy the msu/cab onto it and it extracts the files; ricktendo64 maybe? Googled it and the right program does not show. Thanks.
No KB2908279 (aka Windows 8.1 mouse lag patch) as part of Patch Tuesday? Um... is it common for things like that not to be included?
Ja, installed on main machine without a hitch. Errors in the event log are still there, so business as usually. Now lets update the other installations.
These are the deprecated updates: KB2886439 (Flash; replaced by new Flash) KB2884101 (IE cume; replaced by KB2888505) KB2901549 (IE reliability; replaced by KB2888505) KB2898742 (part of the October patchball; included in KB2888505) KB2895219 (Runtimebroker.exe process crashes in Windows 8.1; included in KB2887595) KB2902864 (Secure boot watermark; included in KB2887595) The mouse update is an update to the compatibility shims. KB2887595 does include an update to the compatibility shims, but the version in the mouse update is newer than the one in KB2887595, so it all depends on when exactly Microsoft updated the compat shims for the mouse problem. If it did so before 16441, then KB2887595 includes the mouse fix. If it did so between 16441 and 16456, then KB2887595 does not include the mouse fix. I think it is most probable that KB2887595 does not include the mouse fix.
I am unable to uninstall any of the superseeded updates in Windows 8.1 Pro x64 (full retail DVD)- no "permanent" entry exists in the mum files. I believe allowing Windows Update Cleanup in cleanmgr is the culprit. Anybodyelse run into this and is there a way...? Thanks for any help.
I haven't tried this, so I have no idea whether it works on an offline image, but have you tried dism with the command line options /cleanup-image /startcomponentcleanup and maybe even /resetbase Using startcomponentcleanup by itself may not remove superseded components, but resetbase definitely will (if available for an offline image).
^ I think he is talking about live online system RickSteele, you have to run this command: Code: Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase meaning, if you ran the command once, you have to run every time you want to remove superseded updates and since MS accomplished the first one time in the GA enterprise/pro releases, the user is obligated to run the command every time
Ah ok! Yeah I've only used it on an online system. It is really the 'ideal' method for removing superseded updates, although with the downside that you can't uninstall an update if it turns out to be bad. In this case, the only solution would be to wait until a superseding update is released.
I am unable to uninstall any of the superseeded updates in Windows 8.1 Pro x64 (full retail DVD)- no "permanent" entry exists in the mum files. I believe allowing Windows Update Cleanup in cleanmgr is the culprit. Anybodyelse run into this and is there a way...?Thanks for any help.