As was foretold, we've added advertisements to the forums! If you have questions, or if you encounter any bugs, please visit this thread:

PC is haunted by old Windows 10 installation

Bliss 101Bliss 101 Registered User regular
I'm trying to help a friend fix his PC, but the supposedly simple task has turned into a mind-boggling nightmare.

Story so far: guy was fed up with his old and crowded HDD, buys a new SSD, plugs it in, creates bootable Win10 installation media, installs Windows 10 on the new drive. Everything goes well, Windows boots from the new drive just fine -- initially. So then we delete the old Windows folder from the old drive to free space. This results in the computer randomly failing to boot (but not every time). This could be resolved by manually selecting Windows Boot Manager from the boot options (which seems to be the default choice anyway but somehow isn't, apparently), at which point it would boot from the SSD every time. This seemed like a minor annoyance that was left to be resolved at a later time.

But then! Windows Update tries to perform a Windows Update, and somehow tries to do it on the now-nonexistent copy of Windows. Then it of course fails. This results in a loop of the computer restarting itself a couple of times, trying to apply the update again and failing. Then after wasting everyone's time for a while it somehow gives up and decides to boot normally from the SSD. This happens every time the computer is booted.

No problem I think. We'll just back up whatever is left on the old drive, use DISKPART to delete all partitions, then put the blank HD to use again. But no! Windows won't let me delete the system partition on the old HD. My understanding is that this means Windows still thinks it lives on that system partition and therefore won't allow it to be deleted. Why? And how do I get around this? I guess I could unplug the haunted drive, bring it home, plug it into my computer and use my own Windows to clean it. But that's a bit troublesome in this case due to the distances involved. Is there a less laborious way?



  • darkmayodarkmayo Registered User regular
    edited October 2019
    Make a DOS bootable thumb drive, boot into that then wipe the disks.

    darkmayo on
    Switch SW-6182-1526-0041
  • spool32spool32 Contrary Library Registered User regular
    edited October 2019
    Plugging the drive into your own Windows install probably won't work, and it might cause his machine not to boot either!

    First step for me would be to disable the drive in BIOS and be sure that his computer will operate correctly without it. After that, I would either boot into a Windows 10 recovery mode, a bootable thumb drive like darkmayo said, or get one of the USB bootable Linux installations that come with disk Management tools and fix it with that.

    spool32 on
  • Zilla360Zilla360 21st Century. |She/Her| Surreal. Immersive. Earth.Registered User regular
    NH844lc.png | PSN | GACSALB.jpg My Blog |🏳️‍⚧️♥️
  • Bliss 101Bliss 101 Registered User regular
    Update: success!

    I was able to take another stab at the computer last weekend. Thanks to @spool32 I had the presence of mind to test if the pc can even boot without the old HD; turns out it didn't.

    So I have no idea how this happened in the first place, but apparently we had a situation where the system booted from the old hd, and only from there, but the Windows folder lived on the new SSD. So I nuked the SSD partitions and installed a fresh copy of Windows. And that was that. Problem solved.

    Thanks for the help. :)

Sign In or Register to comment.