Auto-Repair can't fix--Can't upgrade in place either

This is my first post. Please take pity on me!

If I disable the automatic repair, I get an error about HAL bein missin or contains errors.

I can get to a command line via Troubleshoot->Advanced Options->Command prompt.


I can't see anything wrong with the files on the drive.

I have one SSD drive. I have an c:, d: e:, and x: when viewing under the command prompte.

d: looks to be the windows drive.

I've made a win10 upgrade usb stick by using Rufus to create the files on the sitck from the .iso. After getting to the command prompt, I insert the stick (it becomes the f drive) and run f:setup.

I get stuck on a "Compatibility Report" screen which says "the computer started using the Windows installation media". I've searched on how to avoid this issue, but haven't found a solution from just a command prompt.

I've tried many other things including:

chkdsk /r on all drives (no errors)
restoring registry from regback
mbr repair

Out of ideas. Any help would be greatly appreciated!

Welcome to the Ten forum.

According to Brinks tutorial https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html This can only be invoked from within Windows. Please have a read, see note section.

Obviously you can boot your USB. Have you entered Recovery then startup repair. I've read that you may have to run this automated repair up to three times with reboots in between each.

Before I did any of this, since you can boot have you got your data files backed up.

One other recommendation please consider getting a disk imager. Macrium Reflect is free, it is used widely by forum members and will restore your system the easy way.

Others may comment on how to fix the boot records however by the time I get to that point I've used Image restore or I have my data backed up and I'm doing a clean install. Given this is a Lenovo one of those partitions you mentioned is likely the factory recovery software, maybe worth identifying what each partition is.

See if using the recovery - repair three times gets things fixed. It may be preferable to use your SSD to do the repair three times if the USB device is a different build of Windows. .

Post back and good luck.

Caledon Ken said:

Welcome to the Ten forum.

According to Brinks tutorial https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html This can only be invoked from within Windows. Please have a read, see note section.

Obviously you can boot your USB. Have you entered Recovery then startup repair. I've read that you may have to run this automated repair up to three times with reboots in between each.

Before I did any of this, since you can boot have you got your data files backed up.

One other recommendation please consider getting a disk imager. Macrium Reflect is free, it is used widely by forum members and will restore your system the easy way.

Others may comment on how to fix the boot records however by the time I get to that point I've used Image restore or I have my data backed up and I'm doing a clean install. Given this is a Lenovo one of those partitions you mentioned is likely the factory recovery software, maybe worth identifying what each partition is.

See if using the recovery - repair three times gets things fixed. It may be preferable to use your SSD to do the repair three times if the USB device is a different build of Windows. .

Post back and good luck.

Automated repair has probably been run hundreds of times by now. At first, it was in a loop running it over and over again until I used the Startup options to disable it running automatically.

Yes, I have all my data files backed up.

But I wanted to keep all my apps. There are several expensive ones for which I probably won't be able to find the license keys. Not to mention the literally hundreds I've installed over the previous years for software and hardware development.

I cloned the drive with the Win10 that no longer booted and started trying to do the upgrade in place. Finally gave up on that and used the stick to do a clean install. I figured I could switch to the clone drive if there was a way to do the "upgrade in place" without first having a clean boot.

I'd make backups of my files using Aoemi BackUpper Pro, so once I could boot into Windows I installed the free version and can restore the files that were on my C drive without any issues. The file backup includes stuff from my D: drive, but I figure I'll just put that back in the machine and won't have to restore those files.

Once I had BackUpper installed, I found an image file in a place I didn't expect. It's from 8/2016 -- I think all my applications were installed before then.

So, I figure I'll try restoring from that image. That should bring my apps back, right?

Will that restore Program Files and Program Files (X86), or do those need to restored as files?

Thanks!

I'm running to the store to buy a new SSD. I'll clone my existing SSD with the fresh install to it, then swap it into my laptop to try doing the system restore using BackerUpper.

That way, if things "go south", I can swap back and at least have a system with a fresh install (but no apps).

I'm worried my root cause is laptop (W520) hardware--I've been suffering for months with my #2 SSD. It would drop offline and come back on continuously. Sometimes--other times it would be solid for weeks.

Earlier this week I bought a drive and cloned the #2 drive to it. I was going to use the new drive as my #2 and see if that resolved my issues. I was trying to change the drive letter of my existing #2 SSD so the new one could replace it when bad things (BSOD) happened. I'd never had a problem with booting or BSOD before that, but then I was hosed.

I've also ordered a used W520 as a replacement, in case root cause IS my existing laptop. I have three docking stations and power supplies, so getting a used W520 saves big $ compared to a new laptop. And, if my old laptop proves to be solid, having a second will be very handy.

However, I'd forgotten that Lenovo doesn't support W520 drivers on Win10. So, if the system restore doesn't work to restore my apps, I'll probably downgrade back to Win7, even if I have to buy it. I'd tried unsuccessfully to downgrade soon after going to win10 due to unresolveable graphics issues (can't remember why downgrade it failed). The only reason I didn't do a fresh Win7 install was the apps recovery issue.

If I have to re-install my apps anyway, I'm going back to Win7, since that's supported by Lenovo.

Whew! Complicated.

If you go to Win 7 try using your existing license. Read conflicting reports about what MS will or won't do re you had 7 but went to 10 but now want out. I know there was the 30 days, which I think dropped to 14. If your old key activates, and after ensuring you are not breaking the rules, run with it.

Buying 7 may be a challenge. I read MS was going to stop selling it and I've seen some outrageous prices.

Not a lot of vendors will say they support 10. It is a matter of finding good drivers and not necessarily the latest. I have a Dell D630 that was shipped with XP. It runs 10 very well. I upgraded wireless card to Intel AC7260. Every major upgrade, like AU, the wireless dies. I revert back to the February 2014 drivers and all is good.

Re your suspect SSD. You may wish to see if there is new firmware available. I would still be suspect of it but maybe it just needs to be updated and wiped.

I'm happy to report that after several days of using AOEMI Backupper and partition tools to restore the August version of my system and more recently backed up files--

I'm up and going again!

The Aoemi tools are very intuitive and easy to use. A definite "thumbs up" for them.

I first restored the system to a newly purchased Sata hardfile. Booted fine, but awfully slow. I made a partition backup of data on the #2 TB SSD on a USB drive, then copied the partitions from the new Sata hardfile onto that SSD.

Finally, I copied the partion that contained the #2 SSD backup onto the SSD. It's now the #1 (and only) drive.

I ended up with c, d, and e all on the same physical drive, instead of the e: residing on the #2 ssd. So, if my problem really was with the #2 Ultrabay connector (as I expected), it should be resolved since I'm no longer using a #2 drive.

I'll use the system for a while, before using a #2 drive to see if I have issues again.

But, I was really scared this morning. Windows Update ran last night and shut down the pc. When I started up this morning, the update process went through several screens indicating progress in the update. After it got to its final screen that said something like "Let's Begin", it went dark.

I gave it three hours after that before finally concluding it wasn't going to boot.

Fortunately, after holding the power button down for several seconds to shut down, then powering on, it rebooted ok.

I'm going to make another system backup before I shut it down again!

Great news. These really are complex environments when we mix Windows, packaged software, vendor drivers and physical hardware. Always a great feeling when we're back online.