Macrium problem

lvgandhi said:

I am using Macrium for long time.
For the first time, it started hanging while creating image. I chose to cancel it. Still imaging did not stop. Then did end task macrium. Now C drive space reduced by 3.6 GB. Most probably macrium used storage.
Where macrium will be storing of temp imaging?
Why it was hanging?

Look on the C:\ drive for a folder (probably hidden) called: $WinREAgent. Inside is a folder called Scratch, which is probably the temp folder Macrium uses.

As for why it's hanging... I don't know. I would uninstall it, then install the latest version.

lvgandhi said:

Thanks for the response.
There was no such folder. However the occupied spaced was cleaned on its own. I do not know how. Further I tried again. Everything went well. Imaging was ok.

I think that folder was created in my case, with an older version of MR.
When making a backup, that folder would be used. After the backup finished, it would be emptied.

I won't know till I make my next backup, but I don't think that folder will be created or used since I updated to the MR 7.3.xxxx version.

Anyway, I'm glad you got it working.

If this helps:

The $WinREAgent folder is created during a Windows Update or upgrade and contains temporary files that allow you to recover Windows 10 if there are problems during the upgrade or update.Apr 27, 2020

also: What is this $WinREAgent folder I see on C Drive?

f14tomcat said:

If this helps:

The $WinREAgent folder is created during a Windows Update or upgrade and contains temporary files that allow you to recover Windows 10 if there are problems during the upgrade or update.Apr 27, 2020

also: What is this $WinREAgent folder I see on C Drive?

That makes sense. I had thought it was related to MR because on the older version I had used the RE option when creating the rescue media. LOL

Glad I could help.

Bree said:

Interesting. I have one on all my machines, but haven't bothered deleting them as they're all empty folders.

I had assumed it was the 20H2 feature update that had created them. But on examining the creation dates it seems that was the case for only one of them. For the others the creation date coincides with a Patch Tuesday and the time was just past 6:00pm local time (which is when I routinely check for new CUs). But oddly it was a different month's CU for each machine that left it there on each machine. My earliest dates back to July's CU.

You would have though that the next CU should have cleared it up, but that's not the case.

Don't want to go too far OT (been an issue lately..........), but MS has a long laundry list of dust bunnies that seldom if ever get to the trash bin.