Macrium Reflect

Very helpful - thanks stapp. This will come in handy when I decided to upgrade.

 

Does anyone know how to delete old WinPE files?

I am using WinPE 10, but every time I launch Reflect it prompts me to update my WinPE 3.0 files.

I don't want to check the 'ignore' box in case it no longer prompts me with WinPE 10 updates.

 

If your "Reflect Defaults/Advanced/Macrium Reflect PE files" option is set to "C", you will find your PE3 files located in the ROOT of your C:/ drive in "boot\Macrium" in a folder called "WAIK Files"... you may delete the entire folder.

If the "Reflect Defaults" option above is set to any other drive, the "boot" folder mentioned above will be on that drive.

 

Thank you!

v7 working great here (had to enable CBT which defaulted to disabled).

 

Thank you - not sure how my googling missed that!

 

Ah - I think my initial upgrade install was the last update - hopefully it was a one-off then.

 

me too. been using v6 with the new CBT .dll for a few months & now have the latest version including bug fixes those who stay with v6 will never get. i updated earlier today.

 

I decided to upgrade to v.7 and so far all went well.
One question - can ReflectUI.exe autorun be disabled or will it affect scheduled tasks (I have CBT disabled)?

 

Well, this may resolve my issue of it always asking. Macrium support told me to enable the don't ask box so it does not ask any more. Now I would like to remove the old PE5 files and try again but how do I get to uncheck the don't ask box as it does not come up any more?

 

Decided to give V. 7 a shot. I was unable to upgrade form my paid V. 6. I received this message online; This license purchase is still pending.

 

xcuse me,what are u talking about?
something about breach of the licensing rules?
hopefully they don't find out whom u are and what is ur license, cause they can invalidate it.. aka blacklist..

 

OK...almost a disaster! I did a FULL image with v7.0.2023. No problem. I then did a few things with another program I had and did not like it so I did a full restore of this Image with the rescue disk I had just made. The restored image would not boot and kept saying it was going to try to recover. I restored an image created with v7.0.2001 with my 2023 rescue disk and all was OK! So I did a restore of the "bad" image again and it was back to not booting into windows. I then told the Rescue Disk to fix boot issues. It did and when Windows 10 tried to come up it said there was an issue as Windows\system32\drivers\mrcbt.sys was missing!

I explored the images using the rescue disk and sure enough...when I created the image with 2001 that file was there. In today's image using 2023 it was missing so I added it to the restored drive and all booted OK.

SO...why did 2023 remove MRCBT.SYS and what do I need to do so it will not happen again?

 

You might wanna bring that up with Macrium on their Forums. First of all, the two problems you mentioned above are totally separate from each other. The non-BOOTing had nothing to do with the absentee driver... that issue was fixed by Reflect's FixBOOT (was your RESTORE an RDR or a FULL <remember, the DEFAULT PE mode is RDR>). The missing driver is a whole nuther issue. The installer is supposed to place that driver in your mentioned folder then install it into the System as a running driver during its installation. Build 2023 was not a PATCH, it was a full install upgrade. There may be something wrong with Build 2023 as far as that process is concerned.

 

Well, I will see about RDR as I did not change anything and it sure does look like build 2023 removed the driver! The fixboot was good as windows told me that MRCBT.SYS was missing. THAT is why my restored system would not boot. When I put the file back from a 2001 image all was OK. Anyway, how do I configure the Restore mode to full? Actually, in this case it would NOT help as the image did not have that driver there any more. I believe that the 2023 version removed it as a new image, after I "fixed it" has that driver back.

I did post on the Macrium Forum.

 

Your post above said after the 2023 image was restored your System wouldn't BOOT at all (problem #1). Reflect's FixBOOT fixed that and now Windows came up but told you the driver was missing during the process of BOOTing (Problem #2)... those are two separate issues the way you've described them above.

During a PE restore (same as a LIVE restore), when you get to the summary page prior to the restore, use the "Advanced Options" link at the bottom to allow you to deSelect RDR if you want to do a real FULL restore.

 

NO...Windows did NOT come up when I did the fix boot. It started to come up and then gave me a screen saying that it could not boot because a driver was missing. It then told me what driver was missing. I then used the rescue disk (from 2023) again and explored the image that 2023 created, and I tried to restore. Sure enough, the driver WAS missing. As I said, the 2023 build must have removed it. I explored the image created a few days ago with 2001 and that driver was there, so I put it into my non-booting drive that had the image created with 2023 and it worked. Bottom line was that rdr was OK, but the 2023 install removed mrcbt and left me with a non booting image. I would have never know that if I did not try to restore the image created after the 2023 build as all looked good!

 

I understand what you are saying... but you said after the restoiration your System would not even BOOT and it didn't even try to until you used Reflect's FixBOOT... that's a totally different problem than a Windows starting process telling you about a missing driver. When it tells you about the missing driver it's in the middle of its BOOTing process, long after it wouldn't BOOT following the restoration and its need for FixBoot.

You might wanna try a real FULL restore of that bad image and see if it does the same thing...

 

But I can explore the image and it does not have that driver. The one before it did and had a Feb 28, 2017 date. What I had said was that when I first did the restore and tried to boot before fixboot, it would say that it was trying to rebuild the system, but couldn't. After Fixboot when I tried to boot at least Windows told me what was wrong. It still did not boot, however.One other thing I could try is to go back to the image that worked OK and then let MR update again from build 2001 to 2023 and see if the driver is again removed. I still say a full restore may not help as that driver, that my windows 10 thinks it needs is NOT in the image. I still think that the 2023 build removed that driver. OH, now that it is working, I did another full image with 2023 and the driver is still there, which is why I believe that installing 2023 removed it.

 

Pete,

I forgot, temporarily disabling avast's self protection allows MR to complete backups successfully. The detailed fix with the latest free version of v6 does not work for me.

 

All very interesting re. this driver. I have just checked a very recent full image done under Build 7023, and when I loook in the \Windows\System32\Drivers folder I find mrcbt.sys with a date & time corresponding to the approximate imaging date & time.

I am assuming that this is as it should be and that therefore a restore of that image will be successful?

Regards, Baldrick

 

There's no reason to assume it won't be. What happened to MPSAN is very strange. As I tried to explain, he had 2-issues with that image... the first allowed it not to BOOT, this was not a MRCBT.SYS issue it was a BOOT path issue of which it tried to recover from by itself (I think it failed). MPSAN then had to use Reflect's FixBOOT to reconstruct the BOOT path. After that, when he tried to BOOT, during the normal Windows BOOTing process (which didn't even happen originally) it discovered that one of the drivers that its registry required the loading of, was missing... that was MRCBT.SYS. These were two separate issues of which I have no idea what caused either one. Either the image was bad or something took his System apart before he made that Build 2023 image.

Anyway, back to Build 7023... my experience has shown that 2023 does exactly what it's supposed to do when installed (at least on my test Systems), installs the driver as expected... it does not remove it. I'm not sure what happened to MPSAN but I don't believe there's any reason to suspect a BOOTing/Driver issue with its installation. I'm sure you have a pre-7023 image available for a quick RDR restore if necessary... maybe you can do a "feel-good" restore of an image taken right after your 2023 update just to be sure it's OK.

 

With RDR, this should be pretty easy to try (image 1st before test )... definitely worth the effort!

With that missing driver, you are correct.