Win10 Update Problems

bubba6532 · 17 Oct 2017

Yeah. I figure on getting a 1 Tb 7,200 rpm 2.5" HDD and an external USB 3.0 enclosure. I believe that should handle the imaging of a 500 Gb SSD, or most any imaging I may need to do in the future. Let me know if you think it's adequate -- I won't have a chance to order before tomorrow. That HDD won't be as fast as an external SSD, but the HDD's are quite a bit more economical in the larger sizes. I'd try to get a 2 Tb drive but I can't find one in 7200 rpm, and I'm kinda stuck on that. They are MUCH faster than their 5400 rpm brethren, at least in the laptops I've used.

dalchina · 17 Oct 2017

USB3 is the key there. I can image Windows (about 80Gb) from SSD to a 2Tb 5400rpm HDD over USB3 in under 12 mins. (For historical reasons most programs are installed to D: and personal data is on another disk).

I guess SSD backup disks would be relatively drop-proof...

hawkman · 18 Oct 2017

Would you mind running this tool please, copy/paste the output.

http://www.sysnative.com/niemiro/apps/SFCFix.exe

Hopefully not more than 20 entries on it.
(there appears to be a few hash missmatches in your winsxs folder)

Roy

dalchina · 18 Oct 2017

If you can fix your SFC issues, please then update your disk image, then try deleting the redundant partitions as I commented above.

Then post an updated screenshot of your partitions before attempting an upgrade.

bubba6532 · 18 Oct 2017

Is SFCFix "safe" to run prior to performing a disk image? It'll be a few days before I get the HDD and external enclosure to be able to perform a disk image. Even though this particular installation of Windows is apparently "broken", at least so far as being able to update, it appears to be working just fine so far as allowing me to run a lot of diverse software, and I'd prefer to not risk losing that.

dalchina · 18 Oct 2017

The safest course is the most cautious. Image first, change afterwards.

hawkman · 18 Oct 2017

Its primarily a reporting tool, an equivalent to the Old SURT program, replaced by DISM.

It WILL NOT harm your OS.

Roy

bubba6532 · 21 Oct 2017

While waiting for the external HDD and USB enclosure to arrive, I decided to at least check into reagentc /info, to look at those partitions on the SSD. Somehow, I think the findings may be ominous.

dalchina · 21 Oct 2017

Well, you've a huge array of Recovery partitions and a long history of failed upgrade attempts... so maybe that somewhat explains why your recovery environment isn't properly associated with your OS.

I would expect that you can't get into Safe mode or reboot to Advanced Startup options, and automatic repair wouldn't start.

You've a way to go in trying to fix your OS once you can start by deleting redundant partitions.

You can try
reagentc /enable
and see what happens...

But I would wait 'til you've created your disk image, and then start cleaning up.

bubba6532 · 22 Oct 2017

Yes, I think I've done about all that I feel I can safely do until I'm able to image the drive. One question............ I believe that single recovery partition lurking on the mechanical HD should be the original one prior to when I cloned it, the OS and the other partitions to the SSD. Would there be any reasonable way of comparing that partition to those on the SSD, to eventually help in determining which of the partitions on the SSD mirrors that original recovery partition? Just trying to come up with an idea of which partition to save if other tools don't determine which is the REAL recovery partition.