I want to use the new DirectStorage feature in Windows 11. I checked if my drive was compatible and it gives the below error for my C: drive. I looked up the driver and it is from macrium. Although the file hasn't been updated since 2020, so I'm not sure if it's actually in use anymore. Can I safely delete this and still use Macrium?

Hi @jtcgiants56,

The MRVMDK device driver is a component of Macrium viBoot and is required to use Macrium Reflect Image Files as source disks in VirtualBox.

If you do not need this functionality, then we would recommend removing the VirtualBoot component from the Reflect installation rather than deleting the file.

Alternatively, you can run the following command from an elevated Command Prompt / Powershell console, to flag the MKVMDK driver as BypassIO compatible.

REG ADD HKLM\System\CurrentControlSet\Services\mrvmdk\Parameters /v StorageSupportedFeatures /t REG_DWORD /d 1

Please be aware that once you have flagged MRVMDK as BypassIO compatible, you will likely find that Windows finds other device drivers that are not compatible, including some from Microsoft.

NOTE: You can modify the above command to use for any device driver, however; please be aware that doing so could result in file-system corruption and/or data loss and we recommend you avoid doing so without first consulting with the device driver manufacturer.

The command is safe for use with our MRVMDK device driver, however we are still investigating the effects of DirectStorage on other components and we will update the installer to automatically add support for our device drivers where possible.

Kind Regards

Jamie

Macrium Development

See our reviews on

Hi,
I have the same issue with Mrvdp "Macrium Virtual Disk Provider", however the above solution did not work. I ran "REG ADD HKLM\System\CurrentControlSet\Services\Mrvdp\Parameters /v StorageSupportedFeatures /t REG_DWORD /d 1" in admin ps console and rebooted and still see the DirectStorage error. Moreover the driver remains active even after uninstalling Macrium Reflect and rebooting. 

How would I go about removing the driver? I was thinking just installing Reflect once a day run the backup and uninstall, but the driver didn't get deleted with uninstall.

Is there a different workaround to make it work? Can I install Reflect without the Mrvdp driver? 

+x

 

C.G.B. Spender - 20 August 2022 6:02 AM

Hi,
I have the same issue with Mrvdp "Macrium Virtual Disk Provider", however the above solution did not work. I ran "REG ADD HKLM\System\CurrentControlSet\Services\Mrvdp\Parameters /v StorageSupportedFeatures /t REG_DWORD /d 1" in admin ps console and rebooted and still see the DirectStorage error. Moreover the driver remains active even after uninstalling Macrium Reflect and rebooting. 

How would I go about removing the driver? I was thinking just installing Reflect once a day run the backup and uninstall, but the driver didn't get deleted with uninstall.

Is there a different workaround to make it work? Can I install Reflect without the Mrvdp driver? 

Hi @C.G.B. Spender

MRVDP.SYS is a kernel mode driver that that is installed as part of the viBoot component of Reflect. If you do not require the functionality provided by viBoot, you can exclude it from the installation. This should prevent MRVDP from being installed.

If all viBoot virtual machines have been removed, the service key for MRVDP (in HKLM\CurrentControlSet) should be automatically deleted when uninstalling Reflect. This should stop Windows from loading the driver on the next restart.

We have a policy of not deleting driver files (i.e. MRVDP.SYS) from the disk because if Windows switches to another control set that references the driver (e.g. the last known good control set), the missing driver file could render Windows unable to boot.

You can force removal of the MRVDP driver from the current control set by executing the following from an elevated Powershell console, however; this should not be required if the uninstall procedure completes successfully.



If you are unable to resolve the issue using the information above, please can you open a support ticket at helpme.macrium.com (referencing this post), so that we can arrange to collect some more information.

Kind Regards

Jamie

Macrium Development

See our reviews on

I have tried to uninstall via Settings / Apps and rebooting again, and the driver was still present. The proposed command and reboot led to same result. In the end I just deleted "HKLM\System\CurrentControlSet\Services\Mrvdp" manually and after reboot and reinstall with the optional component disabled it finally complains about different driver not related to Macrium. I guess it was some kind of leftover from older installation (I vaguely recall using viboot some time in the past).