Well, because I'm a bored, idiotic masochist, I decided to install the newest version and see if it fixed my error I got. I downloaded the version just released today, directly from Macrium, and built the PE. This is the result. I still can't restore an image!
The title bar in your screenshot says the Reflect build is 8313, which is the initial production release. The update released today to fix the restore issue is build 8324.
I had to check for update 6 times, but eventually I got it . I still get the same error with the updated version. The error seems to only be affecting my uefi partition; the rest restored fine.
Can you raise a ticket with the support team at macrium? see if they can figure out what is going on?
Are you referring to @n8chavez in this post? https://www.wilderssecurity.com/threads/macrium-reflect.356309/page-437#post-3212415
Yeah, since making the switch that jphughan notified us about, changing the reporting to MB/s, I am now hitting, briefly, much more realistic back up speeds of 5.2 gigs a sec. Acadia
Posted on the Macrium forum 19 October 2024 3:50 AM by PatrickS: “I updated Macrium Reflect X to Build 8324 on Windows 11 VM today. After I rebooted, I can no longer boot the VM. I'm receiving the following error message: Your PC/device needs to be repaired. The operating system couldn't be loaded because a critical system driver is missing or contains errors. File: \Windows\system32\drivers\mrigflt.sys Error code: 0xc000000f”
Another bug: I’ve been unable to create any Rescue Media capable of restoring any images on a USB 3.1 - connected external SATA drive in a Plugable docking station with either v8.1.8311 or v8.1.8325 on Windows 10. The images don't show on the screen, and can't be navigated to due to the drive not being recognized. I’ve tried seeming every combination of 2.0 and 3.1 thumb drive and CD media; and Linux (default, I think), RE, and PE. In all cases the Rescue Media shows the message “Rescue media successfully created” at the end. I don’t remember having any such problem before, and this evening I ran a randomly chosen Windows PE 10 Release 1709 (64 bit) CD without problem.
Not sure your issue qualifies as a “bug”. First, Linux isn’t the default for Rescue Media. It hasn’t even been offered since Reflect V5, or maybe V4? It was definitely gone by V6. If you open up Command Prompt in Rescue by clicking its icon in the taskbar, then run Diskpart, and enter “list disk”, do you see your storage device there? Can you browse it via the PE Explorer app? (Blue computer icon in taskbar.) If Diskpart can’t see it, then there’s something missing or otherwise problematic with the underlying WinPE/RE environment. That would certainly prevent Reflect from seeing the storage device, but that doesn’t mean Reflect caused the problem. Is this “Windows PE 10 Release 1709 (64 bit) CD” a Reflect Rescue Media build created on that WinPE version, or are you referring to an actual Windows 10 install media build here? You say you’ve tried WinRE and WinPE but didn’t specify which specific versions and feature releases of either one you’re actually using — like you did when discussing the CD above. Do other USB storage devices get detected? You mention thumb drives. Are those detected, or does Rescue find itself unable to see the device it just booted from? (Yes, that can happen and became a widespread issue with WinPE 3.1 after USB 3.x arrived.)
First, I appreciate your generosity in looking at this, and for that reason don’t want to waste any more of your time and energy on this matter just to help me if you think the problem is with my system and not Macrium. I plan to soon switch to Hasleo as my main imaging tool and demote v8.1 to a secondary tool. And, I can easily live with using a Rescue CD created with a previous version to restore images created with v8.1.8325 and later. I posted the problem I was having because I thought it was a Macrium bug and therefore something Macrium and other users would want to know about. “If you open up Command Prompt in Rescue by clicking its icon in the taskbar, then run Diskpart, and enter “list disk”, do you see your storage device there?” No, I do not see my storage device (USB 3.1 Plugable docking station containing SATA drive). “Can you browse it via the PE Explorer app? (Blue computer icon in taskbar.)” I also do not see it in the PE Explorer. The Plugable has a light that turns blue when is being seen by the system, and it has always stayed red in all my attempts to create a Rescue thumb drive or CD or DVD with v8.1.8311 and v8.1.8325. “If Diskpart can’t see it, then there’s something missing or otherwise problematic with the underlying WinPE/RE environment.” (Or in the Macrium software that’s creating the Rescue media?) “That would certainly prevent Reflect from seeing the storage device, but that doesn’t mean Reflect caused the problem.” “Is this ‘Windows PE 10 Release 1709 (64 bit) CD’ a Reflect Rescue Media build created on that WinPE version, or are you referring to an actual Windows 10 install media build here?” All my attempts to build rescue media (in all Macrium releases) have been simple Reflect Rescue Media builds, selecting RE or PE options in the Advanced section, and a few times using whatever is the default without going into Advanced. “You say you’ve tried WinRE and WinPE but didn’t specify which specific versions and feature releases of either one you’re actually using — like you did when discussing the CD above.” I built my latest media with Macrium Reflect Server v8.1.8325 (Win PE 10 v2004 64 bit) on a DVD. “Do other USB storage devices get detected?” “Yes, a 3.2 Samsung thumb drive and StarTech external drive are detected. My second identical Plugable docking station (containing a different brand of SATA drive) is NOT detected.” You mention thumb drives. Are those detected, or does Rescue find itself unable to see the device it just booted from? (Yes, that can happen and became a widespread issue with WinPE 3.1 after USB 3.x arrived.) Rescue DOES see the Samsung 3.2 thumb drive and CD and DVD it was booted from.
I thought version X was backward compatible with V.8. I reinstalled Windows, installed trial V.X and then tried to go back to V.8 from a few days ago. Not working. Is this by design?
Needs clarification. When you said you tried to go back to 8, are you saying you tried to downgrade the software itself, or were you trying to use X to restore an 8 image?
It can definitely be done. VX is backward compatible with backups created by all previous versions of Reflect. Can you provide any more detail beyond “not working”? While that’s a common problem report (to the dismay of IT people everywhere…), unfortunately it doesn’t give anyone any information that would allow them to help you.
@AlphaOne Regarding your responses about Rescue: Yes, Reflect builds Rescue Media. But in terms of WinPE/RE, it uses either the contents of your system’s WinRE partition or a WinPE file set downloaded directly from Microsoft. So if built-in tools such as Diskpart can’t see a device, it’s highly unlikely that this issue is caused by Reflect’s modifications — with one exception that I’ll address below but don’t believe applies to your specific case. However, if you ever want to rule out Reflect’s influence, then you could always try building actual Windows installation media for the same kernel that you’re using for Rescue Media. If you boot into regular Windows Setup, pressing Shift+F10 brings up Command Prompt. Or you could boot into your system’s actual WinRE environment, which would also allow you to invoke Command Prompt. The possible exception I mentioned above would be if drivers ADDED to the Rescue Media build created some sort of conflict. I’ve seen a few cases of this especially involving WinRE builds, likely because the WinRE partition can be customized on a per-system basis before Reflect even touches it, unlike WinPE files downloaded direct from MS. But the only drivers Reflect might add that would be relevant here would be for USB host controller chipsets, which is why I asked if other USB devices worked. Assuming the other USB devices that you WERE able to see were connected to ports controlled by the same chipset, your USB drivers don’t seem likely to be the problem — unless maybe there’s some bizarre problem condition triggered by the specific combination of the chipset in your StarTech dock and the drivers used in the WinPE/RE build. The only other variable I can think to tweak would be Rescue Media Builder’s settings under Advanced > Devices & Drivers, where you can override default driver injection behaviors. But if you’re using modern Windows kernels, you should be using the native USB xHCI drivers — as opposed to WinPE 3.1 where USB xHCI drivers had to be added. Sometimes tinkering with this resolved issues where Rescue was unable to see any USB devices at all, but that’s of course not the issue you’re having. So if this issue affects even WinPE, which wouldn’t be subject to per-system modifications like WinRE, and it only affects specific USB devices, I’m admittedly not sure what’s going on there. I am curious what would happen with the Windows install media or WinRE boot tests, though…
Thank you for the time and effort you put into this knowledgeable and thoughtful response. I'll spend some more time on this tomorrow to see if I can make any progress toward understanding what is happening.
Thanks for responding jphughan. This is really messing me up. I need to restore to a few days ago when I was using V.8. What I have tried to do is do what I would have done V.8 and V.8 has never failed me. While running V.X I click on Existing Backups tab and click on the image I want to restore. The program then informs me it is about Run From Windows PE. I then click on Reboot. The program then jumps to a Boot Manager page. It wants me to run windows repair from the installation disk. What is needed to fix this?
@AlphaOne I think WinPE is missing some drivers, like this. Have you tried plugging into another port, on the back panel, directly into the motherboard?
