wubi installer's pyrun.exe says "no disk"

Correction:

in the above description, where i said:

"In Ubuntu 8.10 (which I no longer have installed on my system), after I inserted the CD..."

it should read:

"With the Ubuntu 8.10 CD, after I inserted the CD..."

forgive the mistake again...i am still not writing that last paragraph clearly. The entire last paragraph of my original bug report should read as below:

With the Ubuntu 8.10 CD, after I insert the CD, I correctly get a pop-up that presents 3 installation options (and I want to choose the 2nd one: install inside windows). With the 9.04 CD, however, i get this error message box and, sometimes, if i keep clicking the various buttons on the error message window randomly like 50 times (Cancel, Try Again, Continue, and the little close "X")...I MIGHT eventually get the installation options. But sometimes I cannot get to the installation options at all (in which case, i must actually restart windows to get rid of the pop-up error message).

update...

1. i restarted windows and then inserted the 9.04 CD.
2. the message is now "Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6bf7c"
3. clicking "cancel" or the "X" on the error message 8 times gets me to the installation options dialog.

i restarted windows again with same results. i decided to go ahead with the installation at this point, so i clicked "install inside windows"

the installation went okay except at certain points the error message "Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6bf7c" would pop up and i would have to click cancel 4 times (not 8 as at the beginning) in order to get the installation to continue.

once installed, ubuntu 9.04 is working okay for me so far (i am writing this comment from it).

I get the same result trying to download WUBI or trying to run a previously successful download on my Windows XP Pro SP3 system. I suspect a recent change somewhere since I had no trouble installing 9.04 on a laptop about a week ago.

Pyrun.exe takes such a death grip that it can't be canceled with Task Manager.

Ditto on all the forgoing.

Can confirm problematical "Cancel, try again, continue" dialog, "error processing message" seems vaguely familiar

Related links:
https://bugs.launchpad.net/ubuntu/+bug/366701
http://ubuntuforums.org/showthread.php?t=1134741

Could you attach a log at the point you get "Exception Processing Message"?

