Recent content by Froggie

That's the basic issue with WInRE-based creations. MicroSloth has generated a few major issues along the way after updating the System's WinRE.wim file (one mentioned above) during updates/upgrades. At that point users scramble around trying to find out how to get around a flakey WinRE.wim...

Not being a SECURE BOOT user, I would never go through the machinations being required by these certification changes and BOOT level changes that users in this Forum have been suffering through. Since I've never come across a single user in these groups that has ever been affected in any way by...

The challenge is all yours :rolleyes:

I do not believe most of their options set up as DEFAULTs, only a few,. They are set up once with the task definition and remain as long as the task is in use... a minor issue at best.

@Flipmode - since your LIVE Failure to BOOT occurred in Late July, that's probabaly when the errored disk block went south. I would restore the next earlier image, with RDR turned off, to see if you have the same stability as you do now. If so great... I think:cautious: You still need to find...

It's perpetual for the life of the product, not just throughout the current version. For $18 per System for the entire life of the product... sounds like a good investment supporting the developers. The application is excellent, and other than the MIG feature (which I don't use) and CBT (which...

I made an inquiry of any LTSC users on Macrium's Forum a while back... crickets, so I have no idea whether they've ever been dealt with or even how many LTSC users there may be. It might just be a "ghost" community... :unsure:

Well... it's quiet 'cause it will never be done. If you need it, you'll have to move on.

@Flipmode, I consider this a very unfair rant (and I'm not even a Macrium fanboi). A user of a product needs to know how a product functions... that's called due diligence. A quick lesson... RDR does not mess with disk blocks that have not been changed by the operating System. Why... because...

Many other users have taken this approach to circumvent the problem and it works well... not sure about quicker :unsure:

In my case, both HASLEO and MACRIUM (primary and backup imaging methods) are supported using the single VENTOY functioning multi-BOOT environment.

Well... I've looked just outside of your imaging application box a bit (the app being responsible for both the emergency media generation and producing a format necessary for image storage as well) and came up with VENTOY, a multi-BOOT solution. It allows for the multi-BOOTing of almost every...

That's what AI (the buildout) will do to you... current SSDs (in any form) are off the table these days.

As @KevTech has mentioned, their Forum is rife with the Devs and reported issues have been solved, in many cases, in record time. There is also direct access to the Dev team through "Support AT EasyUEFI DOT com"... I've used it many times.

When it's a requirement, Macrium always mentions it in their RELEASE NOTES.