Windows 8 inaccessible after installing Kubuntu 12.10

[SteveRiley]

Steve that was awesome.

Thank you SteveRiley. You were awesome.

Thanks, guys.

I think longnosemonkey should reinstall and start from scratch now, In orde to clean up the existing UEFI NVRAM so the next time he/she can do the install without assistance.

At this point, the NVRAM variables contain exactly what they should, and nothing more. Longnosemonkey's variable structure matches the from-scratch dual-boot build I was experimenting with last night. I wouldn't recommend to reinstall now, unless Longnosemonkey wants more hands-on experience.

Do we have a sticky thread on EFI installs? I think we are going to see a lot more of this.

The admins should put up a sticky that captures the lessons learnt from this.

We have a subforum dedicated to UEFI assistance. We also have a knowledge base subforum. Indeed, this particular thread contains a number of useful nuggets (along with a fair amount of my own idle musings, sigh). I'll figure out which portions make sense for post in the KB.

[longnosemonkey]

Thank you SteveRiley. You were awesome.

The admins should put up a sticky that captures the lessons learnt from this.

[pauly]

Steve that was awesome. I think longnosemonkey should reinstall and start from scratch now, In orde to clean up the existing UEFI NVRAM so the next time he/she can do the install without assistance. Do we have a sticky thread on EFI installs? I think we are going to see a lot more of this.

[SteveRiley]

I saw that. Alas, your Windows Boot Manager is still a bit confused, and I'll need to think about that later. I, too, am tired now.

If you were to rebuild your PC, my recommendation would be the following:

1. Clear all existing UEFI NVRAM variables for operating system boot loaders. This is a manual step that, so far, none of the automated tools do very well.
2. Ensure that Secure Boot is disabled.
3. Install Windows 8.
4. Install Kubuntu.
5. Fix GRUB to find Windows 8.
6. Enjoy.

Essentially, I've performed the above steps twice. I now see the same thing you do, but I'm not experiencing the issue where the Windows Boot Manager appears after selecting "Windows 8" from GRUB. There's something going on between UEFI boot variables and the Windows BCD that I don't have my brain wrapped around yet.

Eventually, step 5 above will become unnecessary. Hopefully step 1, too.

[longnosemonkey]

In case you missed this tidbit:

The Boot tab in msconfig says:

Windows 8 (C:\Windows) : Current OS; Default OS

There is a tab for Advanced Options and other Boot options etc. below it, but if you're not interested in that, there is only this one line in the box.

I do re-install everything once every few years to clean up all the cruft in my computer. So if I were restore my laptop to factory conditions and start installing everything from scratch, how should I do it? What steps would I take? Or will GRUB have fixed this already?

[SteveRiley]

Are we going ahead with the plan reset my laptop to factory conditions and then re-install Kubuntu or is that plan now redundant?

No. Your problem ended up being less thorny than I first imagined. No need to rebuild now.

Should I be concerned about bootkits because SecureBoot is turned off? Should I keep SecureBoot turned off for good?

Opinions on this vary. I think Secure Boot is an awfully big hammer for a rather small risk. I don't think the trade-off is worth it. The biggest risks home users face are identity theft, scams, and browser-based attacks. For malware to infect the OS in the way that Secure Boot thwarts, an attacker must penetrate other security layers first.

You seem like a big cheese... would it be possible for you see to it that these changes are rolled into GRUB/Kubuntu so that no poor soul has to go through what I have? I hope we can save a lot of people from these problems.

Nah, just a volunteer who likes helping others. It's already known that GRUB's OS-prober needs updating to find Windows 8. Work is underway to smooth Secure Boot support, too. It's just that, right now, you're kind of caught in the growth phase of these technologies

[longnosemonkey]

The Boot tab in msconfig says:

Windows 8 (C:\Windows) : Current OS; Default OS

There is a tab for Advanced Options and other Boot options etc. below it, but if you're not interested in that, there is only this one line in the box.

[SteveRiley]

Try this. Boot Windows. Then press the Windows key, type msconfig, and press Enter. Click the Boot tab. Please list each line you see in the box.

[longnosemonkey]

I'm very sleepy... so I have to go now.. but thanks for your help SteveRiley. But I have a few questions for you:

Are we going ahead with the plan reset my laptop to factory conditions and then re-install Kubuntu or is that plan now redundant?

Should I be concerned about bootkits because SecureBoot is turned off? Should I keep SecureBoot turned off for good?

You seem like a big cheese... would it be possible for you see to it that these changes are rolled into GRUB/Kubuntu so that no poor soul has to go through what I have? I hope we can save a lot of people from these problems.

[SteveRiley]

I suspect you're showing me the output of sudo efibootmgr after you ran sudo efibootmgr -b 0003 -B, because the variable "Boot0003" is now no longer in the list. That's good. I didn't think that spurious entry was causing any problem, but it's always good to keep things clean.

For now, you're in a usable state. Both operating systems are booting. I will think a bit more about how to streamline the Windows 8 side of things. Ideally, from GRUB you should simply launch straight into Windows, without being interrupted by another boot manager.

[longnosemonkey]

Konsole responds:

BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004, 0005, 2003, 2001, 2002
Boot0001* EFI Network 0 for IPv4 (08-9E-01-4C-16-A0)
Boot0002* EFI Network 0 for IPv6 (08-9E-01-4C-16-A0)
Boot0004* Ubuntu
Boot0005* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/DVDROM
Boot2003* EFI Network

I don't see any changes. Everything seems as before.

[SteveRiley]

Sorry, my mistake. The command should be:

sudo efibootmgr -b 0003 -B

Omit the "Boot" portion.

[longnosemonkey]

I tried to run that command, konsole says:

boot entry: B not found

I rebooted and everything seems the same. GRUB allows me to boot into Ubuntu, and passes me to Windows Boot Manager if I try to boot Windows 8. From Windows Boot Manager, I'm able to boot into Windows 8, but booting into Ubuntu fails.

[SteveRiley]

To be honest, this my first time to set up a Windows 8 + Kubuntu dual boot on UEFI, too

In Kubuntu, please type:

sudo efibootmgr -b Boot0003 -B

And then reboot. Now experiment.

That NVRAM variable is pointing to a nonexistent boot loader, so let's get rid of it. I don't know whether this will fix the problem you've described, though.

I'm still a little mystified why you get the "Windows Boot Manager" when you select Windows from GRUB. I'm not seeing that on my test setup.

[longnosemonkey]

I feel like a monkey because I'm simply inputting all these commands and giving you the results without knowing what I'm doing. But SteveRiley, whatever you're doing seems to be working, at least partly.

I input your commands and made the changes you gave me. After saving them, I entered the commands again and went back checked to see if they had saved. They had.

I rebooted and lo, GRUB offered me a fourth boot option: Windows 8. When I chose it, GRUB went away and Windows Boot Manager came on, offering me the option to boot either Windows 8 or Ubuntu. If I chose the first option, I could boot into Windows 8 with SecureBoot disabled. (I checked the UEFI to make sure)

However, if I tried to boot Ubuntu from Windows Boot Manager, I got the same error as before:

"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:" and offered me 3 options - to use my windows installation disc and restart my computer, choose my language settings and click Next, or Click repair your computer.

This was followed by:

File: \EFI\ubuntu\grubx64.efi
Status: 0xc000007b
Info: The application or operating system couldn't be loaded because a required file is missing or contains errors.