Macrium error when trying to explore an image

Has anyone else encountered this error list below...
I've only recently started seeing it after updating to the latest build.
I'm unable to mount any of my images because of this image
and I'm hoping someone can shed some light on the issue.
I'm able to backup and restore but not mount and explore any of the images.

Thanks in advance.

'failed to load the volume access driver with result 0x80070003
the system cannot find the specified path'

Seems another reason to avoid the latest update.

@Lucas North

0x80070003

I've come across that once before, although not with reference to Macrium.

According to the search I did on that expression then, it's an Update failure (ie. not Macrium, of course).

It's a while back, but an inplace (Update) Repair did resolve the issue for me. I haven't seen it since then. Perhaps easier to just rollback to KB5063030 ?

@ian50

Thanks for the feedback Ian, as of yet I've had no positive result.
I will try installing an earlier version of Macrium just to see how it plays out.
I'll keep you in the loop if I have any success.

Is this while booted into Macrium recovery or within Windows.

Here is one suggestion


When you see this error in Macrium Reflect while trying to mount a backup image (e.g. .mrimg), it usually means the Macrium virtual volume driver (used to mount images as virtual drives) is either missing, not loaded, or pointing to a broken path.

---

Cause​

Macrium's image mounting driver (psmounterex.sys) can't be loaded — likely because it's missing, corrupt, or the registry points to a path that doesn't exist.

Click to expand...

Error code 0x80070003 = The system cannot find the path specified — often the path to the driver .sys file.

​

Step 1: Reinstall the Macrium Image Mounting Driver​

1. Open Macrium Reflect
2. Go to Other Tasks > Fix VSS Problems
3. Then also go to: Other Tasks > Re-Deploy Restore > Reinstall Reflect Drivers

@kelper

Many thanks for the detailed feedback, much appreciated.
This recovery is from within Windows...

The driver in question (psvolacc.sys) is in the system32 folder as required and I've followed the other tasks as instructed.
Still no success at this point.
I'm now at a point whereby I will test with an earlier build of Macrium and see how that works out.
Failing that I will revert back to version 8.0 and run a test with that.
I'm running out of options to be honest, failing everything else I will consider other software as an alternative.

Thanks again for the help.

___________________________________________________________________________________
Date: 29/06/2025 1:16:07 PM
Type: Error
Source: Application Error

Faulting application name: MacriumService.exe, version: 10.0.8576.0, time stamp: 0x68276a54
Faulting module name: MacriumService.exe, version: 10.0.8576.0, time stamp: 0x68276a54
Exception code: 0xc0000409
Fault offset: 0x0000000000904eab
Faulting process id: 0x1528
Faulting application start time: 0x1DBE8A376F5087F
Faulting application path: C:\Program Files\Macrium\Common\MacriumService.exe
Faulting module path: C:\Program Files\Macrium\Common\MacriumService.exe
Report Id: 2c7dffac-4efe-4922-a782-a5a2f6946773
Faulting package full name:
Faulting package-relative application ID:
___________________________________________________________________________________

The assigning of the drive letters is where the problem stems from it would seem...
Tried every suggestion I've been able to find, even resorted to going back to earlier
Macrium Images dating back several weeks but still the problem persists.

I can create images and restore them, I just can't explore them via explorer.
I tested other Backup software but wasn't impressed to be honest.
I'm just hoping this doesn't mean a format C:

I have Macrium Reflect 8.0 (free version). I needed to restore just a single file yesterday and the image would not mount. I checked Event Viewer and found that the kernel-mode driver psmounterex.sys was being blocked by WDAC. It seems that the latest Windows driver block list that I installed manually blocks this version of the driver. Boo! I can remove the supplemental policy, but eventually Microsoft will push it out to everyone. Not sure if this helps anyone else.