F5F Stay Refreshed Software Operating Systems You encountered an issue with a Windows 7 partition that became stuck after some activity.

You encountered an issue with a Windows 7 partition that became stuck after some activity.

You encountered an issue with a Windows 7 partition that became stuck after some activity.

E
EvaGos
Junior Member
Find
49
07-23-2016, 08:59 PM
#1
Hello everyone. It will take some time to walk through the sequence of events that brought me to this point. I understand it might be complicated and lengthy, so please give it a chance. I’ll do my best to clarify things clearly. My father’s computer has two hard drives: one he made a copy of from an old drive about a month ago, and another one he’s been using since. Both have multiple partitions—each drive holds Win 7 on one side and Win 10 on the other. He’s only been using the new drive for the past month.

Last night he tried to back up a .pst file from Win 7, which wasn’t critical. After finishing, he used Disk Management’s “Magic 8” tool to switch to the Win 10 partition. But something failed, and when he tried to load Win 10, it crashed with a “something went wrong” message. This triggered some troubleshooting steps, but none worked properly.

Interestingly, yesterday we ran the same program that his dad used for cloning—Acronis—to remove unused space from the new drive. We hoped this would help, but it didn’t. Then, after exiting Acronis and trying to restart (back to Win 10 troubleshooting), we saw a black screen saying “No operating system found.”

It turned out that after deleting what was thought to be an unused partition, the system mistakenly set that partition as active. When I reconnected the old drive and opened Windows 7 in Disk Management, I noticed the new drive’s partitions were completely disorganized. None had a letter assigned next to them, and the active one was actually empty.

I searched online and used DISKPART (via Command Prompt) with DiskPart. I managed three things:
1. Moved the right partition to become the active one.
2. Labeled the new drive “Volume E.”
3. Changed the “info” setting so it wouldn’t be hidden.

After these steps, I booted from the Windows 7 partition on the new drive, and the logo appeared—but the screen froze.

I checked Disk 0 (the faulty new drive) and saw that its leftmost partition was marked as active. The right partition (454 MB) was linked to Volume E. Disk 1 (my old drive) worked perfectly. I attached screenshots showing:
- Disk 0: the problematic new drive, with the active partition on the left.
- Disk 1: the old drive, fully functional.
- A screenshot from DISKPRAT displaying the partitions on my old drive, highlighting Partition #1 as working and booting Win 7.
- Another image showing the new drive’s partition, with Partition #1 set to active but not functioning.

I’m unsure why this happened, but I need guidance. Any advice would be greatly appreciated.
Reply
Reply
E
EvaGos
07-23-2016, 08:59 PM #1

Hello everyone. It will take some time to walk through the sequence of events that brought me to this point. I understand it might be complicated and lengthy, so please give it a chance. I’ll do my best to clarify things clearly. My father’s computer has two hard drives: one he made a copy of from an old drive about a month ago, and another one he’s been using since. Both have multiple partitions—each drive holds Win 7 on one side and Win 10 on the other. He’s only been using the new drive for the past month.

Last night he tried to back up a .pst file from Win 7, which wasn’t critical. After finishing, he used Disk Management’s “Magic 8” tool to switch to the Win 10 partition. But something failed, and when he tried to load Win 10, it crashed with a “something went wrong” message. This triggered some troubleshooting steps, but none worked properly.

Interestingly, yesterday we ran the same program that his dad used for cloning—Acronis—to remove unused space from the new drive. We hoped this would help, but it didn’t. Then, after exiting Acronis and trying to restart (back to Win 10 troubleshooting), we saw a black screen saying “No operating system found.”

It turned out that after deleting what was thought to be an unused partition, the system mistakenly set that partition as active. When I reconnected the old drive and opened Windows 7 in Disk Management, I noticed the new drive’s partitions were completely disorganized. None had a letter assigned next to them, and the active one was actually empty.

I searched online and used DISKPART (via Command Prompt) with DiskPart. I managed three things:
1. Moved the right partition to become the active one.
2. Labeled the new drive “Volume E.”
3. Changed the “info” setting so it wouldn’t be hidden.

After these steps, I booted from the Windows 7 partition on the new drive, and the logo appeared—but the screen froze.

I checked Disk 0 (the faulty new drive) and saw that its leftmost partition was marked as active. The right partition (454 MB) was linked to Volume E. Disk 1 (my old drive) worked perfectly. I attached screenshots showing:
- Disk 0: the problematic new drive, with the active partition on the left.
- Disk 1: the old drive, fully functional.
- A screenshot from DISKPRAT displaying the partitions on my old drive, highlighting Partition #1 as working and booting Win 7.
- Another image showing the new drive’s partition, with Partition #1 set to active but not functioning.

I’m unsure why this happened, but I need guidance. Any advice would be greatly appreciated.

Reply
Reply
S
Shaggy24
Member
Find
64
07-23-2016, 09:41 PM
#2
Check if you can connect a different machine running the same Windows 10 version. Use an 8 GB USB drive and make a recovery disk, then apply it to your damaged Windows 10 setup on the original PC.
Reply
Reply
S
Shaggy24
07-23-2016, 09:41 PM #2

Check if you can connect a different machine running the same Windows 10 version. Use an 8 GB USB drive and make a recovery disk, then apply it to your damaged Windows 10 setup on the original PC.

Reply
Reply