Custom Query (16363 matches)
Results (2428 - 2430 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11269 | obsolete | Windows 7 explorer.exe goes wild after using Virtualbox 4.2.4 | ||
| Description |
This feature has been in many recent versions, not just 4.2.4 I have Windows 7 ultimate 64-bit as a host (in quite a high spec machine;Intel i7-980X, 250GB SSD,2TB HD etc Windows experience index 7.5) and I was now using Ubuntu linux 12.04 LTS as a guest. But this probably is not tightly Virtualbox-version related, nor exact guest related as I have used Debian squeeze quests as well with Virtualbox-versions from around 1 year back. The description is that when I have used the guest and go back to hosts side (guest still running) and start typing something in some edit box of another application (does not matter what app), those keys trigger special Windows explorer.exe shortcuts i.e. windows switched/minimized etc which renders the user interface not usable. The minimum recovery to fix things is to restart explorer.exe (kill it from the process list, then ctrl-alt-del + start a start "explorer.exe".). After that you can use the system again. And before doing this I have also shut down the Virtualbox - I have not tested what happens if Virtualbox is left running while doing the restart. One exact case: after switching from Virtualbox/Ubuntu guest to host side to start WinSCP for example and while entering the user name the explorer "goes wild" -> restart of explorer.exe is required. Other possibly but not likely related: I have Logitech's wireless rechargeable Performance MX mouse and Logitech's illuminated (wired) keyboard + Logitech Setpoint software installed. |
|||
| #11270 | obsolete | WinXP Pro Fails to launch | ||
| Description |
Using Virtual Box on MAC OS 10.8.2. When trying to launch WinXP Pro I'm getting the follow error:Failed to open a session for the virtual machine WinXPro. Failed to Load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE) I deleted the image and completed a full uninstall of VB. Reinstalled VB and set up the WinXPro image again and get this same error when attempting to install the OS. Log file attached. |
|||
| #11271 | obsolete | VB crash on resuming from VB display put to sleep by guest | ||
| Description |
Win 7 host, Xubuntu 12.04 guest This crash is only 50% reproducible (based on 6 trials with the same settings). What I did:
After step 3, I would either experience a 'VB has crashed' error from host (related to MSVCR100.dll), or guest would resume with no problems. Attached are Windows logs with the VB crashes and VB logs. Possibly relevant settings:
Additional notes: I also played with the guest setting to switch the display off (instead of sleeping). Three trials yielded no crashes (although in one trial the guest display was screwed up; after redrawing it was fine). I also briefly tested the host, having it sleep and turn off the display before the guest was set to do so. Only one trial each, no problem either time. I think these crashes only started after I updated VB to 4.2.4. I have been using these settings for a very long time (a year?) and never had any problems until now. My workaround is to set the guest to never sleeping or switching off the display. |
|||

