Opened 15 years ago
Closed 14 years ago
#6807 closed defect (fixed)
"Overlapped I/O operation is in progress." windows error while using vbox
| Reported by: | Roel | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 3.2.0 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Today I got the following errors in Windows 7 Home Premium x64 while running VBox 3.2.0 with a Ubuntu 9.04 Guest:
======== [Window Title] C:\
[Content] C:\ Overlapped I/O operation is in progress.
[OK] ========
I was unable to access the C: drive. Stopping virtual box altogether (close guest and close VBox GUI) seemed to resolve the issue.
I got the same issue a bit later on (VBox was running again). I tried to kill virtualbox.exe process (the Ubuntu guest exe), but this did not clear the error. Re-started the guest and immediately shut it down, then closed VBox GUI. Result = C: drive usable again.
Seems pretty serious.
Attachments (3)
Change History (8)
comment:1 by , 15 years ago
by , 15 years ago
| Attachment: | VBox.log.1.txt added |
|---|
This log is likely from when I open/closed the session quickly (second time issue happened)
by , 15 years ago
| Attachment: | VBox.log.2.txt added |
|---|
This log is likely from when the issue happened the second time (the one were I killed virtualbox.exe)
by , 15 years ago
| Attachment: | VBox.log.3.txt added |
|---|
This log is likely from when the issue happened the first time (I shut down vbox normally)
comment:2 by , 15 years ago
Hmmm. I just got this error even when not running Virtual Box.
Also getting this time:
====== [Window Title] Location is not available
[Content] ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\ refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location.
[OK] ======
comment:4 by , 14 years ago
Please could you update to VBox 3.2.6 and check if that fixes your issue by any chance? There were a lot of fixes since 3.2.0.
Interestingly, this seemed to work fine for some time before this started happening. However, I installed RealVNC today. Wonder if that has anything to do with it at all (was using pc remotely using RealVNC).