Windows 10: Windows 10 partition stopped booting, drive checks out OK

I have a Lenovo p51 laptop which multiboots - there is an Ubuntu 22 partition, a Windows 10 partition, and an ubuntu 18 partition. It's been working fine for about two years. I sometimes boot Windows 10 on the hardware, and sometimes under Virtualbox while running Ubuntu.Things were fine on Friday, 22 December, but yesterday 29 December the Windows partition would no longer boot - neither natively or under Virtualbox. The symptoms are a black screen with no cursor immediately after choosing the "Windows Boot Manager" in Grub. I made a bootable Windows 10 USB stick to try and repair the

:)

 

W7 Hard drive partition issue

to get rid of that 100 meg windows partition that setup creates for you on a new install on a blank hdd:

- press shift+f10 when on the partition management screen in setup <-- this opens a command prompt
- diskpart <-- start the windows command line partition management tool
- list disk <--- list the installed hdds in this computer for the next step
- select disk 0 <- might have to replace 0 with the number of the correct disk
- clean <-- this will erase all data on the disk you selected one step up- dont use the wrong disk!
- create partition primary <- creates a primary partition taking up all space on the drive, adjust the command if necessary
- exit, exit to exit diskpart and the command prompt
- click refresh in partition manager and select your newly created partition and install to that

 

How to go about building a tri-boot system?

i dual boot all the time, and going in to tri boot is easy.

step 1) partition the drive in to 3 partitions ( leaving 1 empty for the linux installer. )
step 2) install windows on the first 2 partitions.
step 3) install linux, and let it auto partition the remaining space. ( i recommend at least 30gb of space for linux, because it will make things a lot easier. )

step 4) enjoy.

 

Move Win7 64 image from a partition NTFS to a new drive

EDIT: After reading your first post again, is there any reason that you would now need GPT? Are you just trying to move the windows install to a new disk or is there a new motherboard involved?

If you are already booting to an NTFS partition, then it makes me wonder if after copying to the new drive, the partition isn't getting marked as Active.

Following the same steps I posted above for startup repair, you can get to a command prompt and use diskpart to see if this is the case.

Code: In the command prompt: diskpart list disk select disk 0 (disk number may be different if you have other disks connected.) list partition select partition 0 (partition number number may vary, but you want to see the boot partition which is the same as your windows partition according to the screenshot on the OP) detail partition (This should have Active: Yes or No. If it says no, since we have the partition selected, you can just use the following command in diskpart) active[/quote]