Skip to content
This repository has been archived by the owner on Jun 10, 2021. It is now read-only.

"Not able to get handle on volume" error + errorlevel checking not working #3

Open
HarikalarKutusu opened this issue Dec 4, 2016 · 1 comment

Comments

@HarikalarKutusu
Copy link

HarikalarKutusu commented Dec 4, 2016

I run this snipplet in an elevated batch file:

CD Tools\CommandLineDiskImager
CommandLineDiskImager.exe %SETUPDRV%%SETUPDIR%img\raspbian-jessie-lite.img %SDCARDDRV%
rem Above structure yields to the following as expected, all files/drives in place
rem CommandLineDiskImager.exe E:\setup\img\raspbian-jessie-lite.img S:
IF ERRORLEVEL 0 GOTO IMAGEOK
GOTO FAIL
CD ....
:IMAGEOK
...
:FAIL

The output is :

writing file E:\setup\img\raspbian-jessie-lite.img to device S:
error - not able to get handle on volume
error - invalid handle value for volume

Same operation works with Win32DiskImager GUI. I also can format the SDCard with Win10 and SDFormatter 4. So I assume the SDCard is functioning. Also tested with two more SDCards (Sandisk Ultra 16GB), same result.

Furthermore the errorlevel check does not work - in this case at least.

I hope I'm not making a stupid mistake...

Cheers

@HarikalarKutusu
Copy link
Author

OK, the first issue was not with CommandLineDiskImager...

I was using COMODO Internet Security Premium and AutoSandbox was on. Although I clicked "ignore" it was not working, may be a bug on their side...

After disabling AutoSandbox, it worked.

Maybe it would be a good idea to put a small note about this as sandboxing is very common nowadays + the software uses direct drive access...

Maybe that condition could be checked inside and/or errorlevel could be set?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant