virtualbox.org

I am currently using VB?3.0.2 on Windows 7 RC, and everytime I try taking a snapshot, I get this:

"Could not save the settings file "C:\[snipped]\.VirtualBox\VirtualBox.xml" (VERR_ACCESS_DENIED)"

Here's what it reads in the "Details" box:

Result Code:
VBOX_E_FILE_ERROR (0x80BB0004)
Component:
VirtualBox
Interface:
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}

Any help would be welcomed.

Windows 7 beta & Release Candidate is a development OS and not supported by the community (us volunteers/mods) directly. Because it's still in development, changes can be made at the last moment, which could cause to render all support done in previous versions useless and possibly cause serious issues.

That being said I hope you can understand that VBox and Microsoft are trying to get this all worked out and as soon as the release is final it should work properly. We do appreciate you input and it will help to improve the product.

Hello,

I'm a french user of VB 3.0.2 r49928 and I obtain the same error on Windows Vista Home Premium :

"Could not save the settings file "C:\Users\(Personal)\.VirtualBox\VirtualBox.xml" (VERR_ACCESS_DENIED)"

Details :
VBOX_E_FILE_ERROR (0x80BB0004)
Composant :
VirtualBox
Interface :
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
Fonction Appelée :
ISystemProperties {9ca0f712-83f3-4631-b143-b75ef6568332}

It appears when I try to change anything in prefs, I want to mount an ISO file or save the system's state (similary to snapshot's function ?)

Windows 7 RC isn't the source of the problem ! VB 3.0.2 doesn't work properly.

Thanks for your help

Just wanted to confirm that this is not a Windows 7 issue.

I get the exact same thing on Vista Home Premium host, Ubuntu guest. I had VirtualBox 2.2 installed, the Ubuntu guest and VirtualBox settings interface worked great. Upgraded to VirtualBox 3.0.2, now I cannot start my old Ubuntu snapshot (just get a blank screen for a while), and editing the settings results in a VERR_ACCESS_DENIED error as described above.

Any suggestions would be greatly appreciated.

Thanks,
Marco

Okay, maybe I should have tried this before posting: after restarting my host OS, it all works fine. I'm not sure what changed, but maybe this should be recommended after a VirtualBox upgrade.

Cheers