Unable to browse Macrium backup

To unmount, right click the Drive and under Macrium Reflex there is the Unmount Macrium Image.
Works for me in 1803.

Jim

Aomei & Macrium were not conflicting because I did not install Aomei until after I discovered the problem with Macrium.

I have no other ISO mounting software installed. I did a few years ago, but uninstalled it when I found out that Windows had it itself.

bbinnard said:

Problem found!
Turning off Windows Defender Real Time Protection allows the backup file to be mounted.
...
Edit: more weirdness - now that I mounted the backup file there is no way to eject/close/unmount it.

dalchina said:

Progress.. I've asked someone else with 1903 to have a look....

I've just got back home and seen dalchina's PM asking me to have a look. I have x64 1903 Home build 18362.145 with Defender real time protection (and controlled folder access) turned on. Macrium is 7.2.4063. No other AV or imaging software is installed. I have no problems mounting or un-mounting Macrium .mrimg files.

To mount, I right-click and select Explore image...




To unmount, right-click on the mounted drive in 'This PC'....

Bree - that's exactly what I do, but after clicking OK in the selection box I get nothing.

One thought - I've installed and since de-installed the Sandbox feature. I reckon most other people (including you) have not done this. So could that perhaps/maybe be the thing that is confusing Macrium?

I've been using Macrium for years and up to now it's been solid as a rock. Which is why my sense is that it's something in the latest Windows update or 2 that is causing the problem. But of course that's just a guess.

bbinnard said:

Bree - that's exactly what I do, but after clicking OK in the selection box I get nothing.
One thought - I've installed and since de-installed the Sandbox feature. I reckon most other people (including you) have not done this...

Well, that's difficult (but not impossible) in Home

You may be onto something there. Do you have a large C:\ProgramData\Microsoft\Windows\Containers folder? It's used by, amongst other things, Windows Defender Application Guard (and left in use after you uninstall it). See this thread....

What is this large folder?

Steve C said:

The conclusion is that once you have enabled Application Guard you are left with several GB of useless files in C:\ProgramData\Microsoft\Windows\Containers even after disabling Application Guard. There appears to be no safe way of deleting the files.
I'll file a feedback report and you never know Microsoft may get around to fixing their sloppy engineering.

In my post #43 I show how to successfully delete 'Containers'...

Steve C said:

Thanks - I'll try that method in a few days if nobody reports any problems

...and, of particular relevance to you, the bit I have made bold here...

Bree said:

I don't think there's a large sample base to hear from, just you and me were mad enough to try Application Guard by the looks of it
There may be more come the release of 1903, seems the new Sandbox feature uses the same Containers function.

Bree said:

Well, that's difficult (but not impossible) in Home

Yes, but Shawn's instructions work fine when followed closely.

Bree said:

Do you have a large C:\ProgramData\Microsoft\Windows\Containers folder?

Mine is 869 MB. Is that large? Most of the space is taken up by the Baseimages directory. The Sandbox directory has only a single 4MB file named sandbox.vhdx.

I've never heard of the Application Guard thingy - does it exist in Home? Do I need it/want it?

bbinnard said:

...Most of the space is taken up by the Baseimages directory. The Sandbox directory has only a single 4MB file named sandbox.vhdx.
I've never heard of the Application Guard thingy - does it exist in Home? Do I need it/want it?

No, I think Application Guard is only available in Pro. However, both it and Sandbox create and use Baseimges in the Containers folder - and both seem to leave them behind (and their registry entries) after uninstalling. Removing them as I described in the other thread may be the solution for your missing Macrium mount/unmount options.

I hardly need to tell you to make a Macrium image before you try