Cleanup removes backup of old files replaced by update, so you can't uninstall updates, because of this. If you want to remove superseded updates, just install new ones and run cleanup again, old files will be deleted, just their entries in updates list remains.
I use: Code: Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore to see if a cleanup is required and: Code: Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase to clean out the image online only-mainly for all the removed apps I disable offline-the cmd does not work offline. Unfortunately I ran the cmd at first logon automatically, so, any Windows 8.1 Pro x64 updates slipstreamed and now installed get the treatment...s**t.
...so, search for the pertanent now false entries in the registry and delete them? (I have a program that will run batches to gain the requisite permissions in bulk throughout the registry-SetACL Studio Pro. Therefore, this is an option for me.)
See post this page; sorry abbodi1406...meant to include your post in the reply. I'm going to try it now because all the cat and mum files are still there in the packges directory.
Security updates are available on ISO-9660 DVD5 image files from the Microsoft Download Center: support.microsoft.com/kb/913086
@ abbodi1406, Burfadel and Gyrxiur The cleanup worked to remove all but the 2884101 files, all registry keys were removed as explained in previous post-only 2884101 was present- and all entries are removed for all updates anywhere. I removed all the 2884101 files in the servicing\packages folder and the registry keys by modifying the permissions using SetACL Studio Pro. Microsoft Update shows no updates to install=up-to-date. SWEET Thanks very much for all the advice-much sweeter when it all comes together.
Since McRip and his server are gone, there needs to be some changes in the way the repo is set up. burfadel has some good ideas, so I've volunteered to step down and let him to take control of things for Win8.1 (and Office 2013). Thanks to Burf his ongoing efforts in helping the community here at MDL. And many thanks to Alphawaves for his great utility, the Windows Hotfix Downloader. WHD is an indispensable tool and will become even more important with the changes being discussed. There'll be a change coming for the Win7 repo also, but it's a little early to announce it yet. I'll be helping as much as possible to make the transition go smoothly and will still be posting here at MDL. Thanks again to burfadel for stepping up and doing this. I think he'll do a great job. -------- P.S. If McRip happens to be reading this- many thanks to you, friend, for originally giving me the opportunity to get the Win8 repo up to date. I enjoyed doing it. Everybody here at MDL hopes you'll start posting again and continue contributing with your helpful knowledge in the future.
How about doing a hotlink repo, where you direct link to those files on the MS servers? If MS pulls the hotfix then upload just that hotfix to a file sharing site
Now there's an idea.....I mean whoever hosts the file downloads pays huge for the bandwidth and hotlinks the downloads to a personal server. Would it be much more trouble to hotlink to the KB itself instead? I don't think any free file sharing site would allow the huge quantity of hits it would get especially on patch Teusdays and for a while after.
I've actually gotten most of my hard-to-get kb files from people posting files individually on different sites. This makes the most sense to link to MS's already existing download links and just make a separate area for Special Case files. Sometimes windows update catalog or ms download center don't have a newer revision of a file that Windows Update has. They also try to make certain ones hard to obtain. The win7 kb971033 comes to mind. The problem with these DMCA crawlers is they search for both filenames and hashes, so we'd need to up them with custom filenames with a password encryption. maybe we could use that encrypt64 thing or whatever it's called to disguise the links as well.