There seem to be different reasons for this (http://www.google.com/search?q=%22no+disk%22+%22exception+processing+message+c0000013%22) including a Worm (http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=218605&start=0), so please scan your machine.

This probably happens while Wubi scans all your drives for a CD/ISO, it would help if you could identify the drive that originates this message by looking at the wubi log in your user temp folder as soon as you see the error dialog.

IFirst attempt at reporducing error as follows:

1, Boot into XP and clean out %temp% directory
2. Insert disk
3. "No disk" error appears with details "Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6bf7c" and three choices: cancel, try again, continue
4. After clicking "continue" 8 times, the expected autorun splash screen appears, exited without installation.
5. No further error message.

Compressed version of log file attached.

Second attempt at reproducing error:

1. Clean out %temp% folder & insert disk
2, Error message appears as detailed above, response as above, installation option chosen when choice offered.
3. Installation proceeds happily until the stage where it modifies boot.ini, at which point the same error message appears
4. Clicked "Continue" 3 times, and a prompt to reboot appears
5. System rebooted, and boot into XP: Windows does not appear to offer the option to boot into Ubuntu
6 Log file saved from %temp% folder
7. Chose "uninstall" from Add/Remove programs on the Control program - no error messages noticed, and no sign of C:\Ubuntu folder.

Log file attached.

Question: would more information on computer specs be useful?

Comments on possible causes noted: scanning my affected machine now (last scan found nothing), will check the card reader idea shown in one of Google's results when scan finishes. Will report back if any news.

Apologies for "hijacking" this bug report

D'oh! A little while back I rechecked the attached logs: seems I was using rev 122 of Wubi 9.04 with the "release candidate" disk for 9.04......
No signs of the mentioned worm, removing quicktime (as suggested in one of the discussions returned by Google (wonderful friend!) didn't help, no sign of "dit.exe" mentioned by another thread......
Clearing the list of recent documents (suggested somewhere else) didn't help....
No sign of error dialog when using an 8.10 32-bit disk from Cannonical....
Downloading rev 129 & a fresh ISO for the 64-bit version (placed in same folder) didn't seem to help.

I need a break, & I'll bet those reading my ramblings do too....

Update: I just did a fresh install of XP on my affected machine (part of preparation for reoganization what's on my system), inserted a freshly burned CD of 9.04, 64-bit (downloaded from Cannonical)

Surprise surprise, no sign of the previous error messages.

I don't have time to pinpoint the exact reason for the problems on my machine at the moment (whether it's malware or conflict with something else installed on my system) but will post any additional clues as they come to mind. If doing a fresh install of XP (or whatever) is too drastic, then the links already provided by Agostino Russo might be able to provide a few ideas to check.

Good luck everyone!

Just took off the copy of Norton that was preinstalled, put on AVG free (downloaded on another machine to help avoid connecting to the internet and catching something), tried the same install disk again: a complaint that there was no disk in the drive. Interesting......no updates or other changes made other than enabling networking. Hmmmm, interesting.

Hello. If this could be helpful, also I have AVG Free installed on the machine.

_________________________________________________________________
È arrivato il nuovo Messenger! Provalo subito
http://clk.atdmt.com/GBL/go/140630370/direct/01/

Hi I'm on Vista and have the same problem. The virus program is scanning now, but have the feeling that it will not find any thing.

<Correction of my message above:>
Trying to run Wubi on an XP virtual machine and on a Win 7 Beta virtualbox machine, it seems to run fine, no error messages noticed (I didn't complete the installation because of lack of disk space in my virtual machine) and AVG free 8.0 is installed in both of them. So the problem, in my case, is not directly connected with AVG, or at least it seems not to be.

The above logs are fine, there is no error which is visible by the application. The issue probably manifest itself when trying to access a particular drive of yours. A lot of programs mentioned by other users are not really the cause, they simply scan the available drives similarly to what Wubi does, and trigger the error. You might first want to identify the drive, possibly by reducing the number of drives until you find the one responsible.

keep in mind that the wubi installer on my ubuntu 8.10 disk does NOT do this. The wubi installer on my 8.04 disk does NOT either. Only the wubi installer on my ubuntu 9.04 disk does this.

wubi 9.04 has been changed in some way. and it is only this initial part because once past this problem, the wubi installer works fine.

i do not know what logs i should post.

i have 2 optical drives. Drive E (a dvd burner) and drive F (a cd-rom). As long as BOTH drives contain an ubuntu ISO image (for example, if drive E already has the ubuntu 8.10 disk in it), then when i insert the 9.04 disk, i do NOT get the error. On the other hand, if i have no disk or a non-ubuntu disk in drive in drive E, then when i insert the 9.04 disk in drive F, i get the error.

it seems that wubi 9.04 has changed, in some fundamental way, the method by which it interacts with the drives and it causes windows xp to generate the "no disk" error when wubi interacts with an optical drive that doesn't contain a valid ubuntu ISO image (at least on my computer).

Again, wubi 8.10 does NOT produce these errors.

I think that it's probably NOT the AV blocking something, and possibly not SP3 either. I also noticed that the 8.10 disk didn't have the error while the 9.04 did. I, too, suspect that something has changed with the way 9.04 interacts with the disk, but haven't had a chance to do informal tests yet.

I had the same problem until 5 minutes ago.
I simply unplugged my card reader (any removable drives) and it's now installing perfectly

Give it a shot!

I can confirm that the card-reader might have some connection (direct or otherwise) with the difficulties: on my XP machine, I clicked on "safely remove hardware" for the built-in card reader, and the error message failed to appear. A restart (to reconnect the card reader) and the error returned. Looking to lspci for clues to manufactures, it wasn't immediately obvious which (internal) USB port was responsible for the card reader, but ATI was mentioned a few times.

Trying the same disk on another machine with a built-in card reader, but running Vista. there was no error. This machine has what lspci describes as a Texas Instruments 5-in-1 multimedia card reader (SD/MMC/MS/MS PRO/xD)

Removing a multi-card reader (Kingston) that assigns 4 drive numbers to my Vista solved the same problem for me.
Wubi now works.

I also think that the problem is connected with the card reader. I have an
economic USB built-in card reader (a generic one) and, running wubi after
clicking on safely remove hardware to disconnect card reader, it starts
without any error. Rebooting the computer (to reconnect the device): the "no
disk" error appears when I start wubi.

Hello guys!

I had that problem too.. And I had "... File "Z:\home\evan\bzr\wubi.trunk\build\wubi\files\lib\wubi\backends\common\backend.py", line 153, in fetch_basic_info ..." thingy in log. The problem is the unsupported characters. Just make any ş ç ö ğ or anything like that to english characters in every disk's label.

Please confirm whether this is due to non-ascii chars in the volume label. In which case please see bug #365648 which also contains a new version of wubi to try. By the way wubi 9.04 has been completely rewritten, so yes, things have changed.

i have the same results. if i "remove" my card reader (i.e., click on "safely remove hardware"), then my various usb / memory card drives are no longer viewable AND wubi 9.04 works fine.

all of my volume labels are ascii characters (i don't remember the exact letters and i will have to restart windows to view them again, but they were simple capital letters like G:, H:, I:, J:, K:)

from what i can see, wubi has been (is being) ported to python from some other language (largely due to the efforts of Agostino Russo, if i understand correctly). that's a tremendous project and appears to be done by a small number of people. so, we can definitely expect some hiccups.

i downloaded and tried the revised wubi...it does the same thing as the original wubi 9.04. keep in mind that none of my drive volumes are non-ascii.

I tried running wubi from Windows 7 RC and got the 'pyrun no disk' error. The only way to kill it was through Task Manager and End Process. :-(

I've also been experiencing the same issue when trying to install Ubuntu or Kubuntu 9.04. Doesn't matter if I download the distribution or download Wubi, I get this error message from pyrun.exe:

There is no disk in the drive. Please insert a disk into drive \Device\Harddisk2\DR2

and I can either cancel, try again, or continue.

I'm running Windows 7 RC at the moment.

If I click on Try Again twice or Continue, it'll still launch the setup menu for the distribution, but I never had this problem until after I installed Ubuntu (which I then removed due to video card problems when trying to launch Ubuntu) and downloaded Python 3.0 from the repository.

Using Win XP Professional:
I had the problem first without an error message (on a laptop) - Wubi made the drive lamp blink for a minute or so and then went back to sleep. On the other machine wubi exe on the 9.04 disc and the downloaded installer both produced the insistent error message from pyrun, which itself was hard to get rid of.
I tried closing down all peripherals but to no avail: finally I tried the "desperate click" method described above and eventually I got the installer window. My Kaspersky asked several times if I would allow pyrun to communicate with home (wherever that may be) and I did; after that installation proceeded normally.
 Obviously a bug, and one that is not going to encourage new users to use either Wubi or Ubuntu. Let's hope someone can fix it!

I also have a SD card reader. After doing "Safely Remove Hardware", not a single "No Disc" or Exception error. The solution seems to be to just have the basic A:, C:, and D: drives active.

I had the same issue with Win XP SP 3.

To get by the impasse, I just put a data CD with a valid directory structure into the drive. Wubi was able to read it, and to determine that it contains nothing of interest to Ubuntu. Once Wubi verified that (a) there was a disk in the drive, and (b) it was not the disk it wanted, it started to automatically download the files it needed to go ahead with the installation.

There are options for fixing this issue. I personally don't care whether it ignores my empty drive(s) or interrogates me about my intention to put an install disk into one or more of them. The current implementation, which reports the issue but gives no guidance to the user regarding the next step, is a "sub-optimal" solution.

BTW, you can get rid of pyrun.exe if you get rid of a companion process with an unusual name such as py###.tmp.exe. If you are of a cautious nature, you might want to reboot after having done this.

Just downloaded latest wubi and am running winxp pro sp3. I have the same problems. I have the latest ubuntu iso in the same folder as wubi with no other files. When I run I get "pyrun.exe - No Disk" for my DVD drive (drive E).

If you are very very patient however, clicking Cancel (50 times?) eventually wubi loads.

I am a newbie at all of this. This is my first post. But I was having the same problem on my Vista computer. It has both a Drive E (a DVD/CD-RW drive) and a Drive F (DVD RW drive). I’d insert the Ubuntu 9.04 installation disc in Drive E and I would get the error message Windows no disk exception processing message, ditto if I put it in Drive F: By clicking on Continue a couple of times the screen with the three installation options comes up. Ok, on my XP machine with just a CD drive there was no problem. The installation screen with the three options came right up.

 I found this post on the web: http://itknowledgeexchange.techtarget.com/itanswers/windows-no-disk-exception-processing-message-c0000013/ It states:
“The event indicates that the server received an exception of STATUS_NO_MEDIA_IN_DEVICE (c0000013). The error occurs when the server tries to access a shared resource (for example, a CD-ROM or floppy disk) which has no media (that is, no disk) in the drive. To prevent these errors, insert a disk in the drive.”

I put a blank CD in my F drive, the Ubuntu CD in the E drive and no problem. The screen with the three installation options came up and no error message.

WORKAROUND:

Downloaded wubi.exe from the website to a brand new Windows XP install. Had DAEMONTools installed. Mounting any image in the DAEMONTools drive caused the "Please insert disk in drive..." error message to go away. Unmounting image caused error message to return.

I posted an answer on 6/10/09 stating that when I put a blank CD in my 2nd DVD drive I did not get the exception error message. On trying to duplicate this, I again got an error message when putting the Ubuntu Live CD in disc drive 1, even though had put a disk in my 2nd drive. So I pulled the USB connection cable from my HP Photosmart D7160 printer which contains a card reader, essentially disconnecting my printer (with a card reader) from my computer; put the Ubuntu CD in my disc drive and no error message. So simply disconnecting my printer’s USB cable solved the problem for me. I tried this several times and no error message.

So in my case at least, it appears to be the card reader on my printer causing the problem. I must have had my printer disconnected (because I was trying everything I could think of) when I put the blank CD in my drive and erroneously thought I had solved the problem at that time by inserting the blank CD in my empty disc drive.

I am sorry for the confusion, but glad I have isolated the problem at least on my computer. I hope this might work for some of the others having this problem.

@BB,

i also made several wrong guesses about what was causing the issue...i also installed blank CDs in my drives (lol)...then finally someone else pointed out the issue with card readers.

@others,
it appears that the wubi script is scanning all "drives" on the PC (windows treats card reader slots as drives on my machine) and is not able to deal elegantly with the card reader slots -- if they are empty.

i have 4 card reader slots and i have to click "continue" 12 times total (8 times at the beginning of the installation and 4 times somerewhere in the middle)...so that is 3 times per card reader slot. (all my card reader slots have normal ascii character names like drive M:).

WORKAROUNDS...
one can successfully install ubuntu by merely clicking thru the error messages 12 or so times OR by "ejecting" the card-reader (eject by right-clicking the card-reader's icon in the systray, then clicking on "safely remove hardware", then clicking on "stop")

SOME THOUGHTS ABOUT THE BUG (PROGRAMMING-WISE)...
i am not knowledgeable of python (i dabble in C#), but i did scan the python code and it seems to have some code that tries to check the letters A-Z to see if any of those letters are valid drives. I think that could be the source of the first 4 errors. Then i think i saw some code that scans all drives for an available ubuntu image...so that's probably where the second set of 4 errors originates...i don't know about the last 4 times, though...i didn't look too far into the script. however, the wubi script itself may not be so much to blame as the underlying python libraries (i googled and googled and it seems hard to find documentation on python methods that allow access to system drive information on a windows machine)...but perhaps python provides a way to catch the error...kinda like a try-catch block in C#??? (again, i am not familiar with python...so i may be way off base). Could the errors somehow originate from the instantiation and/or use of the Drive class objects??? (just some thoughts)

unfortunately...
if one is not aware of the card reader issue, after clicking "continue" on the error message 3 or 4 times, one naturally feels the computer is in some kind of infinite loop. this could potentially cause first-time users to think the ubuntu installation program is defective (that's what i thought at first) or has some compatibility issue with their PC...when, in fact, they simply have empty card reader slots.

you know, i'm wondering if a small C# or JAVA program could somehow provide wubi with the drive information it needs. i'm not sure how that would work or even if it's possible.

but perhaps that violates ubuntu's open-source-ness...

but c++ (not microsoft's visual c++, tho) would probably be okay perhaps...anyway it would just be a tiny program whose only job would be to get system drive info and pass it to wubi on request because c++ may have better libraries for accessing such information...unless python has solutions of its own and i just couldn't find them in my google search.

William Bass:

With regard to the "infinite loop" phenomenon, I have no card readers on my machine, but an empty virtual CD drive provided by Daemon Tools. The loop sent me through the message dozens of times rather than three times. The same thing happens if my actual DVD drive is empty.

The workaround for a Daemon Tools virtual drive and a physical CD/DVD drive is to mount an image in the drive or put a disc in the drive, respectively. (The image and disc were not Ubuntu.)

I think this bug is due to mounting or running the cd/ iso image from multiple drivers.

1- un install wubi
2-check in windows by writing in RUU:
%temp%

and clear all files

restart and try again.

i did it this way and it works.

P.S:
make sure that there is no ISO images in the root directories of the partitions e.g.(C,D,E,F,...etc.)

This is just a rehash, but can also confirm problems with a memory card reader (this one also built in) preventing installation thru Wubi from pyrun.exe. This is an installation done thru Windows Vista Home Premium. A simple right click and "safely remove hardware" of the card reader drive, as mentioned before, allows installation.

Crazy.

i have the same problem too, but i found out a simple sulution to this error, just disable all ur USB connected drives including memory card readers etc. and try rynning the installation again this will work now,, cheers

Confirmed for me too. "Ejected" the card reader and all seems to be working again. Just go to "Safely Remove Hardware" and remove that card reader, then give it another try.

Using Vista x64 Ultimate with latest SP's and updates.

I have a Ubuntu 9.10 cd and SONY VAIO laptop with Windows 7 and having the same issue.

Same like #49, also win 7 and sony vaio. I just clicked about 30 times on continue and finally could get the installation screen. So just be patient an keep on clicking that continue button. Installation itself goes smooth once you get to the install screen.

Still an issue on the current version of Wubi, on a clean install of Windows 7.

It does appears to relate to the presence of card readers in the PC (I have 4) - and with the proliferation of these in both printers and PCs, it's likely to be affecting many, many first-time Ubuntu users.

I personally had to click 'Continue' a total of 44 times before the Wubi splash screen appears. Without having read this bug report, I'd probably have given up long before then :)

Adding an extract from the log file - if the developers need further information, let me know.

Popup which appears 44 times in slight variations before Wubi starts

Just checked with http://people.canonical.com/~evand/wubi/lucid/wubi-r178.exe and still got a similar message which disappeared after using "safely remove device". (My machine which seems to be affected is an older one (previously described), which I currently use as an Ubuntu-based server, so I'm not in a position to do much troubleshooting without taking down my web site & email server)

I've just done the Device Manager in Windows XP. I've disabled all empty unused USB Host Controllers and my Floppy Drive. I have ubuntu 9.10 - i386 desktop as a mounted ISO to the U:/ drive. It installs and works without errors.

Just a helpful hint

I was also getting the "Exception" error dialog and I had to click Cancel twice before Wubi appeared.

After reading some of the above comments, I went to Disk Management and unassigned the drive letter from my card reader. When I tried Wubi again there were no errors.

This really needs fixing as Wubi is meant to be an easy way for people to try Ubuntu and scary dialogs are likely to make a lot of people give up right there.

I am also getting the Exception Error dialog with a USB card reader plugged in.

Before clicking Continue each time, I waited a minute to leave a gap in the log timestamps to see if that would give any useful information.

I've attached the log and you can see that there are gaps before "DEBUG WindowsBackend: drive=Drive(G: removable 0.0 mb free )" and the same for drive K which are the empty card reader slots and again between "CommonBackend: Searching ISOs on USB devices" and "CommonBackend: Searching for local CDs".

My configuration is : C: & D: Hard Disk, E: cd with LiveCD mounted F: cdr empty. G: empty card read slot, I: & J: card reader slots with cards mounted, K: empty card reader slot ( Not sure what has happened to H: !)

I think that I have isolated where in the wubi code these dialogs pop up.
The first set are when GetDiskFreeSpaceExW is called at line 69 in backends/win32/drive.py. The second set are when glob.glob is called at line 650 in backends/common/backend.py

If it is a CD or USB card reader from which the media has been removed, you get the "Please insert disk message". If it is a card reader than has not had a card in since it was mounted, you get the Exception Error.

The solution might be to check filesystem in the __init__ method of Drive and set type = None if filesystem is blank.
I attach a patch that does that (patch at lines 43-50)

Sorry I'm new to this and don't know how to build a proper patch. I will make it a normal attachment

Hi Ray,

How interesting, just yesterday I also sent an idea for a patch via email to Agostino Russo. I didn't even notice the patch system here. Thanks for bringing that to my attention.

I looked at your patch, but just to let you know -- for me, at least -- get_filesystem() also causes the error for me GetVolumeInformationA method is the culprit in that one).

I have recommended that he use ctypes.windll.kernel32.SetErrorMode(1) at the beginning of the Drive class's __init__() to suppress the pop-up and ctypes.windll.kernel32.SetErrorMode(0) at the end to return windows back to the default state (regarding this pop-up, at least)...

I had wanted to do something like this when I first found the bug....I figured out the Drive class was probably the culprit but I didn't know anything about Python, so a week ago, I studied Python just enough to track this bug down and write a possible correction. Glad to see others are thinking along these lines, too.

Hi William,

It's interesting that you get the error on get_filesystem as well. That would explain why you get the message 3 times for each drive and I get it 2 times. Maybe itt is dependent on WIndows version? I'm XP Home SP3.

I am not familiar with the Windows API, but googling SetErrorMode suggests that this is the recommended way to avoid these messages.

I think you would still need to do something to avoid the message on the call to glob. You could wrap SetErrorMode calls round that, but the call in a common routine rather than windows, so I'm not sure of the implications of doing that.
Alternatively, you could set type=None if filesystem == "" in Drive

Ray,

I don't know windows api either. I found SetErrorMode after literally hours and hours of googling. Also, it needs to be clear...I have no experience in Python at all...except to try to figure out the Wubi code.

Also, you raise a good point, I seem to recall getting this error during installation, too. So, turning the message off just during Drive instantiation is probably not going to prevent all cases of this message.

In that case, I guess the script is calling methods on Drive objects somewhere else? So the SetErrorMode should be incorporated directly in the Drive methods causing the problem (get_space and get_filesystem).

However, then there is the glob.glob(path) issue that Ray Folwell found, and I see some calls to os.path.exists() in the code, too. I have confirmed taht os.path.exists() can raise the error IF it is called on an empty drive (I cannot tell if wubi code ever calls os.path.exists() on empty drives, though...but the potential seems to be there).

I recommend something else, in this case....

Somewhere in the Wubi code, there needs to be a function like so....

    def perform_disk_operation(disk_operation, *args):
        ctypes.windll.kernel32.SetErrorMode(1) # turn off no disk error
        retval = disk_operation(*args)
        ctypes.windll.kernel32.SetErrorMode(0) # restore no disk error to default mode
        return retval

Calls to the above function would actually pass in the desired function and arguments for that functions. For example...

    def get_space(self):
        drive_path = self.path
        freeuser = ctypes.c_int64()
        total = ctypes.c_int64()
        free = ctypes.c_int64()
        perform_disk_operation(ctypes.windll.kernel32.GetDiskFreeSpaceExW,
                unicode(drive_path),
                ctypes.byref(freeuser),
                ctypes.byref(total),
                ctypes.byref(free)) # FYI, returns 0 if unsuccessful...which could be
                                           # stored in a variable like so: is_successful = perform_disk_operation(....
        return total.value, freeuser.value

I don't know enough about Python to know if self needs to be an argument in the function or not {i.e., perform_disk_operation(self, disk_operation, *args): ???}, but I am envisioning a static method (does Python have those?) accessible from anywhere...perhaps in the Drive class....Drive.perform_disk_operation().

If Python doesn't support static methods, then a Disk_Manager or WubiUtilities object class could be created and instantiated and it could be used mainly for these sorts of things.

utilities = WubiUtilities
utilities.perform_disk_operation(xxx, yyy, zzz, ddd)

-----------------

Alternately (and I don't know how recommended this would be), SetErrorMode(1) could be called at the very beginning of the wubi execution and SetErrorMode(0) when wubi terminates. That would put the error mode in a non-default state while wubi is executing, and I don't know if that could cause potential problems in other windows processes or not (seems doubtful, though). It should be really easy to implement though and should prevent the pop-up the whole time (unless other windows processes are ...

I would normally prefer to turn something like this off for a short a time as possible, but it is worth noting that the Microsoft documentation at http://msdn.microsoft.com/en-us/library/ms680621%28VS.85%29.aspx says

"Best practice is that all applications call the process-wide SetErrorMode function with a parameter of SEM_FAILCRITICALERRORS at startup. This is to prevent error mode dialogs from hanging the application."
(SEM_FAILCRITICALERRORS is a constant value 0x0001)

That might be the simplest solution to implement.

Hey Ray,

Excellent catch...that "best practice" thing. I glanced at the article when I first discovered SetErrorMode() and totally missed that important info.

Not only that, but I get the idea that it is setting the error mode only for that application...in deed, maybe even only for the particular thread it's called in. So, I think it can be turned off at start up and then there is no reason to even set it back to default before termination.

I opened up two command prompts and ran get_space() on one without calling SetErrorMode() at all and another that called only SetErrorMode(1) ... and never SetErrorMode(0). The command prompt window that didn't call it got the pop-up every time I ran it. The other did not....no matter that I ran the one that turned off the pop-up first...so it should have zero impact on other apps or processes.

That makes the answer clear to me...call ctypes.windll.kernel32.SetErrorMode(1) at start up and forget about it...unless there are other threads that could raise the error (I think I did see code that indicated wubi had more than one thread), then they all would need to call it as well before they were started.

I have sent Agostino an email calling attention to posts 63 and 64 in this thread as they seem the most useful.

William,
The same Microsoft documentation (see post 63) says that SetErrorMode works at the process (not thread) level so it should be OK even if Wubi runs multi-threaded.

Thanks a lot, that is very useful information, I will patch wubi and upload a new version in the coming days!

I did a test that seems to confirm Ray's point in #66 -- that is, that it if the application calls SetErrorMode(1) the pop-up will be off for the whole application including for any threads started by the application.

Shoudnt this bug be set for wubi and not ubuntu in general?

1 thing i can say is that you can end that annoying box, press ctrl alt + delete and then find pyrun.exe in the list, click it once, press end process, then once thats done, exit task manager, and press cancel on the message box and its gone. It works for me ^_^

I haven't read through the whole shebang since this page is *huuuuuuuuuuuge*, but I can confirm that if my Nexus One phone is connected to the computer (on Windows 7) and I try to run Wubi, I get the error. I can get past it by clicking "Continue" in a whole bunch of error boxes, or I can simply unplug the Nexus One and start over.

Disable all your USB drives, your unused optical drives (with no ubuntu CD), and any virtual drive or cardreader. After that wubi should work

I can confirm that AVG (the 2011 free edition) is detecting "pyrun.exe" as malware. The application will not run correctly with the AV activated. I cannot find confirmation anyware that the pyrun binary in the wubi distribution is "clean", so I won't risk disabling the AV for installing.

Thoughts? can somebody confirm if it's safe to whitelist pyrun from the wubi distro?

I'm not 100% sure, but I think pyrun.exe is some sort of python language interpreter. Wubi is written in Python. I could be wrong, though. You're the first person in this thread who has had AV problems with pyrun.exe. The rest of us were trying to get pyrun.exe to stop giving us a "no disk in drive" error every time it encountered a card reader slot.

I have WinXP with 3 optical units and had to click Cancel in that dialog 22 times.
Then 2 more times during installation.

Wubi rev197.

I change the drive letter of my CD-ROM and mount new virtual CD-ROM with the same drive letter to pass the problem in Windows XP.
More details on http://errerrors.blogspot.com/2011/03/solve-wubi-installers-pyrunexe-says-no.html

Just to say a big thank you!

As you mentioned, it seems like an endless loop of error messages, all very much the same

I'm not sure how many times I had to click to work my way through (easy 20 plus!) but got there in the end!

once again, many thanks for the info!

I encountered this bug in ubuntu 11.04. Booting the iso gives black and wubi is not happy to see me. :(

@Tijs Maas: No disrespect intended, but I see no obvious connection between the problem you have described and the general tenor of this particular discussion of problems with Wubi. Have you search http://ubuntuforums.org for similar problems?

@Tijs Maas: The problem you're experienving **could** be the result of a "bad burn" or a corrupt download.

Is this bug on progress? Someone assigned? The bug is reproducible on Ubuntu 11.04 and there are workaround and patches attached. With an unsuccesfull experience on the Ubuntu installer could produce a big loss of begginers users. Could someone take care of this? Thanks.

Running Windows XP Home Edition, SP3. Encountered the dreaded pyrun.exe error. After using the "click through" workaround, I was prompted as expected to reboot into Ubuntu and let the installation complete. At 28% the installation froze, and after a reboot to finish the installation, I was given an error that the NTFS file system was corrupted, and to run a chkdsk /f through Windows.

Went back into Windows, did as was requested...uninstalled Ubuntu properly to attempt a clean install. When running the WUBI installer AFTER running the chkdsk /f; I received no further pyrun.exe errors. I checked different versions, tried loading off a CD, USB, and a mounted .ISO from a virtual drive. No further pyrun.exe errors at all. This may be something to look into. Thanks!

I am running Windows 7 Ultimate on a 64bit AMD PC and got the same error when starting the Wubi.exe as Administrator, so I thought what else can I do and first tried it with running the file as normal user. Result: The same problem.

Then I did a right click on the file and found another option by trying the Troubleshoot Compatibility Problems option. This option proposed me to run Wubi.exe in the Windows XP (SP2) mode and yes, the complete problem did not arise!

But in the end, the installation did not work (could not start Ubuntu)

I've experienced this "No disk in drive" problem with the latest Ubuntu 11.10 Windows installer on my Sony VGN-NW11S laptop. Based on the details of this bug, I assume the problem is related to the SDCard and Sony Memory Stick "drives". I won't be working around the problem; I'll wait until if / when this bug is closed.

Same "No disk in drive" issue for by Dell Studio XPS desktop. Windows 7 64-bit. Again, it has a built in memory stick / SDCARD reader.

By clicking through the error message several time the installer started
and now I'm a happy camper as Ubuntu 11.04 is installed and running. I
updated to 11.10 and found that it is not user friendly for me. I
un-installed the 11.10 version and re-installed 11.04 which is clear, clean
and works very nice.

On Sun, Dec 4, 2011 at 12:55 AM, David Boden <email address hidden>wrote:

> Same "No disk in drive" issue for by Dell Studio XPS desktop. Windows 7
> 64-bit. Again, it has a built in memory stick / SDCARD reader.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/365881
>
> Title:
> wubi installer's pyrun.exe says "no disk"
>
> Status in Wubi, Windows Ubuntu Installer:
> New
> Status in Ubuntu:
> Confirmed
>
> Bug description:
> The issue i'm having is with the initial installation.
>
> I run Windows XP Home Edition on an HP Pavilion a656x with an added
> video card and an added stick of memory. It has two optical drives,
> drive E (a DVD/CD drive) and drive F (a CD drive).
>
> Here is what happens...
>
> 1. I boot into Windows XP
> 2. I insert the Ubuntu 9.04 CD into drive E
> 3. I get a pop-up message window (from pyrun.exe) telling me that there
> is no disk in drive F
> 4. My options are Cancel, Try Again, and Continue and the "X" to close
> the little window
> 5. no matter what i click, the error message just pops back up.
>
> if I put the CD in the Drive F, then everything happens exactly the
> same except that in step 3, the message informs me there is no disk in
> drive E.
>
> So, whichever of my two drives i insert the CD into, the installer
> complains that i don't have a disk in the OTHER drive.
>
> In Ubuntu 8.10 (which I no longer have installed on my system), after
> I inserted the CD, I would simply get a pop-up that presented 3
> installation options (and I want to choose the 2nd one: install inside
> windows)....in Ubuntu 9.04, if i keep clicking the various buttons
> randomly like 50 times (Cancel, Try Again, Continue, and the little
> close "X")...I will eventually get the installation options.
>
> ---------------------------------
>
> UPDATE:
> I am the author of this bug report, which I reported in april 2009. It is
> now January 2010, and I have decided to sum up the issue and the work
> around so people won't read the first 5 or 6 posts and misunderstand the
> issue. I am still getting email notifications; so, apparently this is
> still a problem.
>
> APPARENT CAUSE:
> This issue appears to be due to the wubi installer being ported to python
> from its original language; therefore, if i remember correctly, this
> problem will only be seen on wubi 9.04 and later. Wubi (and possibly python
> itself) has problems dealing elegantly with empty data storage devices in
> certain instances. Wubi scans all drives on your system a certain number of
> times during the installation process. Every time it scans through the
> drives and encounters one it does not know how to deal with, it produces
> this error. If you click through it, wubi moves on to the next drive.
>
> WHAT TO EXPECT:
> It feels like an infinite loo...

Unfortunately, if I click "Continue" the 30 or so times required to get the installation to progress, it ultimately ends up with an error stating that it can't write to drive E:. Drive E isn't mounted, so I assume it's trying to write to the SDCARD drive which it thinks is there. I've attached the install log, hope it helps a little.

That sounds like bug 862003 which means the install is likely successful.

On Sun, Dec 4, 2011 at 4:22 AM, David Boden <email address hidden>wrote:

> Unfortunately, if I click "Continue" the 30 or so times required to get
> the installation to progress, it ultimately ends up with an error
> stating that it can't write to drive E:. Drive E isn't mounted, so I
> assume it's trying to write to the SDCARD drive which it thinks is
> there. I've attached the install log, hope it helps a little.
>
>

Amazingly this problem still exists two years later.
Is Canonical getting "Microsoftized"?

After looking at the resolution (from a user not anyone from Canonical) I realized it was WUBI looking at one of my USB fobs as a hard drive. The only 2 USB fobs I had plugged in were for my web camera and my Logitech wireless mouse.

I removed the webcamera connection and lo and behold, WUBI works... go figure... since when have web cameras ever been considered as mass storage drives? Granted I've only got 10 years using Linux so I guess one can learn something new every day.

bcbc, you're right; the install was indeed successful. It booted all the way through. Thanks for the direction.

The only remaining failure is that it doesn't recognise the Wifi card (sorry, this post is now starting to go off topic). I'll try to find time over the Xmas period to run a cable from my router to my PC in order to get the drivers downloaded :)