Trying to fix Windows Boot Loader

If none of the more specific forums is the right place to ask

Trying to fix Windows Boot Loader

Postby ryankm » 2018-04-07 16:42

Debian 9.4
Intel Core i5 6500
Geforce gt 730

Earlier I was trying to ad Debian to the Windows boot loader. I used a program called EasyBCD which would ad a second grub or something and allow me in. It messed everything up, so now I got the normal GRUB just loading. I can select Windows Boot loader, but that is still messed up; no way to get into Windows 10. Apparently that program saves backups of the old settings, so I am trying to open it up with Wine.

I am having trouble with that as I need Wine mono to execute this program.

I need libtoolize to get wine mono.

When I try to 'make install' libtoolize as per install instructions I get this error:

checking host system type... Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized

Makefile:413: recipe for target 'libtool' failed
make: *** [libtool] Error 1
root@Ryan:~/Downloads/libtool-1.2#



If any one has any ideas on how to help me restore Windows boot loader or install libtoolize that would be great!

All in all I want to ad Windows 10 to the grub, and NO; the auto OS finder thingy brings up that messed up Windows Boot loader.
ryankm
 
Posts: 11
Joined: 2018-04-07 16:21

Re: Trying to fix Windows Boot Loader

Postby Wheelerof4te » 2018-04-07 19:58

https://www.tenforums.com/
This is not a Debian issue, since you don't have any problems with Debian.
User avatar
Wheelerof4te
 
Posts: 804
Joined: 2015-08-30 20:14

Re: Trying to fix Windows Boot Loader

Postby debiman » 2018-04-08 16:13

Wheelerof4te wrote:https://www.tenforums.com/
This is not a Debian issue, since you don't have any problems with Debian.

that is harsh, and i do not agree.
op clearly says tehy cannot get into windows and are trying to fix the problem from within debian.

i am not sure if running that windows app through wine will get the desired results, but if you want to try, you should find it here: https://appdb.winehq.org/

all in all, i think you should provide more information, maybe your system is fixable with linux tools.

or maybe there's a windows repair disk? iirc you can download it if you have a valid license.
User avatar
debiman
 
Posts: 2127
Joined: 2013-03-12 07:18

Re: Trying to fix Windows Boot Loader

Postby Wheelerof4te » 2018-04-08 16:49

:roll:
https://sourceforge.net/projects/boot-repair-cd/
I've used this many times before to fix MBR, I don't know if it will work on modern Windows 10/Linux dual-boots and UEFI.
User avatar
Wheelerof4te
 
Posts: 804
Joined: 2015-08-30 20:14

Re: Trying to fix Windows Boot Loader

Postby Segfault » 2018-04-08 16:55

It is not a Debian issue. Even if it is a Grub issue it still does not make it Debian issue. Grub is not part of any Linux or any other OS. It is a standalone project. MS Windows is not a part of Debian, either.
Segfault
 
Posts: 664
Joined: 2005-09-24 12:24

Re: Trying to fix Windows Boot Loader

Postby bw123 » 2018-04-08 17:04

I think there are a lot of threads and search results about the issue. I agree it's not a debian issue, but it still might be good to have some links available to others.

https://duckduckgo.com/html/?q=grub+windows+10

From what I have read, most people who dual boot prefer to use the windows efi bootloader, but some do seem to figure out how to use chainloader from grub to load the win10 os directly.

https://wiki.debian.org/DualBoot/Windows10

https://wiki.debian.org/UEFI
User avatar
bw123
 
Posts: 2928
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Trying to fix Windows Boot Loader

Postby ryankm » 2018-04-08 18:19

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 100M 0 part
└─sda2 8:2 0 931.4G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 450M 0 part
├─sdb2 8:18 0 100M 0 part
├─sdb3 8:19 0 16M 0 part
└─sdb4 8:20 0 931G 0 part
sdc 8:32 0 111.8G 0 disk
├─sdc1 8:33 0 512M 0 part /boot/efi
├─sdc2 8:34 0 95.4G 0 part /
└─sdc3 8:35 0 16G 0 part [SWAP]
sdd 8:48 0 2.7T 0 disk
├─sdd1 8:49 0 4K 0 part
└─sdd5 8:53 0 2.7T 0 part /media/root/3TB R
sr0 11:0 1 1024M 0 rom
root@Ryan:~# blkid /dev/sdb
/dev/sdb: PTUUID="36c00817-bdb9-47c1-b583-e91984c609c3" PTTYPE="gpt"


So I am tryng that manual entry method. I am going off sdb because when I tryed sda it didn't work, besides the windows 10 disk is the second disk on the devices list. But I don't no what to do with that output. Why is it PTUUID and not UUID. Do I put that ptUUID where UUID goes... There is also a non-functioning Windows 7 on here that I think I am going to wipe.... That is probably what got picked up for sda.
ryankm
 
Posts: 11
Joined: 2018-04-07 16:21

Re: Trying to fix Windows Boot Loader

Postby Wheelerof4te » 2018-04-08 19:13

You have a quatro-boot there, impressive! /s
Try boot-repair disk. It worked for me on my old box.
User avatar
Wheelerof4te
 
Posts: 804
Joined: 2015-08-30 20:14

Re: Trying to fix Windows Boot Loader

Postby sunrat » 2018-04-08 22:54

Did you try
Code: Select all
update-grub

Worked for me when it didn't initially appear after Debian installation.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2221
Joined: 2006-08-29 09:12
Location: Melbourne, Australia


Return to General Questions

Who is online

Users browsing this forum: No registered users and 4 guests

fashionable