Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot lock volume - access is denied #7

Open
SoraKenji opened this issue Aug 2, 2023 · 3 comments
Open

Cannot lock volume - access is denied #7

SoraKenji opened this issue Aug 2, 2023 · 3 comments

Comments

@SoraKenji
Copy link

More than an issue, this is a question. While using the software on a Windows Surface Pro 3 we got the message:

Cannot lock volume '': Access id denied. (0x5)

We got this error using:
dskwipe.exe -s 0 -e 2048 -y -x reboot -f -g \Device\Harddisk0\Partition0
and also the same using the following:
dskwipe.exe -s 0 -e 2048 -y -x reboot -f -g \\.\PhysicalDrive0

The command dskwipe.exe -l shows the following:


Device Name                         Size Type      Partition Type
------------------------------ --------- --------- --------------------
\\.\PhysicalDrive0                256 GB Fixed
\Device\Harddisk0\Partition0      256 GB Fixed
@rasa
Copy link
Owner

rasa commented Aug 3, 2023

Are you sure you are administrator and are not trying to wipe the disk windows is installed on?

@SoraKenji
Copy link
Author

SoraKenji commented Aug 3, 2023

Hey Rasa! Thank you for replying!

Yeah, I am the administrator, but I'm trying to wipe the disk Windows is installed on... We have being doing that in other devices as a way to "eliminate" the disk if someone stole them and it did work in those devices, but not in this kind of device (Surface Pro 3) for some reason D: but maybe I'm doing something wrong haha.

Edit: Sorry I'm on my phone and touched "close issue" by mistake! I re-opened tho haha.

@SoraKenji SoraKenji reopened this Aug 3, 2023
@rasa
Copy link
Owner

rasa commented Aug 3, 2023

I doubt Windows would let you wipe the boot disk, unless you booted into a PE environment first, or wrote some kind of special kernel driver that allowed you to write to the primary disk's boot sectors, sorry.

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

No branches or pull requests

2 participants