Reflect backup or windows

man00 · May 25, 2026

Started getting this message when trying to mount image made using Reflect 8

Mooly · May 25, 2026

Please have a read at this long thread:
Overwhelmed - Macrium Reflect

And the Macrium thread:
psmounterex.sys load error

dalchina · May 25, 2026

Also worth using Google or searching the forum first ...

Backup and Restore with MR is unaffected. Only mounting images is, and the thread does offer a fix of sorts if I understood it correctly.

However- I also recently found that the buttons were off screen when using the boot disk to restore a partition (MR 8.1). So I'm considering using Hasleo Backup.

man00 · May 25, 2026

I just did a backup and MR could not see it to restore...I try to disable all the security stuff see if that works. Could be MR and MS are bed partners ?

dalchina · May 25, 2026

And thank you for your reply. No idea why you're having a problem. You haven't said where you've saved your image file to, and provided no screenshot.. no info, no comment.

man00 · May 25, 2026

I disable Memory Integrity seem to fix it .....for now

zbook · May 25, 2026

One or more of these links may be useful:

April 14, 2026—KB5083769 (OS Builds 26200.8246 and 26100.8246) - Microsoft Support

support.microsoft.com

April 2026 Windows security updates introduce protections to known vulnerable kernel drivers - Microsoft Support

support.microsoft.com

Microsoft recommended driver block rules

View a list of recommended block rules to block vulnerable non-Microsoft drivers discovered by Microsoft and the security research community.

learn.microsoft.com

Microsoft:

Introduction:

After installing Windows updates released on or after April 14, 2026, certain third-party backup applications that
rely on the kernel driver psmounterex.sys might experience failures when attempting to mount or manage disk images.

These Windows updates include routine security hardening to help protect devices by blocking third-party drivers with
known vulnerabilities.

For more information on the psmounterex.sys driver vulnerability, see CVE-2023-43896.
Learn about these protections at Microsoft vulnerable driver blocklist.

Mooly · May 25, 2026

man00 said:
I just did a backup and MR could not see it to restore...I try to disable all the security stuff see if that works. Could be MR and MS are bed partners ?

That is what happened to me a couple of days ago.
Overwhelmed - Macrium Reflect

I finally put it down to the fact I had played around with partitions and only by using bootable media could I get MR to see the image.

Anybody... Is that normal?

I was surprised because I thought Macrium loaded into RAM and so it should have worked by starting the process under Windows as I normally do.

I had disabled the driver blocklist and turned off core memory protection and then without giving it any thought created a USB recovery drive from Macrium. It said a newer version of WinRE was available and did I want to download and install that. I declined simply because I thought the existing WinRE would be fine and it was. The bootable media worked perfectly.

Have we something going on here? or was my failure simply that MR would not see the image files because of my playing around with partitions and then running MR from within Windows as I have done many many times before.

garlin · May 25, 2026

Mooly said:
I had disabled the driver blocklist and turned off core memory protection and then without giving it any thought created a USB recovery drive from Macrium. It said a newer version of WinRE was available and did I want to download and install that. I declined simply because I thought the existing WinRE would be fine and it was. The bootable media worked perfectly.

Have we something going on here? or was my failure simply that MR would not see the image files because of my playing around with partitions and then running MR from within Windows as I have done many many times before.

Older versions of WinRE don't have the Apr 2026 update to the blocked drivers list. So the Macrium driver is still allowed.

Mooly · May 25, 2026

Interesting.

What I was actually doing was resizing and moving the WinRE partition and I originally made a mess of it. So I had the Windows WinRE disabled and moved to the sys32 area and no working recovery partition on the drive. Those were the conditions I created the bootable MR media under. The WinRE that was in sys32 was bang up to date as it is the latest Canary 29595 build. Does Macrium have its own WinREas well? If so then me declining the offer of a later version might have been a fortunate choice.

garlin · May 25, 2026

Macrium takes the WinRE from your Windows. When required, WinRE may be updated as part of the Monthly Update.

One of the problems is you don't have visibility on which WinRE was used to build your recovery USB. A drive created months ago could be different from one created today. Until recently, it didn't matter what WinRE version was used since all that Macrium cared about was having a bootable environment which had your drivers (imported from the live system).

Now you may have to pay attention because of the blocked drivers list.

Mooly · May 25, 2026

I created the bootable drive on the day.... which was 48 hours ago. WinRE had already been moved to sys32 and there was no recovery partition (I had deleted it)

garlin · May 25, 2026

WinRe.wim can reside in the C:\Windows\System32\Recovery folder ("reagentc /disable"), or on the RE partition ("reagentc /enable").

Mooly · May 25, 2026

I had used the reagentc /disable while I tried to recreate a new larger recovery partition. I have done all that now (all good) but having made such a mess of things first time round I wanted to restore back to an image I made a couple of hours before I started all that.

I would like to know whether Macrium run from within Windows should have been able to do the restore. It kept throwing errors of 'invalid file path' if I moved the image to a second HDD and of just not seeing the image if I left it on the second internal SSD where it was originally created. I've done countless restores in the past, all from within Windows and never an issue.

man00 · May 25, 2026

On desktop reflect tried to update and popped this error

antspants · May 25, 2026

man00 said:
Started getting this message when trying to mount image made using Reflect 8
View attachment 172452

Apparently, Microsoft updated its Windows Vulnerable Driver Blocklist in April 2026 to block this Macrium driver from loading.

More info if you search Google, like the following. (if it helps you)

Affected Software: Older versions of Macrium Reflect (such as v8) and some other backup tools.
What breaks: You may be unable to mount or browse backup images as virtual drives, and you may see errors related to Microsoft's Volume Shadow Copy Service (VSS) timing out. Note that creating backups usually still works; it is the mounting process that fails.
What doesn't break: Your underlying backup data is still safe and can be used to perform a full disaster recovery if needed.

April 2026 Windows security updates introduce protections to known vulnerable kernel drivers - Microsoft Support

support.microsoft.com

antspants · May 25, 2026

man00 said:
On desktop reflect tried to update and popped this error
View attachment 172493

Did you try a reinstall? (Sorry I just woke and can't focus yet to read anything but your problem)

man00 · May 25, 2026

antspants said:
Did you try a reinstall? (Sorry I just woke and can't focus yet to read anything but your problem)

No not yet, wondering if I did would Macrium kill my license in not supported 8.1

antspants · May 25, 2026

man00 said:
No not yet, wondering if I did would Macrium kill my license in not supported 8.1

Might need @Bree or someone else to answer that.

Josey Wales · May 25, 2026

man00 said:
No not yet, wondering if I did would Macrium kill my license in not supported 8.1

My wife is using MR 8.1 and I did an in place upgrade repair and she did not lose it.

Reflect backup or windows

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Like a rolling drone.

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Like a rolling drone.

My Computers

Endeavor to Persevere

My Computers

Similar threads