I upgraded, and now I have this error...

[bcbc]

From the release notes:

Upgrading Wubi systems from 10.04 LTS is known to fail, and is not recommended at this time. (653134)

If you have already upgraded and find that the system reboots, hangs or drops you at a grub prompt when selecting Ubuntu (with or without error messages), then first try to replace the c:\wubildr file from the one in c:\ubuntu\winboot\wubildr (change 'drive' if necessary and backup c:\wubildr first as a precaution). This fix has been confirmed by many different people, as it appears that in many cases the upgrade is corrupting the wubildr file.

Otherwise another workaround is to boot a live CD, loop mount the wubi root.disk, edit the grub.cfg (gksu gedit /mountpoint/boot/grub/grub.cfg) and remove all lines above the first "menuentry".

If you get a read-only error on grub.cfg, then either use vi or nano, or before running gedit first run:
sudo chmod +w /mountpoint/boot/grub/grub.cfg
Note: if you install kernel updates, new kernels, remove kernels, run update-grub etc. you'll have to reapply the workaround as grub.cfg is regenerated automatically. It's easier to do this before you reboot (or you'll have to use the live CD again).

PERMANENT MANUAL FIX:
I am working on completing testing for this but so far it works on 10.04.1 and 10.10 which all are affected by the same issue. http://ubuntuforums.org/showpost.php...0&postcount=78
You still need to boot the wubi before applying the permanent fix.

[Rubi1200]

From the release notes:


If you have already upgraded and find that the system reboots or hangs when selecting Ubuntu (with or without error messages), then a workaround is to boot a live CD, loop mount the wubi root.disk, edit the grub.cfg (gksu gedit /boot/grub/grub.cfg) and remove all lines above the first "menuentry".

Thanks for this information bcbc; much appreciated.

Couple of questions:

1. prior to this I have observed that you were recommending that users should reinstall the Windows bootloader (in most cases) to correct the problem.

Important Note to Wubi (Windows Ubuntu) Users: Grub Update results in "No Such Disk":
A late July 2010 Grub 2 update is causing a "no such disk" error for some users of WUBI, resulting in an unbootable system. If the system doesn't display the original Windows menu, the most likely cause of the failure is that Grub 2 was installed in the MBR and/or on the Windows partition. To correct this, restore the Windows bootloader using this link:
How to restore the Ubuntu/XP/Vista/7 bootloader

Whether the failure is due to improper user selections or Grub 2's failure to recognize a Wubi install, it has been reported in the following bug and users can review it for status updates and recovery options when they become available:
https://bugs.launchpad.net/wubi/+bug/610898

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

2. is the method suggested in your post above mine now the preferred way of dealing with this issue?

Thanks in advance,
Rubi

[bcbc]

Thanks for this information bcbc; much appreciated.

Couple of questions:

1. prior to this I have observed that you were recommending that users should reinstall the Windows bootloader (in most cases) to correct the problem.

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

2. is the method suggested in your post above mine now the preferred way of dealing with this issue?

Thanks in advance,
Rubi

You're right, Rubi. I should have clarified.
The problem that bug 610898 refers to is still an issue. The symptom of this is that your computer boots straight to a grub rescue prompt instead of the windows boot manager. This bug only affects wubi installs to a partition other than the main windows partition, and only if the user elects to install the grub-pc bootloader to their hard drive master boot record (MBR). The fix for this remains to reinstall the windows bootloader.

But there is a new problem involving grub2 changes that are breaking wubi upgrades to 10.10. The symptoms of this are that you still boot to the windows boot manager, and can boot windows, but whenever you try to boot Ubuntu it either reboots or hangs (before displaying the grub menu). It may or may not display some error messages e.g. error: command loadfont/gfxterm not found.
At present this affects any wubi install (https://bugs.launchpad.net/bugs/653134). From Colin Watson's recent comment on this bug it is unlikely that a wubi upgrade will be possible anytime soon for a wubi install on a different partition to windows (this is where it's related to 610898 ). And at present any wubi upgrade may fail (results are inconsistent and no fix has yet been released).

[Rubi1200]

Excellent!

This will definitely be very useful when it comes to helping users who face these problems.

Thanks bcbc

[sjsu]

I am just new to this forum and your answer just gave me what I was looking for. I had this problem and had to reinstall wubi totally three times. Last time even my windows got corrupted. Thanks for the info

[jonthomas83]

Hi all, I'm gutted my first post here is as a result of needing help, but here goes.

I've updated within the last hour. 83 updates needed. I had to restart and after I did so, it hasn't been able to load Ubuntu since.

I run a dual boot machine with Windows XP and it keeps looping me back to the OS selection, if I press Ubuntu it loops, Windows is fine.

Have I lost all my work or is there a way back from this?

Any help would be greatly appreciated, thank you.

[bcbc]

Hi all, I'm gutted my first post here is as a result of needing help, but here goes.

I've updated within the last hour. 83 updates needed. I had to restart and after I did so, it hasn't been able to load Ubuntu since.

I run a dual boot machine with Windows XP and it keeps looping me back to the OS selection, if I press Ubuntu it loops, Windows is fine.

Have I lost all my work or is there a way back from this?

Any help would be greatly appreciated, thank you.

Nah - that sounds totally fixable. Have a look at the Wubi megathread and post there if you need help.

[jonthomas83]

Nah - that sounds totally fixable. Have a look at the Wubi megathread and post there if you need help.

That's great news, thank you, ill take a good look and will post there. Thanks again for your time.

EDIT: Problem fixed, thank you so much! (for anyone else who sees this, it was "Problem 2, Solution 1" in the above WUBI thread link). Thanks again bcbc, you're a legend!

[svegress]

I noticed some reports that copying c:\ubuntu\winboot\wubildr over c:\wubildr fixed the problem. It's unconfirmed, but easy to try without using live CD. (If you installed on another 'drive' change as appropriate).

With gratitude everyone, the copying of the wubibldr file to the Windows root directory worked for me.
Booting with Windows 7, I renamed c:\wubildr as a precaution and made sure that I only copied and not moved C:\ubuntu\winboot\wubildr to c:\ Three minutes work as opposed to a lot of messing around with files and partitioning that I barely understand. Then a simple restart and Ubuntu with all my files intact came up as normal. I will now write a note for filing in the computer's documentation box so I will discover the answer again the next time wubi refuses at the starting gate.

Wubi is a wonderfully reliable half way house--except when it stuffs up like this. I can remember going through much the same pain when I first moved towards Ubuntu trying to use the beta wubi. I learnt that time that a good, uptodate backup is essential insurance. If I hadn't found this set of posts I would have been reconstructing from the ground up and then hoping that my incremental backup done with Simple Backup over the last few days had worked.

You might ask why I bother to stay with Wubi instead of partitioning for a dual boot. A real gotcha from Microsoft: the new Compaq Presario CQ56 has four partitions on the internal disk taken up by Windows and that is the limit to the number of partitions allowed. If anyone knows a way around this, I am listening.

[crienoloog]

@svegress: lucky for you...
However it didn't work for me... I already had a newer wubildr in my Windows root folder, but to test I renamed it wubildr(2) and copied the one from /ubuntu/winboot folder...
Ubuntu still gives me the double error: file not found and returns start-up.