- Aug 19, 2015
- 16
- 0
- 10,510
I am aware that this question has been asked numerous times, but I haven't gotten the usual method to work for me. Here is what happens:
1. I go to Disk Management in Windows 10 and delete all of the partitions which I believe have Ubuntu on them. (list at https://drive.google.com/open?id=1ozzTGh6pE4aOH4N54jd2VdlTxaA5SktQ I delete Disk 0 Partitions 4 and 6. I don't know what's up with the double "RECOVERY D:” drive)
2. I reboot the computer with an install disk in, then rebuild the MBR with the `BootRec.exe /fixmbr` command. I also would use the `BootRec.exe /fixBoot` command, but it tells me "Access is denied."
3. I shut off the computer, remove the install disk, and reboot.
The result is that I still have GRUB, as if I didn't fix the MBR, but it doesn't boot straight to Windows. Is there something I did wrong, or maybe did not do that I should have done? Thanks for any help. If any more pictures are needed, I can try to provide those.
[Update from December 21, 2017 at 0:30: Here are some more details I found. The first update screenshot I have can be found at https://drive.google.com/file/d/1IrBPIURTZS8bJEvoWtFkPRunxhNs2j5J/view?usp=sharing and shows what happened when I tried The Paladin's method invilving the Administrative Control Panel, shown at the upper-left. It seems to be saying that it couldn't do anything. It also shows what happens when I try to delete Partition 1, the EFI partition. It first tells me that the partition was not created by Windows and that it might affect another operating system. After clicking Yes (it confirms that I want to delete it), it mentions that it is being used by an application, as shown on the bottom-left. The partition table is on the bottom-right, and as of today, I haven't been able to delete partition 4. I also removed Ubuntu from partition 6 for the sake of trying the method, which explains the unallocated space. Since then, I have reinstalled it, and according to Ubuntu's disk management tool...
My second update screenshot can be found at https://drive.google.com/file/d/1g0jrX0R4_L-raqeCnCQtLr_ZzCETHjRg/view?usp=sharing and shows Ubuntu's disk management tool. I noticed that Partition 1 is indeed the EFI system, and that Partition 4 is a Windows recovery drive. It was then that I began to understand why I couldn't delete partition 4 this time around. Other than that, this might have been because of the new installation of Ubuntu, but it seems that there is a bit of free space left over, and also that Ubuntu has 17 GB of total space rather than 16. I'll need to look into this in Windows a bit to check on it.
I figured that as long as I was going to try to fix the issue with The Paladin's method, I should at least try again to rebuild the MBR from a Windows installation disk. I already had partition 6 deleted, and because I couldn't delete p4 (which I did not at the time know belonged to Windows, as this happened before reinstalling Ubuntu and learning what each partition did) and I was afraid to delete p1 (the EFI/boot partition) I didn't delete any more partitions. I tried all of the BootRec commands in the install disk's Command Prompt, and the results of each:
/fixmbr: The operation completed successfully.
/fixBoot: Access is denied.
/scanos: brought up 0 Windows installations to write to boot
/rebuildbcd: brought up 0 Windows installations to write to boot
I'm not familiar with the latter two or what they do, so I might be saying something wrong in saying "to write to boot". Also, even though /fixmbr "completed successfully", nothing changed in the boot loader; it was GRUB as usual.
To sum it up, I tried the method presented to me, as well as the typical once again, but both to no avail. I noticed that p1 and p6 are used by Ubuntu, but p1 is boot, so I am afraid to delete it. I'm starting to think that the remedy would be to reinstall Windows completely, but due to the nature of starting from scratch, I want to use this as only a last resort. If anybody has another suggestion, I am willing to try it, and will update again based on my findings. Thank you, and thanks to The Paladin for giving me the suggestion that the trying of which led to this update.]
1. I go to Disk Management in Windows 10 and delete all of the partitions which I believe have Ubuntu on them. (list at https://drive.google.com/open?id=1ozzTGh6pE4aOH4N54jd2VdlTxaA5SktQ I delete Disk 0 Partitions 4 and 6. I don't know what's up with the double "RECOVERY D:” drive)
2. I reboot the computer with an install disk in, then rebuild the MBR with the `BootRec.exe /fixmbr` command. I also would use the `BootRec.exe /fixBoot` command, but it tells me "Access is denied."
3. I shut off the computer, remove the install disk, and reboot.
The result is that I still have GRUB, as if I didn't fix the MBR, but it doesn't boot straight to Windows. Is there something I did wrong, or maybe did not do that I should have done? Thanks for any help. If any more pictures are needed, I can try to provide those.
[Update from December 21, 2017 at 0:30: Here are some more details I found. The first update screenshot I have can be found at https://drive.google.com/file/d/1IrBPIURTZS8bJEvoWtFkPRunxhNs2j5J/view?usp=sharing and shows what happened when I tried The Paladin's method invilving the Administrative Control Panel, shown at the upper-left. It seems to be saying that it couldn't do anything. It also shows what happens when I try to delete Partition 1, the EFI partition. It first tells me that the partition was not created by Windows and that it might affect another operating system. After clicking Yes (it confirms that I want to delete it), it mentions that it is being used by an application, as shown on the bottom-left. The partition table is on the bottom-right, and as of today, I haven't been able to delete partition 4. I also removed Ubuntu from partition 6 for the sake of trying the method, which explains the unallocated space. Since then, I have reinstalled it, and according to Ubuntu's disk management tool...
My second update screenshot can be found at https://drive.google.com/file/d/1g0jrX0R4_L-raqeCnCQtLr_ZzCETHjRg/view?usp=sharing and shows Ubuntu's disk management tool. I noticed that Partition 1 is indeed the EFI system, and that Partition 4 is a Windows recovery drive. It was then that I began to understand why I couldn't delete partition 4 this time around. Other than that, this might have been because of the new installation of Ubuntu, but it seems that there is a bit of free space left over, and also that Ubuntu has 17 GB of total space rather than 16. I'll need to look into this in Windows a bit to check on it.
I figured that as long as I was going to try to fix the issue with The Paladin's method, I should at least try again to rebuild the MBR from a Windows installation disk. I already had partition 6 deleted, and because I couldn't delete p4 (which I did not at the time know belonged to Windows, as this happened before reinstalling Ubuntu and learning what each partition did) and I was afraid to delete p1 (the EFI/boot partition) I didn't delete any more partitions. I tried all of the BootRec commands in the install disk's Command Prompt, and the results of each:
/fixmbr: The operation completed successfully.
/fixBoot: Access is denied.
/scanos: brought up 0 Windows installations to write to boot
/rebuildbcd: brought up 0 Windows installations to write to boot
I'm not familiar with the latter two or what they do, so I might be saying something wrong in saying "to write to boot". Also, even though /fixmbr "completed successfully", nothing changed in the boot loader; it was GRUB as usual.
To sum it up, I tried the method presented to me, as well as the typical once again, but both to no avail. I noticed that p1 and p6 are used by Ubuntu, but p1 is boot, so I am afraid to delete it. I'm starting to think that the remedy would be to reinstall Windows completely, but due to the nature of starting from scratch, I want to use this as only a last resort. If anybody has another suggestion, I am willing to try it, and will update again based on my findings. Thank you, and thanks to The Paladin for giving me the suggestion that the trying of which led to this update.]
Facebook
Twitter
Instagram