Will need experienced help with this.
It's a long explanation, brace yourself.
Written in points to be more clear.
If needed, see my build specs by clicking on my profile pic.
This is how I got Windows 7 and Windows 10 to dual boot on the same SSD's different partitions WITHOUT converting it into GPT.... About 3-4 months ago:
How chkdsk screwed up the logical drive partition and Windows 10, Win10 won't start. After a few months from getting a proper dual boot:
Note: I barely have any free space, and absolutely no backups of a total of 5 TB Data (3x 1TB External HDDs, 2x 1TB Internal HDDs, 1x 256GB Internal SSD)
1. How do I reinstall Windows 10 in a new partition (not logical partition/drive), on the same SSD?
2. Can I do that without having absolutely ANY effect on my current Windows 7 installation? (Like the drive letters n everything should remain the same, changes to boot menu are ok and obvious.)
3. To dual boot, Can I install another copy of Windows 7 on the new partition and properly upgrade it to Windows 10?
4. Will it function just like before? (I know my files/settings won't be there)
5. If yes, how can Windows 10 be upgraded from Windows 7, still being on a MBR disk?
6. Will chkdsk still create issues like before if I do this? Why/why not?
7. If chkdsk will create issues, how do I completely prevent it from scanning the drive? (Can I rename the extension of chkdsk.exe in system files so it won't work?)
Thanks for any help in advance
It's a long explanation, brace yourself.
Written in points to be more clear.
If needed, see my build specs by clicking on my profile pic.
This is how I got Windows 7 and Windows 10 to dual boot on the same SSD's different partitions WITHOUT converting it into GPT.... About 3-4 months ago:
1. Had Win7 on 256GB MBR SSD, tried to convert to GPT using gptgen as I wanted to install win10 clean but Win10 clean install from boot doesnt install on MBR.
2. After gptgen completed, a BSOD came, my win7 stopped booting.
3. Trying to recover, accidentally executed "clean" in DISKPART. Entire drive was unallocated.
4. Used EaseUS Partition Recovery (Boot version) to recover but it was recovered as a MBR disk, with the previous 2 partitions: ((System Reserved and Windows 7 drive)), and the empty partition recognized as a normal logical disk.
5. My Windows 7 booted successfully after somehow repairing boot files from the Win7 Setup disk.
6. Then, instead of clean installing Win10, I installed another copy of same Win7 from the same setup CD to the logical partition of the same SSD and upgraded it to Windows 10 Pro x64 from running the setup from the iso file in Win7 Environment. Everything worked perfectly fine and normal.
7. Ended up with a successful Windows 7 and Windows 10 Dual Boot on the same SSD, without converting it to GPT. (yay)
8. Knew it's messed up, avoided chkdsk at all times, cancelled all scans.
2. After gptgen completed, a BSOD came, my win7 stopped booting.
3. Trying to recover, accidentally executed "clean" in DISKPART. Entire drive was unallocated.
4. Used EaseUS Partition Recovery (Boot version) to recover but it was recovered as a MBR disk, with the previous 2 partitions: ((System Reserved and Windows 7 drive)), and the empty partition recognized as a normal logical disk.
5. My Windows 7 booted successfully after somehow repairing boot files from the Win7 Setup disk.
6. Then, instead of clean installing Win10, I installed another copy of same Win7 from the same setup CD to the logical partition of the same SSD and upgraded it to Windows 10 Pro x64 from running the setup from the iso file in Win7 Environment. Everything worked perfectly fine and normal.
7. Ended up with a successful Windows 7 and Windows 10 Dual Boot on the same SSD, without converting it to GPT. (yay)
8. Knew it's messed up, avoided chkdsk at all times, cancelled all scans.
How chkdsk screwed up the logical drive partition and Windows 10, Win10 won't start. After a few months from getting a proper dual boot:
1. Power cut one day while Win10 was booting, unsuccessful shutdown. (The power cut timing was too perfect, as Win10 on my SSD takes like less than 5 seconds to load, and it turned off exactly in those 5 seconds)
2. After the power cut, always booted from Win7 as I use it as the primary OS.
3. Booted Win10 3 days ago, it launched automatic repair without even prompting.
4. It "scanned for disk errors" and suddenly restarted, then showed a message "automatic repair cannot repair this comp" or something.
5. About 30GB Data from that partition, videos, game files, pics, movies, even windows's own registry had it's size "0 bytes".
6. Successfully removed and completely formatted Windows 10 partition.
7. Scanned my Win7 partition, no drive errors found by chkdsk. Win7 boots all fine. Everything must be ok.
2. After the power cut, always booted from Win7 as I use it as the primary OS.
3. Booted Win10 3 days ago, it launched automatic repair without even prompting.
4. It "scanned for disk errors" and suddenly restarted, then showed a message "automatic repair cannot repair this comp" or something.
5. About 30GB Data from that partition, videos, game files, pics, movies, even windows's own registry had it's size "0 bytes".
6. Successfully removed and completely formatted Windows 10 partition.
7. Scanned my Win7 partition, no drive errors found by chkdsk. Win7 boots all fine. Everything must be ok.
1. How do I reinstall Windows 10 in a new partition (not logical partition/drive), on the same SSD?
2. Can I do that without having absolutely ANY effect on my current Windows 7 installation? (Like the drive letters n everything should remain the same, changes to boot menu are ok and obvious.)
3. To dual boot, Can I install another copy of Windows 7 on the new partition and properly upgrade it to Windows 10?
4. Will it function just like before? (I know my files/settings won't be there)
5. If yes, how can Windows 10 be upgraded from Windows 7, still being on a MBR disk?
6. Will chkdsk still create issues like before if I do this? Why/why not?
7. If chkdsk will create issues, how do I completely prevent it from scanning the drive? (Can I rename the extension of chkdsk.exe in system files so it won't work?)
Thanks for any help in advance