New
#230
Hello - my first post so please pardon any breaches of protocol! So successful was your Option 3 on my super swish PC that when an elderly friend asked me to look at her not-so-swish laptop which seemed to be suffering the same problems I agreed.
In fact I decided to do a clean install on the machine (Dell Inspiron running Windows 7 Home Premium) as it had been maintenance-less for many years and was somewhat clogged with un-needed clutter. The ReInstall from OEM disc went fine. Updates started well until after the SP.1 update and the subsequent download of the Windows Update Agent which follows. Then the ubiquitous "Checking for Updates" endless loop and 100% CPU hog. I have encountered endless cases of this precise sequence of events on pretty well every forum and help-site.
Undaunted I ran the Option 3. (In fact I have run it a number of times!) The bat file runs but "stalls" usually after sucessfully deleting the qmgr0.dat and qmgr1.dat files but sometimes after the next line where it returns the "Software Distribution Store.bak DATSTR~1 - The directory is not empty". There is a long pause and finally an Access Denied message followed by a "Could not acces the file as it is in use by another process" The .bat file then proceeds smoothly to completion. I would send you a snip-cap but not sure how to cap the dos screen before it closes?
I am guessing that the Option 3 that worked so well for me previously is not doing everything that it should here. Advice would be much appreciated. This is particularly troublesome after a reinstall - not just the CPU hog but the inability to install some 200 or so updates.