Hi everyone,
Can you please help on this issue why I cannot open the WinXP Virtual Box on my laptop. This VB is ran OK on other laptops of my colleagues.
I have attached the error screenshots + the log file.
Thanks,
Nhat
Cannot open VB for WinXP
Cannot open VB for WinXP
- Attachments
-
VBoxHardening.log- log file
- (13.34 KiB) Downloaded 3 times
-
- after press OK on the 1st screenshot, this message box appear
- vb error 2.JPG (34.03 KiB) Viewed 699 times
-
- error when opening VB
- VB error.JPG (30.22 KiB) Viewed 699 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Cannot open VB for WinXP
Please read the following FAQ: Diagnosing VirtualBox Hardening Issues.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Cannot open VB for WinXP
That's a strange error message... it implies that it couldn't open an executable image (not disk image) because something else already had the file open. I don't think I've seen that before. Normally an OS is done with the DLL/EXE file once the contents have been load. Maybe antivirus, but I'd also try rebooting the host in case some glitch has left a system DLL file-locked.
...
Ah. User is using Portable-VirtualBox. That's a fork, and we don't support forks here. I must ask the OP to either demonstrate the problem using genuine VirtualBox, or fork off to the Portable-VirtualBox site to get support there.
...
Ah. User is using Portable-VirtualBox. That's a fork, and we don't support forks here. I must ask the OP to either demonstrate the problem using genuine VirtualBox, or fork off to the Portable-VirtualBox site to get support there.