Conflict Between NIS and Macrium Reflect

This post is just an FYI in case anyone else runs into this problem.  I couldn't find another topic regarding this issue, so my apologies if I missed one and this is a duplication.

 

I use Macrium Reflect Standard on my WinXP Pro SP3 x86 desktop PC along with NIS 20.3.0.36.  This morning I was trying to create a Rescue CD for Macrium and the PC crashed.  I contacted Macrium Support and they pointed me to this KB article on their website: http://kb.macrium.com/KnowledgebaseArticle50175.aspx

 

As the article explains, I had to temporarily disable NIS Auto-Protect in order to create the Macrium Rescue CD.  Easy workaround.

Gary, Thanks for posting this.

 

Just to confirm that the conflict is between the 'ImageX' utility supplied with the MS Windows Automated Installation Kit and NIS 2013  (version: 20.3.0.36) . The BSOD will occur even if Macrium Reflect is not installed and ImageX is invoked from the command line on Windows XP.

 

Best Regards

 

Macrium

This post is just an FYI in case anyone else runs into this problem.  I couldn't find another topic regarding this issue, so my apologies if I missed one and this is a duplication.

 

I use Macrium Reflect Standard on my WinXP Pro SP3 x86 desktop PC along with NIS 20.3.0.36.  This morning I was trying to create a Rescue CD for Macrium and the PC crashed.  I contacted Macrium Support and they pointed me to this KB article on their website: http://kb.macrium.com/KnowledgebaseArticle50175.aspx

 

As the article explains, I had to temporarily disable NIS Auto-Protect in order to create the Macrium Rescue CD.  Easy workaround.

You're welcome.  I just didn't want anyone else spending unnecessary futz time on a known problem with an easy workaround. :smileywink:

Too late! :-)

 

I have been trying for a few weeks (off and on) to find out why my system reboots while trying to create this disk in Reflect Free. I checked the Macrium Reflect log and saw it had to do with mounting/unmounting the Win Image. I thought that it could be NIS2013 as it could be protecting the image. So I disabled autoprotect and it worked. In fact, I came here to post about this.

 

Is this going to be fixed?

I noticed that within the last day or two, NIS updated itself to ver 20.3.1.22 but I haven't had a chance to try and burn another Macrium Rescue CD so I don't know if the problem is fixed or not.

I was going to try as I wanted to add drivers, but who knows what has happened.