![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
I installed Debian 7 on my machine, and that somehow upset the delicate sensibilities of my Windows 8 installation. I'm not sure how or why, but I want to fix it.
What happens is that bootmgfw.efi kicks off and I get the black screen with a Window on. There it hangs. I assume bootmgfw is showing that screen, which would mean that things are OK at least until the point where it tries to load the BCD and on. I don't exactly have a clear, detailed idea of the boot process exactly.
I have my USB stick with the Win8 install on it. The "automatic repair" does not work. It wants to restore a system restore point which I'm not keen on trying except as an absolute last resort.
The first impulse was to rebuild the BCD (that's what the Internet tells you to do), which I did (using bcdboot ...), to no avail.
What's more, the BCD actually looks okay to me now, given my very limited knowledge about how it's supposed to look.
Essentially my setup is a 120GB M4 as disk 1 where I originally installed Windows 8 in GPT/EFI mode on an 89GB partition. I had reserved ~30GB from the get go for a future linux install, so there's been no partition resize or anything here.
Booting the Win8 installation media on the USB stick in UEFI mode gives the following:
I have no idea why the 27GB linux partition (volume 2) has a drive letter here, but it shouldn't be fatal. I have assigned I: to volume 4 (the ESP -- EFI System Partition) using 'assign' previously, it doesn't have a letter assigned normally (which seems to be standard).
Looks fine to me.
And here's the dump of the current (rebuilt) BCD. Note how the device partition seems ok, as does the osdevice and systemroot:
My hypothesis has been that the extra partition somehow threw the BCD out of whack, but I can't see anything wrong with it.
I'm actually running out of ideas here. I have no idea what it's hanging on. My next step would probably be to open the
computer up and physically disconnect the other drives just to make sure it's not getting confused by them somehow.
I have even verified the sha1 signatures of the efi files on the ESP vs the install media, and they check out.
# sha1sum /boot/efi/EFI/Microsoft/*.efi
765ce680a932d9f36a6b09c2191c9e2cab1a89cd bootmgfw.efi
8e3d465e4eb78e5f816721699c1d7f1f63a4a5cb bootmgrefi
Haven't been able to verify this one since it's not available unpacked on the install media:
# sha1sum /media/1050D37250D35D52/Windows/System32/winload.efi
28328e1c87ecd3d45828c69ba1c21b3ed6b032c4 /media/1050D37250D35D52/Windows/System32/winload.efi
So... suggestion? Note, this is EFI, suggestions such as "bootrec /fixmbr" aren't helpful unless they come with an explanation as for why they should work.
What happens is that bootmgfw.efi kicks off and I get the black screen with a Window on. There it hangs. I assume bootmgfw is showing that screen, which would mean that things are OK at least until the point where it tries to load the BCD and on. I don't exactly have a clear, detailed idea of the boot process exactly.
I have my USB stick with the Win8 install on it. The "automatic repair" does not work. It wants to restore a system restore point which I'm not keen on trying except as an absolute last resort.
The first impulse was to rebuild the BCD (that's what the Internet tells you to do), which I did (using bcdboot ...), to no avail.
What's more, the BCD actually looks okay to me now, given my very limited knowledge about how it's supposed to look.
Essentially my setup is a 120GB M4 as disk 1 where I originally installed Windows 8 in GPT/EFI mode on an 89GB partition. I had reserved ~30GB from the get go for a future linux install, so there's been no partition resize or anything here.
Booting the Win8 installation media on the USB stick in UEFI mode gives the following:
Code:
I:\EFI\Microsoft\Boot>diskpart
Microsoft DiskPart version 6.2.9200
Copyright (C) 1999-2012 Microsoft Corporation.
On computer: MININT-JU4SK5T
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 238 GB 563 MB
Disk 1 Online 119 GB 1422 MB *
Disk 2 Online 1863 GB 101 MB
Disk 3 Online 7695 MB 0 B
DISKPART> select disk 1
Disk 1 is now the selected disk.
DISKPART> list part
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 300 MB 1024 KB
Partition 2 System 100 MB 301 MB
Partition 3 Reserved 128 MB 401 MB
Partition 4 Primary 89 GB 529 MB
Partition 5 Primary 27 GB 89 GB
DISKPART> list vol
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C Samsung830 NTFS Partition 230 GB Healthy
Volume 1 D NTFS Partition 89 GB Healthy
Volume 2 E RAW Partition 27 GB Healthy
Volume 3 H Recovery NTFS Partition 300 MB Healthy Hidden
Volume 4 I FAT32 Partition 100 MB Healthy Hidden
Volume 5 F WD20EADS 2T NTFS Partition 1862 GB Healthy
Volume 6 G ESD-USB FAT32 Removable 7694 MB HealthyI have no idea why the 27GB linux partition (volume 2) has a drive letter here, but it shouldn't be fatal. I have assigned I: to volume 4 (the ESP -- EFI System Partition) using 'assign' previously, it doesn't have a letter assigned normally (which seems to be standard).
Looks fine to me.
And here's the dump of the current (rebuilt) BCD. Note how the device partition seems ok, as does the osdevice and systemroot:
Code:
I:\EFI\Microsoft\Boot>bcdedit /store BCD /enum
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=I:
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {default}
resumeobject {5664034e-bcba-11e2-aea3-a3e5f6caddca}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \Windows\system32\winload.efi
description Windows 8
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \Windows
resumeobject {5664034e-bcba-11e2-aea3-a3e5f6caddca}
nx OptIn
bootmenupolicy Standard
detecthal YesMy hypothesis has been that the extra partition somehow threw the BCD out of whack, but I can't see anything wrong with it.
I'm actually running out of ideas here. I have no idea what it's hanging on. My next step would probably be to open the
computer up and physically disconnect the other drives just to make sure it's not getting confused by them somehow.
I have even verified the sha1 signatures of the efi files on the ESP vs the install media, and they check out.
# sha1sum /boot/efi/EFI/Microsoft/*.efi
765ce680a932d9f36a6b09c2191c9e2cab1a89cd bootmgfw.efi
8e3d465e4eb78e5f816721699c1d7f1f63a4a5cb bootmgrefi
Haven't been able to verify this one since it's not available unpacked on the install media:
# sha1sum /media/1050D37250D35D52/Windows/System32/winload.efi
28328e1c87ecd3d45828c69ba1c21b3ed6b032c4 /media/1050D37250D35D52/Windows/System32/winload.efi
So... suggestion? Note, this is EFI, suggestions such as "bootrec /fixmbr" aren't helpful unless they come with an explanation as for why they should work.
Last edited: