Failed to open the disk image file

[Vadim R.]

Hi there,

I've got an issue. I've created VMDK RAW file with command line:

VBoxManage internalcommands createrawvmdk -filename E:\VHD\W10CU.vmdk -rawdisk
.\PhysicalDrive2 -partitions 2

and it was created with no issues, however I\m not able to use it with error below:

Failed to open the disk image file E:\VHD\W10CU.vmdk.

Permission problem accessing the file for the medium 'E:\VHD\W10CU.vmdk' (VERR_ACCESS_DENIED).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004) Component: MediumWrap Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda} Callee: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945} Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

[Socratis]

An error message is not a bug.

It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (​https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Also, searching in the forums helps tremendously...

[Vadim R.]

"error message is not a bug" - no, it is.

error message - it's event. Based on even, we've got incident. Couple of incidents about the same issue - it is a problem. Now we got a problem, because the same issue was detected in 5.0 version. Now it comes again. So, please, don't send me to the middle of nowhere and suggest something. To prove my words, feel free to search across you KB, I guess you're should be able to do this.

If you thought that issue is on my side - please, explain, why?

[Perry G]

Actually this has been covered a lot on the forums. Your access denied is a permission issue and not a bug as such. RAW access requires read/write access to the partition and your error message is telling you that you do not have it. Also be warned that RAW access is an advanced feature requiring you to know what you are doing. Misuse can lead to corruption.

[Vadim R.]

Ok. Let's close this request. Issue was in UAC of Windows OS. I guess, you knew this. Sad that I spent a lot of my time to investigate simple things, which should be in hands of level 1 vendor support.

[Perry G]

Excuse me but how would anyone besides you know the issue was UAC on the host? All I could tell is there was a permission issue which I pointed out and that can be a lot of different things. Not be be too blunt but even if you had paid for commercial support this would still have had to be resolved by you.

[Frank Mehnert]

I agree with Perry. Nothing to add.