Last edited by oldfred; December 14th, 2012 at 11:06 PM. Reason: Added clickable link
Welcome to the forum.
What is the problem?
It looks like Boot-Repair made some fixes. Grub2's os-prober does not create correct chain load entries, but Boot-Repair does.
Wrong style chain boot entry
These entries do not work:
'Windows ...) (on /dev/sdXY)'
Some seem to have issues with Sony.
Sony VAIO E Series Windows 8/Ubuntu 12.10 Dual Boot, EFI help
Sony - manually copy grub efi files & rename to make them work post #3
Sony - Manually copied but still some issues.
Hi oldfred, thanx for responding.
My main problem is that it won't load windoze. Ubuntu loads without problems.
How can this be solved?
Boot repair will automatically add a correct chain boot entry. Grub will still have its entries that do not work.
Post the link to the BootInfo report that this creates. Is part of Boot-Repair:
Boot Repair -Also handles LVM, GPT, separate /boot and UEFI dual boot.:
You can repair many boot issues with this or 'Create BootInfo' report (Other Options) & post the link it creates, so we can see your exact configuration and diagnose advanced problems.
Install in Ubuntu liveCD or USB or Full RepairCD with Boot-Repair (for newer computers)
I have already followed the linx you provided (I think).
Yes, the boot options are different after trying it but other than Kubuntu, nothing else loads.
So I'm left wondering what I should do....
It should also be noted that
#1 windoze recovery could be loaded prior to running boot-repair
#2 I was unable to shrink a windoze partition and re-partitioned the disk using gparted before installing Kubuntu.
I run boot-repair again work and then noticed one of the error messages when choosing to load windoze saying that it could not load secure boot is enabled.
So I disabled secure boot from bios and was able to load windoze as usual.
Now let's see if it is able to load linux!
yep, Kubuntu loads as expected!
Glad it is working, but it was secure boot that stopped Windows from working?
Considering that after running boot repair it was the *only* variable changed, I'd say yes.
Now, I don't pretend to understand it but oh well....
Many thanx for pointing me to boot-repair!