1

So I have a lot going on here, unfortunately. I'm trying to work through the issues but I've found myself stuck. I THINK that the issue in the title is now my problem as I have been able to fix my EFI boot partition, and from my untrained eye things appear to be correct, but I've noticed that my windows partition shows as 'unknown' in disk part and perhaps that is why my win7 is now getting stuck forever at the windows boot logo.

Since I'm a new user I cannot post more than two links, I've edited the URL's so that they can be posted.

My original issue was posted here (for background) -

https://answers.launchpad.net/ubuntu/+question/293607

Since then, I've done a number of things, such as running Easy Recovery Essentials from NeoSmart, and obviously the windows recovery boot repair, endlessly along with ubuntu boot-repair in 16.02 LTS. A quick note, 14.02 LTS i saw a EFI error on boot, so i was thinking maybe that boot-repair wouldn't be able to correctly repair things unless the live cd was correctly launched in EFI mode. The same with recovery essentials, when i boot the cd it doesn't give me the UEFI option for booting the cd, so perhaps that also wont work for my EFI situation? My windows 7 does show UEFI at the boot and I did attempt to do all of the bootrec.exe commands in windows recovery cmd. The only part I could not do was the bootsect.exe /nt60 SYS /mbr command from this guide -

https://neosmart.net/wiki/fix-uefi-boot/#Fix_UEFI_Boot_in_Windows_7

Because it complained that I had to be in bios mode/non EFI mode to do it. When i booted win7 without UEFI, then win7 complained I cannot enter recovery environment because it needs to be EFI. Damned if you do, damned if you dont :) But my understanding is that EFI does not use a MBR so im not sure how that is a relevant fix anyways?

I went from not being able to see the OS, to resolving that part by changing the ID of my windows partition located here -

Issue with a Windows 7 Boot issue - involving the BCD perhaps

Now the windows recovery environment see's my OS, but its location is "(Unknown)" at the first screen and "Unknown" in the 'type' column in disk part.

My most recent boot-repair attempt is located here -

http://paste2.org/9Gb5sUWn

The boot summary info prior to that attempted repair is here -

http://paste2.org/7Xt9jNFs

I'm a little curious as to why my sda3 (windows install partition) was showing up as a EFI partition? In Gparted it shows as a ntfs partition, and I've of course ran all the chkdsk and other tools on it to ensure there's nothing wrong with it.

I'm thinking changing the ID of the partition might have screwed with things, but when i ran bootrec /rebuildbcd I think it should have fixed it? When I first did it, it did see the OS, but running bootrec /rebuildbcd it could not find the OS. Then I changed the ID on partition 3 and it found it.

I've also tried renaming bcd to bcd.old after changing attributes and then trying bootrec /rebuildbcd again, but it identifies "0" windows installations and I've noticed that there is no mounted windows OS during the windows recovery environment. Perhaps this is the issue? It see's the OS because at the very first screen after clicking 'repair windows' from the boot cd, it see's the OS (windows 7 professional) but just status location (Unknown).

I did all of that following this guide -

http://pcsupport.about.com/od/fixtheproblem/ht/rebuild-bcd-store-windows.htm

Maybe it needs to be mounted before I can repair it? Not sure. Losing my mind over this :(

Here is a picture of what disk part shows currently -

http://imgur.com/SIIQ85j

The last windows repair attempt I've tried says its unable to repair the system and under the diagnosis and repair details I see "A patch is preventing the system from starting." under the "Software installation log diagnosis" section (there's a lot more but they are all error 0x0 which seems like no issues found)

System Disk =\Device\Hardisk0
Windows directory = \\?\GLOBALROOT\Device\HardiskVolume3\Windows

If you guys need me to generate any information please just advise what to do and I will supply with as much diagnostic info as needed. And if anyone is wondering, the data is fine on the partition, I can mount and access my windows partition in ubuntu or other explorers and transfer the data etc.

1 Answer 1

2

It is unknown because you have entered an undefined partition type GUID.

What you have entered:

C12A7328-F81F-11D2-BA4B-00A0C93EC930

While the correct type GUID for EFI System partition is:

C12A7328-F81F-11D2-BA4B-00A0C93EC93B

(0 vs B at the end)

In any case, you should use the following type GUID:

EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

which is Basic data partition in Microsoft Windows.

Since your disk is a GPT disk, you must use UEFI boot. There is no boot code from Windows that is capable of legacy booting a Windows installation on a GPT disk.

For UEFI boot, bootsect and bootrec is pretty much useless (except MAYBE bootrec /rebuildbcd), since UEFI boot is purely file-based (EFI binaries/executables), while bootsect/bootrec only deals with boot code on the MBR/boot sector.

If bootrec /rebuildbcd still doesn't help after you revert Partition 3 to Basic data partition, then you may consider bcdboot. You MIGHT want to delete \EFI\Microsoft under the ESP (Partition 1) first after you mount it with mountvol drive: /s (where drive: can be any available drive letter), or simply reformat it (FAT32) if it's not shared with Ubuntu or so. Then, run:

bcdboot X:\Windows

where X: is the drive letter of Partition 3 under the current environment (so check with diskpart or so first).

P.S. There is a high chance that the actual installation (on Partition 3) is broken or messed up. I suppose how to fix that depends on what error you see when you boot it (after you reinstall Windows Boot Manager and build a new BCD store with bcdboot X:\Windows from it).

1
  • Tom - You nailed it! After changing the GUID to "EBD0A0A2-B9E5-4433-87C0-68B6B72699C7" , then deleting my boot partition and running bcdboot it solved all my issues!!! bootrec /rebuildbcd did not help my situation, it did not find any windows installations when I ran it, but bcdboot did the trick after the GUID was fixed. After spending so many days on this it is overwhelming to have everything working again, thank you so much!
    – seanpf
    May 15, 2016 at 23:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .