Windows Vista not shown on Grub Boot screen

[tom_middleton]

I have just installed Linux on a partition of my hard drive. Computer boots up and gives me the grub boot screen where i can choose from: ubuntu, some memory tests and windows recovery environment (loader).

But no Windows Vista.

When I boot the windows recovery option the windows boot loading screen comes up but then the screen turns blank but the hard drive is still working and the wifi light also comes on my keyboard.

Ubuntu is working completely fine I just need to find a way of getting Grub to display Vista instead of the Recovery environment.

Here is my Boot Info Script:

[Quackers]

Welcome to UF :-)
Please post boot script output in code tags, like this

Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #4 for (,msdos4)/boot/grub.

sda1: __________________________________________________ _______________________

File system: vfat
Boot sector type: Dell Utility: Fat16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /COMMAND.COM

sda2: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /Windows/System32/winload.exe

sda3: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /bootmgr /Boot/BCD /Windows/System32/winload.exe

sda4: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda4 and
looks at sector 377010256 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/menu.lst /boot/grub/grub.cfg /etc/fstab
/boot/grub/core.img

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 63 289,169 289,107 de Dell Utility
/dev/sda2 290,816 21,262,335 20,971,520 7 HPFS/NTFS
/dev/sda3 * 21,262,336 364,141,987 342,879,652 7 HPFS/NTFS
/dev/sda4 364,142,592 429,801,471 65,658,880 83 Linux


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 07D9-030E vfat DellUtility
/dev/sda2 88708B7A708B6DAE ntfs RECOVERY
/dev/sda3 72AC0D18AC0CD90D ntfs Windows
/dev/sda4 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ext4
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sda4 / ext4 (rw,errors=remount-ro,commit=0)


=========================== sda4/boot/grub/menu.lst: ===========================

title Windows Vista
root (hd0,2)
makeactive
chainloader +1

=========================== sda4/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
echo 'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows Recovery Environment (loader) (on /dev/sda3)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 72ac0d18ac0cd90d
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

=============================== sda4/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed / ext4 errors=remount-ro 0 1

=================== sda4: Location of files loaded by Grub: ===================


193.0GB: boot/grub/core.img
188.7GB: boot/grub/grub.cfg
193.0GB: boot/grub/menu.lst
187.0GB: boot/initrd.img-2.6.35-22-generic
193.0GB: boot/vmlinuz-2.6.35-22-generic
193.0GB: boot/vmlinuz-2.6.35-24-generic
187.0GB: initrd.img
193.0GB: vmlinuz


For some reason when Vista is involved, Grub names the Windows Loader wrongly. Your entry in the grub menu for the Windows Recovery Loader actually points to sda3, which is your actual Vista installation, so it will boot Vista just fine if you select it.

[Quackers]

Duplicate due to dodgy forum behaviour!
It took 8 minutes to accept this post!

[Quackers]

Duplicate due to dodgy forum behaviour!

[Quackers]

Duplicate due to dodgy forum behaviour!

[tom_middleton]

I tried to put it in the code but didn't really know how too.
When I boot the recovery the usual windows boot comes up but then then when it would usually show the log in screen, it just shows a blank black screen. Thats why I assumed it wasn't the right one.

[tom_middleton]

I have also created a Windows Vista Recovery disk to see if this will fix the booting problem but the disk does not load on startup and grub continues to. Even after putting the cd drive as 1st in the boot list. Any ideas on this?

[Quackers]

For code tags you can just type
(without the space after the e ) before the script you want to include, the type after the script.
Or you can click on New Reply rather than quick reply, and click on the # symbol in the toolbar, then paste what you want inbetween to 2 generated code tags.

I don't know what's causing your Vista problem. Everything seems ok, other than the mis-naming. I'll have another look.

[wilee-nilee]

sda4: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda4 and
looks at sector 377010256 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/menu.lst /boot/grub/grub.cfg /etc/fstab
/boot/grub/core.img

You have both grub legacy and grub2 in Ubuntu and the script. Use this link to purge Grub then reinstall grub2, probably the chroot method is needed. Read the instructions carefully.
http://ubuntuforums.org/showthread.php?t=1581099


The grub-legacy is chain loading sda2 the recovery, or at least trying to.
=========================== sda4/boot/grub/menu.lst: ===========================

title Windows Vista
root (hd0,2)
makeactive
chainloader +1

[tom_middleton]

I added in the bit for windows vista on the menu.lst to try and fix the problem but that was before I knew I had Grub2.
Do I still go ahead with the advice you gave?

[Quackers]

No wonder I've never seen it before :-) You scuppered yourself :-)
I thought sda4 was an extended partition - I must concentrate more!
Yes wilee-nilee's suggestion is definitely the way to go, from the link he gave.

[tom_middleton]

Do i need to chroot even if i'm not using the liveCD.
Can't i do it from my Ubuntu OS.

If you could clarify which steps to take as i'm abit uneasy. I don't want to ruin my system.
Thanks

[Quackers]

This is something that must be done via the chroot method from within the live cd/usb.
If you boot from the live cd/usb then come back here, I will collect the necessary commands for you.

[tom_middleton]

Right. I'm on the Lice CD. What now?

[Quackers]

From within the Live cd desktop, and making sure you are connected to the internet, open a terminal and copy/paste these commands in one at a time pressing enter after each one.


sudo mkdir /mnt/temp
sudo mount /dev/sda4 /mnt/temp
for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt/temp$i; done
sudo cp /etc/resolv.conf /mnt/temp/etc/resolv.conf
sudo chroot /mnt/temp
At this point your terminal prompt should change from ubuntu@ubuntu to root@ubuntu - if it doesn't something is wrong.

At this point go to the link below and follow the guide from 2 to 8 in the section headed Why chroot (in red)

http://ubuntuforums.org/showthread.php?t=1581099

[tom_middleton]

What is my sdXY and sdXZ ?

Sorry i'm not really clever at this. It changed to root@ubuntu so we are on the right track.

I really appreciate this by the way. I hope it will all work.

[tom_middleton]

And do I use B: The Wubi only?

[Quackers]

sdXZ???
Did you go to number 2 in the Why chroot part? Or are you at part A ?

[Quackers]

You should be at number 2 !!!!! You are before then at A

[tom_middleton]

Haha. My bad. Told you I wasnt on the ball.
Right. I'll work my way through from 2.
thanks

[tom_middleton]

At step 4 do install grub on sda and sda4?

[Quackers]

sda by pressing the space bar etc.

From the guide
"Do not select a partition ( example: [ ] /dev/sda5 , etc)."

[tom_middleton]

ok ive done that all and rebooted. I am now on the Ubuntu OS as i was before but the Windows recovery boot still hasn't changed. Still goes black when it should go to log in screen.

Please please please help

[Quackers]

Please re-run the boot script and post the new results. It may be called results1.txt

[tom_middleton]

here it is.



Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #4 for (,msdos4)/boot/grub.

sda1: __________________________________________________ _______________________

File system: vfat
Boot sector type: Dell Utility: Fat16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /COMMAND.COM

sda2: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /Windows/System32/winload.exe

sda3: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /bootmgr /Boot/BCD /Windows/System32/winload.exe

sda4: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda4 and
looks at sector 377010256 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 63 289,169 289,107 de Dell Utility
/dev/sda2 290,816 21,262,335 20,971,520 7 HPFS/NTFS
/dev/sda3 * 21,262,336 364,141,987 342,879,652 7 HPFS/NTFS
/dev/sda4 364,142,592 429,801,471 65,658,880 83 Linux


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 07D9-030E vfat DellUtility
/dev/sda2 88708B7A708B6DAE ntfs RECOVERY
/dev/sda3 72AC0D18AC0CD90D ntfs Windows
/dev/sda4 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ext4
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sda4 / ext4 (rw,errors=remount-ro,commit=0)


=========================== sda4/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
echo 'Loading Linux 2.6.35-24-generic ...'
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
echo 'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/11_Windows ###
menuentry “Windows Vista″ {
set root=(hd0,3)
chainloader +1
}
### END /etc/grub.d/11_Windows ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set 51dbed70-d4ba-42a6-84aa-ccf4409ba6ed
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows Recovery Environment (loader) (on /dev/sda3)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 72ac0d18ac0cd90d
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

=============================== sda4/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=51dbed70-d4ba-42a6-84aa-ccf4409ba6ed / ext4 errors=remount-ro 0 1

=================== sda4: Location of files loaded by Grub: ===================


193.0GB: boot/grub/core.img
188.9GB: boot/grub/grub.cfg
187.3GB: boot/initrd.img-2.6.35-22-generic
187.2GB: boot/initrd.img-2.6.35-24-generic
193.0GB: boot/vmlinuz-2.6.35-22-generic
193.0GB: boot/vmlinuz-2.6.35-24-generic
187.2GB: initrd.img
187.3GB: initrd.img.old
193.0GB: vmlinuz
193.0GB: vmlinuz.old

[Quackers]

From an Ubuntu point of view things look ok except for grub2 being installed to the boot sector of sda4. I hoped the purge would have removed that, but obviously not.
If you choose to boot Windows does the screen go black, or is there any script on there?
Did you delete or resize a Windows partition in order to create the Ubuntu partition?

[tom_middleton]

Yea i resized the windows part to make space available to create a partition for ubuntu.

[wilee-nilee]

Yea i resized the windows part to make space available to create a partition for ubuntu.


Have you run

sudo update-grub

In Ubuntu do it and post the terminal output.

[Quackers]

Did you defrag the C: partition first? What software did you use to do that?
Did you try to boot Windows after doing the change?

[tom_middleton]

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.35-24-generic
Found initrd image: /boot/initrd.img-2.6.35-24-generic
Found linux image: /boot/vmlinuz-2.6.35-22-generic
Found initrd image: /boot/initrd.img-2.6.35-22-generic
“Adding Windows”
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Recovery Environment (loader) on /dev/sda3
done

[wilee-nilee]

Did you defrag the C: partition first? What software did you use to do that?
Did you try to boot Windows after doing the change?

I think your on the right track, the sda3 is in the script now.

[tom_middleton]

I used Power Defragmenter i think.
Ive never been able to boot to windows since ive installed ubuntu.

Any ideas how we can move on so Windows is available to me. I can access all my files but i have programs like Microsoft office i need to access from windows.

[Quackers]

Did you use Windows disk management screen to resize C: ?
Is your recovery disc a cd or is it one of 2 or more dvd's?

[wilee-nilee]

I used Power Defragmenter i think.
Ive never been able to boot to windows since ive installed ubuntu.

Any ideas how we can move on so Windows is available to me. I can access all my files but i have programs like Microsoft office i need to access from windows.

If you don't have a Vista recovery disc here is one we will use it to do a chkdsk /r and or reload the MS bootloader to see if it actually boots.
http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/

[tom_middleton]

i made a cd using http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/

but this wont start when i reboot.
I tried to make a partition in Windows default software but I think i fiddled about with it when in the wubi installation.

[Quackers]

If the resize didn't go well Windows is likely to have stopped booting at that time. You should always reboot Windows after partition changing. It is very finicky about it. Windows holds data right at the end of the partition and if that data is lost it will stop booting. Even so, a pure black screen is not good.

I think chkdsk C: /r from the comand prompt in the recovery console should be run and re-run until no errors are found, as wilee-nilee suggests.

Edit, you will need to set the bios to boot from the cd first.

[tom_middleton]

I cant get my windows recovery disk to work. even when i put the cd drive first.

[wilee-nilee]

I cant get my windows recovery disk to work. even when i put the cd drive first.

So there is a per-session boot from menu outside the bios I get there with a f12 tapping at powering on. Yours may be another f key or the esc.

With my old dell laptop it is f12.

[Quackers]

Did you burn the file to a cd or did you burn the image? If you download an iso file you must burn the image.
I suggest you download the correct repair image from the link wilee-nilee provided. Make sure you get the right architecture (32 bit or 64 bit) and then burn the image to cd using brasero (bottom option on screen iirc).

This disc, along with recovery discs should have been made from within Windows long ago. You really can't afford to take chances partitioning without the tools to recover your system!

[tom_middleton]

i dont understand how this can help.
what would i do if i were to find this menu?

[wilee-nilee]

i dont understand how this can help.
what would i do if i were to find this menu?

You would choose the cd reader to boot with. This works when the bios having the cd reader first is not working.

You did burn as an image as Quackers suggests as well I assume.

Actually knowing this key prompt will keep you from having to changing the bios when you want to boot anything, like a thumb, cd, or a external HD.

[tom_middleton]

ok so ive solved some kind of problem.

I've used the repair disk and went on the command prompt and did the following.

diskpart
select disk 0
select partition 3
active
exit

Then rebooted

bootrec /fixmbr
bootrec /rebuildcd
bootrec /fixboot

Now when i boot it goes straight to windows. I know ubuntu is still there but how can i now access it?

[Quackers]

You would need to re-install grub to the mbr of the drive from the live cd/usb desktop, as you did earlier.

[tom_middleton]

wouldnt that install the whole ubuntu os again?
can you give me some detailed steps please?

I am very grateful for this. Ive been trying to get windows back for days!

[Quackers]

No, it will just re-install grub.
Boot from the Ubuntu Live cd/usb and when the desktop loads open up a terminal.
As your Ubuntu boot files are intact, it should be enough to use the short way.
Try this please

sudo mount /dev/sda4 /mnt
sudo grub-install --root-directory=/mnt /dev/sda

Then reboot. This time Ubuntu should load directly. If it does, open a terminal and run
sudo update-grub
then watch as grub.cfg is run, to see if the Windows Loader is picked up. If it is, you can try rebooting. You should then get a grub menu with the choice to boot Windows. Select it and check it boots ok.

[tom_middleton]

ok i will try shortly.
is grub2 the best boot chooser to use?

[Quackers]

For later versions of Ubuntu, definitely :wink:

[tom_middleton]

wow!
Quackers and wilee-nilee, I can not thank you enough. I can now access both Vista and Ubuntu.
Any ideas on how to tidy things up. Like removing the unnecessary options that come up with grub and potentially renaming Windows Recovery to Windows Vista.

Not essential as the problem is solved just abit of tidying.
Thank you!

[Quackers]

Excellent :-) You're welcome.
Could you mark the thread as solved using the Thread Tools near the top of the page? Thanks.
Your grub menu queries will be answered in this guide by drs305

http://ubuntuforums.org/showthread.php?t=1287602