From Newsgroup: alt.comp.os.windows-11

On 04/18/2026 10:32 AM, Paul wrote:

On Sat, 4/18/2026 10:26 AM, Paul wrote:

On Sat, 4/18/2026 6:53 AM, Dennis wrote:

FYI.

Yesterday I had the need to mount a Macrium image in order to restore a
single file.

When I double-clicked the .mrimg in File Explorer I got a screen saying
psmounterex.sys could not be loaded.

https://imgur.com/a/lN4ZdKk

I found the following link on the web...


https://forums.malwarebytes.com/topic/335035-macrium-reflect-8-driver-blocked-psmounterexsys-cause-and-workaround/

Apparently a certificate has been revoked, possibly by the patch Tuesday >>> MS update earlier in the week.

The MBAM registry workaround and reboot mentioned at the above MBAM link >>> did not work for me.

So I typed Core Isolation in the search bar and turned off Memory
Integrity and Microsoft Vulnerable Driver Blocklist and rebooted.

That fixed the problem, but left me a little less secure for the effort. >>>
This driver problem only affected image mounting. Image backups and I
assume restores still worked.

I don't know if newer versions of Macrium are affected.

Note: I bought a lifetime license for Macrium v8 about the time that
they switched to an annual subscription model. This is why I'm still
using v8.

I have a copy of Macrium 7.3 here, which failed the same way after
Patch Tuesday this month.

psmounterex.sys

That is most likely to be the "Microsoft Vulnerable Driver Blocklist".

One entry I found in Google, stated that a patch with a release number
after the end of the free 8.0 , could fix this, but I'm a suspicious
person and your result seems to fall in line with my expectations.
We'll just have to wait and see if anyone with a later Macrium, is
experiencing no problems at all with their OS-level backups or mounts.

By the way, this issue was identified in 2023. Now, three years later...

Paul

Hi Paul,
Had to refresh my TBird Win11 group, and noticed I intended to reply
with another piece of the pie for this 'Macrium' topic.

The broken Macrium issue in most cases is reasonably, easily resolved.

Prior to making the image(Win10/11) disable Personalization\Start
- Show recently opened items in Jump Lists on Start or the taskbar and
in File Explorer Quick Access.

Prior to mounting the image or performing any other image related functions(recreate image, restore, inspect, etc.) ensure the same
feature is off.

The key, is to prevent the image name from being in the recent list.
Once done with Macrium(and until next use), the 'Show recently' option
can be re-enabled.

If necessary, one can, if available on the device, disable Core
Isolation or the Vulnerable Driver BlockList
--
...w¡ñ§±¤ñ
--- Synchronet 3.21d-Linux NewsLink 1.2