[SOLVED] Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On

OK, will do. Those other things were in my "speedup" proposal and I inferred that you had accepted the entire proposal as I wrote it in your first cab.zip download list.

BTW: jcgriff2 requested I use Sysinternals’ Autoruns and his BSOD script SysnativeBSODCollectionApp to collect my entire registry and a bunch of other system data for a different thread I initiated. Would these be of any help to you on this problem?
 
I'm assuming that the order of these installs is not important, therefore I'm doing them in the alphabetic order they appear in my Downloads folder. Hope that's OK.
 
Hi!

The next set of instructions will have to wait a bit as I have two very busy days ahead of me.

Please be patient for just a bit and I'll be with you as soon as I can.
 
No problem. You have already put in a lot of time on this thread and there's obviously a lot more to do. I have immediate obligations too.
 
Didn't know that C:\Windows\System32\Config\components is actually a registry hive, but despite all the database design and app writing I've done, I have never understood exactly what a "hive" is. Perhaps a "hive" corresponds to an RDBMS table placed in an individual file? Anyhow, as I said before, my Bitzipper archiver won't process a file name without an extension, so inside the ZIP file at 03-13 COMPONENTS Hive.zip the "file" is named components.xxx.

Once again, please let me know when you've downloaded it so I can free up my dropbox space.

Thanks.
 
I’m wondering if running Disk Cleanup, which I used to do a lot when I had a small Windows partition, could have contaminated the COMPONENTS hive or other aspects of my registry. One of the categories Disk Cleanup looks at is Windows Update, to wit:

4500145002

Is it safe to run Disk Cleanup on your Windows partition?
 
Hi!

I've downloaded it. You can remove it.

Hive is a collection of registry data. COMPONENTS hive is a collection of data on the Components Store. I doubt it was that. More likely there was a power failure or something that interrupted writing on the HDD/SSD.

And yes, it's safe.

MEGA
MEGA
MEGA
MEGA
 
softwaremaniac said:
More likely there was a power failure or something that interrupted writing on the HDD/SSD.
Click to expand...

The HDD is out of the picture because all extant users at the time of failure were defined with Profiles on the HDD while all system data was on my small SDD. Moreover, CHKDSK /F and SFC /SCANNOW have never revealed any problems on the new SDD. It could not have been contaminated by Samsung’s Disk Migration Tool when I replaced the small SSD with a new 1TB version because the W.U. problem that occurred before the swap. Interrupted I/O, maybe, but what’s the probability of that causing problems only with W.U.? I think the Registry Mechanic cleaning runs I used to do are more likely.

We probably won’t ever know what caused it. Far more important to just fix it.

softwaremaniac said:
And yes, it's safe. .
Click to expand...

Thanks.

New runs will have to wait for about 8 hours; busy all day recording music. Sorry.
 
malletKATman said:
It could not have been contaminated by Samsung’s Disk Migration Tool when I replaced the small SSD with a new 1TB version because the W.U. problem that occurred before the swap.
Click to expand...
Actually, it’s possible that Samsung’s Disk Migration Tool could have caused some of the problems that you see in the results of a FURT Scan run, but not the ones that triggered the W.U. failures starting with the Dec 2018 “patch Tuesday” release.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top