v 4.24???
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
v 4.24???
I just upgraded to the new version release v4.24 and I got an error opening VB/Windows. I tried restarting. I downgraded back to v4.18 and now I get the following error now too. I was working fine before I did anything.
Error:
Failed to open a session for the virtual machine vbox vm.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Thoughts?
Using Yosemite current OS.
Error:
Failed to open a session for the virtual machine vbox vm.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Thoughts?
Using Yosemite current OS.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
I just tried reinstalling 4.24. Here is the error message:
Failed to open a session for the virtual machine vbox vm.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Failed to open a session for the virtual machine vbox vm.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: v 4.24???
I very much doubt that the guest OS is XP-64bit. Choose the correct template in the VM settings.
The error appears to be that the drive image file is locked, perhaps because the VM is already running.
FYI, please try to be accurate with error reporting. E.g. there is no VirtualBox v4.24, nor was there a v4.18. Happily it was easy enough this time to decode the accurate information, but that isn't always the case.
The error appears to be that the drive image file is locked, perhaps because the VM is already running.
FYI, please try to be accurate with error reporting. E.g. there is no VirtualBox v4.24, nor was there a v4.18. Happily it was easy enough this time to decode the accurate information, but that isn't always the case.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
Sorry about the nomenclature error, misread it.
I noticed the 64 bit setting also after I posted. (I don't know how it changed as I believe it was set to the 32 bit before the recent update). I fixed that setting but it still isn't starting.
I noticed the 64 bit setting also after I posted. (I don't know how it changed as I believe it was set to the 32 bit before the recent update). I fixed that setting but it still isn't starting.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
Any further thoughts on this? I tried using the VB uninstall tool from the installation window but it doesn't work. Can I uninstall and reinstall without affecting my data attachment?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: v 4.24???
Yes, you can uninstall and reinstall VirtualBox without affecting your data - so it is also unlikely to affect the error, though I suppose there is no harm in trying.
I gave my opinion regarding your problem in the second paragraph of my previous reply. Lacking any new evidence I must stick with that.
I gave my opinion regarding your problem in the second paragraph of my previous reply. Lacking any new evidence I must stick with that.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
This is the current error message.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
FYI, I did change the settings back to windows XP 32 bit. I also tried uninstalling and reinstalling as well as rolling back to previous version and reinstalling current version. As far as the image file being locked, no idea how to go about fixing that without instruction.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: v 4.24???
Files are locked by the host OS because the file is in use, or because you don't have permission to access it. The simplest test is to reboot the host, which hopefully ensures that no running app is using it. If it's a permissions repair problem then a Mac user will have to advise you on that.drs@dcneuro.net wrote:As far as the image file being locked, no idea how to go about fixing that without instruction.
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: v 4.24???
The first thing to try is run "Repair Disk Permissions" from Disk Utility in the Utilities folder.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Posts: 96
- Joined: 29. Oct 2013, 18:10
Re: v 4.24???
I had actually done both of those things two days ago when I first posted the problem. (Disc permission repair and reboot). Oddly, when I came in to my office today and booted the system up, windows started up after a short pause asking me if I want to run in safe mode or start windows as usual. Really odd that it didn't work when I restarted the other day. Perhaps it needed to be shut down rather than simply restarted? Is there a difference?