Skip to main content

Locking a physical disk on windows....

In this, I've tried to lock a physical disk using a small Windows C++ program. The steps to follow to achieve this are:


1. Get the Physical Drive and volume mapping. Say, the computer is attached with three physical drives, and we're interested to lock the Physical Drive 1 ("\\\\.\\PhysicalDrive1"). Then we need to figure out how many volumes are there on that physical disk.

2. Then Lock that volume one by one using control code FSCTL_LOCK_VOLUME.

3. Do the stuff we'd like to perform on the disk and then unlock each volume using control code  FSCTL_UNLOCK_VOLUME.

4. Close disk and volume handle(s).

Few things to remember here. As per Microsoft documentation,

a. The NTFS file system treats a locked volume as a dismounted volume.
b. Lock volume call will fail with Access Code 5 (Access Denied) if the volume is in use. If we're not sure who's using the volume, just unmount it once.
c. The FSCTL_DISMOUNT_VOLUME control code functions similarly but does not check for open files before dismounting.
d. The operating system tries to mount an unmounted disk as soon as an attempt is made to access it. So, a call to GetLogicalDrives API will trigger the operating system to mount the disk.

Note: Since this deals with disk locks, please use it wisely.

Here is the code snippet, I tried to lock the drive here which has only one volume (J:).

void LockDisk()
{
    HANDLE    hDisk_Device = NULL;
    HANDLE    hDisk_Drive = NULL;
    DWORD    returnedLength;

    // Open the drive(s) associated with this disk and lock.
    hDisk_Drive = CreateFile(
            L"\\\\.\\J:",                                                     // device interface name
            GENERIC_READ | GENERIC_WRITE,            // dwDesiredAccess
            FILE_SHARE_READ | FILE_SHARE_WRITE, // dwShareMode
            NULL,                                                          // lpSecurityAttributes
            OPEN_EXISTING,                                        // dwCreationDistribution
            0,                                                                // dwFlagsAndAttributes
            NULL                                                         // hTemplateFile
            );

    if(hDisk_Drive != INVALID_HANDLE_VALUE)
    {
        BOOL status;
        status = DeviceIoControl( hDisk_Drive, FSCTL_LOCK_VOLUME, NULL, 0, NULL, 0, &returnedLength, NULL );

        if ( !status )
        {
            wprintf(L"IOCTL failed with error code: %d.\n\n", GetLastError() );
        }
        else
        {
            wprintf(L"IOCTL success, volume locked\n\n");
           
            status = DeviceIoControl( hDisk_Drive, FSCTL_UNLOCK_VOLUME, NULL, 0, NULL, 0, &returnedLength, NULL );
            if( !status)
                wprintf(L"IOCTL failed with error code: %d.\n\n", GetLastError() );

            CloseHandle(hDisk_Drive);
        }
    }
}

We can test this piece of code by using debug breakpoint to see if it really works. I've used Windows 7 (x64).

On successful lock, if we try to access the drive from Windows Explorer, we'll get the following error:



Comments

Popular posts from this blog

Reversing char array without splitting the array to tokens

 I was reading about strdup, a C++ function and suddenly an idea came to my mind if this can be leveraged to aid in reversing a character array without splitting the array into words and reconstructing it again by placing spaces and removing trailing spaces. Again, I wanted an array to be passed as a function argument and an array size to be passed implicitly with the array to the function. Assumed, a well-formed char array has been passed into the function. No malformed array checking is done inside the function. So, the function signature and definition are like below: Below is the call from the client code to reverse the array without splitting tokens and reconstructing it. Finally, copy the reversed array to the destination.  For GNU C++, we should use strdup instead _strdup . On run, we get the following output: Demo code

A simple approach to generate Fibonacci series via multi-threading

T his is a very simple approach taken to generate the Fibonacci series through multithreading. Here instead of a function, used a function object. The code is very simple and self-explanatory.  #include <iostream> #include <mutex> #include <thread> class Fib { public:     Fib() : _num0(1), _num1(1) {}     unsigned long operator()(); private:     unsigned long _num0, _num1;     std::mutex mu; }; unsigned long Fib::operator()() {     mu.lock(); // critical section, exclusive access to the below code by locking the mutex     unsigned long  temp = _num0;     _num0 = _num1;     _num1 = temp + _num0;     mu.unlock();     return temp; } int main() {     Fib f;          int i = 0;     unsigned long res = 0, res2= 0, res3 = 0;     std::cout << "Fibonacci series: ";     while (i <= 15) {         std::thread t1([&] { res = f(); }); // Capturing result to respective variable via lambda         std::thread t2([&] { res2 = f(); });         std::thread t3(

Close a Window Application from another application.

 This is just a demo application code to show how the WM_CLOSE message can be sent to the target process which has a titled window to close the application. To achieve this, either we can use SendMessage or PostMessage APIs to send required Windows messages to the target application. Though both the APIs are dispatching WM_XXXXX message to target application two APIs has some differences, these are as below: 1. SendMessage () call is a blocking call but PostMessage is a non-blocking call(Asynchronous) 2. SendMessage() APIs return type is LRESULT (LONG_PTR) but PostMessage() APIs return type is BOOL(typedef int). In Short, SendMessage () APIs return type depends on what message has been sent to the Windowed target process. For the other one, it's always a non-zero value, which indicates the message has been successfully placed on the target process message queue. Now let's see how can I close a target windowed application "Solitaire & Casual Games" from my custom-