Permit to offer a brief observation:  The sin, in my view, is that Reflect should NEVER DELETE a source of data for it's operation.  If the option Do Not Copy Driver has been set, then it should just not copy the driver from an INF file, NOT delete the INF file, and NEVER delete the Windows INF folder or any other folder containing an unwanted driver unless said folder was created by Reflect and/or is under the control/purview of Reflect.

I can't tell precisely what the forthcoming fix will do when confronted with the same confusing instructions from a user.  @JoeA Could you confirm that the forthcoming fix complies with those thoughts so we all can breathe easier. 


L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7638+ on Windows 11 Home 23H2 22631.2715+  

Hi All, 

We've conducted a more in-depth investigation into this issue and determined that it originally entered the software during an early version of v8.0. This bug wasn't introduced with v8.1.7638. The nature of the option selections required to trigger this problem has made it elude our detection until now, and there are no reports of other users encountering it.

While we concur that the severity of this issue is significant, it's worth noting that @Keith Weisshar only recently uncovered it. This suggests that the likelihood of another user encountering the same problem before the patch is applied is quite low.

We're actively working on a solution for this issue, currently in the testing phase within our internal environment. Once we're confident that this issue won't reoccur, we'll promptly release the fix to ensure a seamless experience for our users.

The nature of the option selections required to trigger this problem is selecting Use Host Drivers and then selecting Do Not Copy Host Drivers when the status is Driver already present in Drivers folder and applying the changes to the rescue media builder.

Kind Regards

Joe A

Macrium Support Team

See our reviews on

When will the next update be released as selecting "Use host driver" and then selecting "Do not copy drivers" with "Driver already present in Drivers folder" status and then applying the changes will result in unrecoverable catastrophic failure of the Windows operating system that will require a clean reinstallation of the operating system?

+x

 

Keith Weisshar - 18 September 2023 11:29 AM

When will the next update be released as selecting "Use host driver" and then selecting "Do not copy drivers" with "Driver already present in Drivers folder" status and then applying the changes will result in unrecoverable catastrophic failure of the Windows operating system that will require a clean reinstallation of the operating system?

"Promptly", apparently:

"...we'll promptly release the fix to ensure a seamless experience for our users."

Is there a way to prevent malicious exploiting of this destructive bug if I share the computer with other users or use remote access software?

+x

 

Keith Weisshar - 28 September 2023 7:51 AM

Is there a way to prevent malicious exploiting of this destructive bug if I share the computer with other users or use remote access software?

Macrium said "we'll promptly release the fix to ensure a seamless experience for our users."

Did they release an update yet?

The last update was released on September 4th.  So, it hasn't been addressed yet.

+x

 

Dan Danz - 9 September 2023 7:23 PM

Permit to offer a brief observation:  The sin, in my view, is that Reflect should NEVER DELETE a source of data for it's operation.  If the option Do Not Copy Driver has been set, then it should just not copy the driver from an INF file, NOT delete the INF file, and NEVER delete the Windows INF folder or any other folder containing an unwanted driver unless said folder was created by Reflect and/or is under the control/purview of Reflect.

I have no idea what goes on in the minds of the developers, but I suspect all of them would agree with you.  It's almost certain they did not intend to delete any system folders from Windows.  I would bet that they intended either to delete a copy of the folder that they had made or to perform some action other than "delete".   It's a bug, not an intentional action.  Testing should catch errors like this, but this bug requires an unusual combination of options not covered in the tests.  (I bet there's a new testing scheme that covers all unusual combinations of options in Rescue Media Builder.)

Keith,

Are you sharing your computer with hackers or people who want to do harm to you?  If not, why are they even going to access Reflect?  You can password protect Reflect if needed (via 3rd party software).  That would be a good idea anyway even when this bug IS fixed if you think these other people are going to try to mess up your computer.  And if that is their intention there are easier ways to do it then to use Reflect (they can easily reformat your HDD).

+x

 

dbminter - 28 September 2023 1:49 PM

The last update was released on September 4th.  So, it hasn't been addressed yet.

So it seems.