By rescue2017 - 29 April 2017 9:31 AM
Hello!
Since 3 Years i use Macrium Reflect for daily Backup my Lenovo Thinkpad P70 Workstation Computer. It works fine.
After installing Windows 10 Creators Update (Win 10 Clean-Install) and Macrium Reflect i create a new Recovery USB Medium.
Macrium Reflect works fine - no problems!
When i test the USB Rescue Stick, the PC starts with PE5/PE10 Rescue Medium but the resolution is buggy. Please see attached picture. PE5 or PE10 the same resolution.
I cannot change with CTRL+SHIFT+R - only 640x480 is the resolution.
Can anybody help me? My System is up to date - drivers, bios etc!
My System is Windows 10 Creators Update on Lenovo Thinkpad P70 Workstation Notebook.
Befor the new installation i had no problems with the Rescure Medium.
|
By Nick - 29 April 2017 10:39 AM
Hi
Thanks for posting. Unfortunately there's a compatibility issue with the Lenovo UEFI BIOS and the Windows ADK. Please see this Lenovo KB:
https://support.lenovo.com/gb/en/solutions/ht503599
Can you disable 'Secure Boot' in the system BIOS to confirm this issue?
|
By rescue2017 - 29 April 2017 10:54 AM
Secure Boot is disabled- always - no change!
I Need a Macrium Reflect Rescue Stick - no windows Start Disk !
|
By Nick - 29 April 2017 11:42 AM
Please download bootx64.efi from here:
http://updates.macrium.com/reflect/utilities/pe/bootx64.efi
This is the latest PE UEFI boot microcode and may not suffer the Lenovo bug.
Replace the file : \EFI\Boot\bootx64.efi on your USB flash drive.
|
By rescue2017 - 29 April 2017 12:13 PM
Hello! Nick, i have replace the downloading file to my USB Stick, bit nothing help!
Same with PE 5 and PE 10.
See photo.
What can i do?
|
By Nick - 29 April 2017 12:20 PM
I would suggest trying PE 4.0, but if you are trying to restore a non booting system you'll have to create the USB media on a different PC.
You could also try DiskRestore. This should work with 640x480
http://knowledgebase.macrium.com/display/KNOW7/Running+DiskRestore+from+Windows+PE?src=search
|
By rescue2017 - 29 April 2017 12:23 PM
So, you say i should try PE4? Is that compatible with Win 10?
Is a way to create a DVD ROM against USB Flash Drive?
So, whats the solution for the future. I think many users have thinkpad Computers. Do you fix the problem?
|
By Nick - 29 April 2017 12:36 PM
You just need to boot your hardware to run the recovery environment, so PE 4 should be fine. Win 10 compatibility isn't relevant.
We are still investigating how this problem is manifesting itself with the Lenovo BIOS before we can offer a definitive solution. I suspect that Lenovo may update their BIOS firmware.
PE running from DVD has the same problem. Only the boot menu has the native resolution.
|
By jphughan - 29 April 2017 1:01 PM
PE 4 is confirmed working on Lenovo systems that display in 640x480 in newer PE versions, and you still get USB 3 support. Not sure about NVMe support though (I think that only became native in 4.0), but that driver can be added manually. This does sound like a fix that Lenovo would have to deliver, but who knows if they'd even bother with some systems depending on how old they are.
|
By rescue2017 - 29 April 2017 1:14 PM
Ok. I will create a PE 4 USB Stick in Macrium Reflect. So... Should i replace the bootx64.efi File .... see post .... from Nick.. or nothing?
|
By rescue2017 - 29 April 2017 1:39 PM
Soo, i have created a PE 4 USB Medium. I can tell you:
NVME Driver supported.
No change in resolution. Same bug.
See picture.
What should i do?
Macrium Support Technicans / Lenovo / Microsoft please fix the problem, so that the users can use a usb rescue stick with Win PE10/PE5 in Windows 10 Creators Update and high resolution, not 640x480.
Please answer here also and bring a fix / update.
|
By jphughan - 29 April 2017 5:03 PM
Do you have the latest BIOS/Firmware installed? If it still doesn't work, you could use WinPE 3.1 if you also switch your system temporarily to support Legacy booting, either by disabling UEFI or (preferably) by enabling CSM (Compatibility Support Module) or Legacy Option ROMs as it might be called, which allows both UEFI and Legacy booting. WinPE 3.1 doesn't use UEFI booting at all and should therefore have no issue, and that BIOS change would allow you to boot it. Then you would either have to switch back to UEFI mode or (optional but recommended) re-disable CSM/Legacy OROMs again to boot the restored disk. You'll definitely need to add Win7 NVMe drivers if you have an NVMe SSD though -- same for USB 3 drivers.
|
By rescue2017 - 29 April 2017 5:34 PM
Is this a solution? Not really!
Macrium should investigate that problem!
Maybe Win10 Creators Update is the reason for that issue so please support-> fix the Problem!
Are in the Macrium Support a German speaking Technican?
|
By jphughan - 29 April 2017 5:57 PM
This isn't a Macrium problem, and it has nothing to do with the Creators Update because Reflect still uses the Anniversary Update WinPE files. This issue exists because some Lenovo systems don't have full or correct support of the UEFI spec, and as Nick mentioned earlier, you would have the same issue if you booted into regular WinPE, such as by booting a regular Windows ISO. It just doesn't create a problem there because Windows Setup is actually usable at 640x480 because the interface is simpler. But there's nothing Macrium can do about this without either using Linux rather than WinPE or figuring out how to hack WinPE. The real fix would have to come from Lenovo. But since vendors are likely to continue providing Windows 7 drivers for at least a few more years, WinPE 3.1 should continue to be a usable platform for Rescue Media if Lenovo doesn't fix this for some systems.
|
By rescue2017 - 29 April 2017 6:52 PM
Macrium Reflect is a great software company/program and so this company should investigate this problem and speak with Microsoft/Lenovo and fix the issue!!!
Macrium Reflect (in old Versions), there was a great Linux-based Rescue Medium. Is this possible to get this / work fine??
|
By jphughan - 29 April 2017 7:06 PM
The Linux-based version was dropped because it represented additional engineering effort to maintain and it wasn't widely used. It was also more difficult to add drivers to a Linux-based Rescue environment for Windows users. Additionally, since this an issue of some Lenovo computers not complying with the UEFI spec, it's possible that a Linux kernel would have the same issue. I agree that Macrium is a great company, but I don't think they're large enough to get attention from Lenovo -- although I could of course be wrong. But again, this issue isn't limited to Reflect; it would apply to ANYTHING that uses WinPE in UEFI mode and that doesn't work well at 640x480 resolution. Lastly, I think this has ALREADY been fixed on newer Lenovo models, so this would be a case of getting Lenovo to spend effort fixing older systems.
In the meantime though, why don't you at least TRY WinPE 3.1 with the BIOS tweaks I mentioned since that would solve the immediate problem while you wait for a possible future real solution from Lenovo.
|
By rescue2017 - 29 April 2017 9:09 PM
I think and i am sure, that many pc users - and so macrium customers are having thinkpad computers and so please macrium investigate the issue and fix ist with lenovo!
|
By jphughan - 29 April 2017 10:16 PM
rescue2017 - 29 April 2017 9:09 PM
think and i am sure, that many pc users - and so macrium customers are having thinkpad computers and so please macrium investigate the issue and fix ist with lenovo!
Well as one of those users, can you at least check whether PE 3.1 works correctly as a temporary fix? Last time this issue was discussed here, using PE 4.0 rather than 5 or 10 resolved the issue for the user's Lenovo system. I think it's nice that you think Macrium might be able to push a company as large as Lenovo to go back and fix their older systems now, but again I think that is a completely unrealistic expectation.
|
By rescue2017 - 29 April 2017 10:35 PM
Are you a official Macrium Reflect Technican?
I think for troubleshooting is
1. Macrium Reflect
2. Lenovo / Microsoft
the right way, so the company should fix the issue with Resolution in Win PE.
I dont want to make experience with Win PE 3 - i have a Samsung SSD 960 PRO NVME SSD ... and so i do not will change the bios settings ....
|
By rescue2017 - 29 April 2017 10:38 PM
Since 2 days the users / support say, please create a Win PE 5 USB Rescue media, that works fine -> no change - Resolution 640x480
... then the say ... please create a Win PE 4 USB Rescue media, that works fine -> no change - Resolution 640x480
... and today .... please create a Win PE 3 Rescue ....
I dont want experience!
I want a solution!
|
By jphughan - 29 April 2017 11:20 PM
The different suggested fixes for other users could have been because they weren't all using the same Lenovo model. It looks like there are 2 separate issues that can create this 640x480 resolution limitation. One issue is that SOME Lenovo systems have an incorrect UEFI implementation (which is Lenovo's fault) but the other issue is that according to the Lenovo KB that Nick posted earlier, ALL Lenovo systems have an issue specifically with WinPE 10 1607/Anniversary, which is the newest version that Reflect can use for Rescue Media right now. Lenovo blames that on a Microsoft bug, and their suggested workaround is to use a file from WinPE 10 1511, which is what Nick posted -- so it can make sense that different cases will have different suggested fixes.
I understand wanting a real fix rather than using a workaround, but until a real fix becomes available, a workaround is better than not having anything, especially if a real solution NEVER becomes available for the incorrect UEFI systems because Lenovo decides never to develop a BIOS update for their older systems. In that case if you don't accept a workaround, you might be stuck with nothing until you get a new laptop. Everything Reflect does will work on WinPE 3.1 Rescue Media. The only additional requirement is manually adding some drivers that are easy to get from Lenovo's site and then enabling CSM/Legacy Option ROMs if you normally run in UEFI mode (and you ONLY need to do that when you need to boot Rescue Media). That's inconvenient, but it's a LOT better than not having Rescue Media.
And for that matter, since you're so passionate about demanding a fix, if your issue is due to the incorrect UEFI implementation, have you considered posting about this on the Lenovo forums since Lenovo created this issue in the first place, instead of just expecting Macrium to do it?
|
By jphughan - 29 April 2017 11:26 PM
And no I don't work for Macrium, but again I've explained why I feel this isn't their problem to fix. Lenovo did something that is incompatible with Microsoft's WinPE environment in one case, and in another case according to Lenovo, Microsoft has a bug in their WinPE environment -- neither of those is Macrium's fault or within their ability to fix. But you of course can and obviously do feel differently. And since PE 3.1 isn't an option in your mind, there's no additional information or help I can provide for you at this point, so I'll just wish you good luck on getting a fix that you consider acceptable and focus on other threads on this forum instead. I personally would rather have working Rescue Media even if it involves some inconvenience WHILE I wait for a better solution instead of letting myself sit around with nothing that works while I wait for a fix, but that's just me.
|
By rescue2017 - 30 April 2017 9:11 AM
Please Macrium Reflect Technicans investigate that issue, thanks!
|
By Nick - 30 April 2017 11:58 AM
Hi
Apologies for the frustration that this issue is causing for some Macrium Reflect users with Lenovo PCs.
As has been mentioned, the boot process of Windows PE is controlled by the UEFI firmware/micro code and there are compatibility issues between Lenovo and Microsoft PE. It seems that some Lenovo UEFI implementations may have been 'out of spec' and understanding the scope of problem, e.g, which models can boot PE 10, which can boot PE 5.0 or 4.0 and which don't support any external PE media booting at the correct resolution is non-trivial.
Note this issue appears widespread and has been a problem with Lenovo for a while:
https://social.technet.microsoft.com/Forums/en-US/c502f331-79d3-40e5-b24c-58e879ca0512/winpe-resolution-issue?forum=mdt
The solution that has always worked in the past is to use PE 5.0 or 4.0 and this is is first case we have seen where no PE version supports UEFI booting of external media with the correct screen resolution.
If using an earlier PE version doesn't help, then you can boot your USB media in 'legacy' MBR mode. In MBR mode the screen resolution will be native. You can restore partitions using MBR mode but the 'Fix Boot Problems' option will not function due to PE running in MBR mode. Setting the BIOS to boot in Legacy mode varies between systems, but, if you have a 'Legacy first' option in the boot order and move this to the top, then the start up sequence should detect your external media as MBR bootable.
|
By rescue2017 - 30 April 2017 12:11 PM
Hello Nick, nice to answer me! :-) Thanks!
First - i am a Macrium User since many years - you can check this... you know my email adress!
So... I have the Lenovo Thinkpad Workstation Notebook P70 since 1 Year, everything worked fine since April 2017. This was the time where i make a Clean Install of Windows 10 with Creators Update and buy Macrium Reflect V7 and create a new Recovery Medium.
Before - everything worked fine. Everything. And i worked on the Lenovo Thinkpad P70 machine. No issues.
Please look in google search - many posts with the same issue..... "can only see 640x480 resolution ..." -> And you think that all the Users have Thinkpad Computers?
Is that possible - that Windows PE miss the drivers for the graphic cards .... because i have found a forum post you can see here: http://forum.macrium.com/Topic8877.aspx?PageIndex=2#bm9116
Nick, for the future, is there a german-speaking support technican in your company?
And Nick i will inform you, that Macrium is a great software for Backing up - the Best i think, but please help me and the other users to fix the issue, thank you!
Regards from Austria! And i hope, you have a sunny day!
|
By Arvy - 30 April 2017 2:21 PM
So... I have the Lenovo Thinkpad Workstation Notebook P70 since 1 Year, everything worked fine since April 2017. This was the time where i make a Clean Install of Windows 10 with Creators Update and buy Macrium Reflect V7 and create a new Recovery Medium.
I can offer no help beyond what Nick has already suggested, but you should be aware that you are far from alone in experiencing some strange results after installing the Windows 10 "Creators Update" manually. Did you know that, despite having made the set-up ISO available for download earlier this month, Microsoft has recommended against its manual installation citing unexpected difficulties with unspecified "problem devices" as the reason? That sounds as if it the issues and their consequences might possibly involve some system UEFI configurations that could, in turn, affect WinPE start-ups and device support. There are many on-line articles on the subject. This one is typical.
|
By rescue2017 - 30 April 2017 3:28 PM
Hello together!
First - i am not a computer beginner!
I have noticed about Windows Update and the articles in the last days -> but -> why is this issue reported in 2016, please see here: http://forum.macrium.com/Topic8877.aspx?PageIndex=2#bm9116
So - i think the reason for this issue (Screen Resolution in Win PE 640x480) is another.
|
By Arvy - 30 April 2017 4:05 PM
No belittling of your computer experience or other adversarial implication of any kind was intended in my reply. Its only purpose was to make you aware, in case you weren't already, that Microsoft itself has recommended against manual installation of its "Creators Update" and its stated reasons for that recommendation. And my secondary hope was that others reading this thread might also benefit from that cautionary information.
In fact, the originator of the 2016 thread to which you refer ultimately arrived at a similar conclusion about the cause for his problem involving a Win 10 version 1511 cumulative update. Perhaps you may be as fortunate as he was in having the issue resolve itself following a subsequent MS cumulative update. I sincerely hope so. Good luck.
|
By rescue2017 - 4 May 2017 10:59 AM
Macrium Support do you have a solution?!
|
By jphughan - 4 May 2017 3:56 PM
+xMacrium Support do you have a solution?!
Nick already gave you Macrium's solution -- you just didn't seem to like it when others suggested the exact same thing:
+xIf using an earlier PE version doesn't help, then you can boot your USB media in 'legacy' MBR mode. In MBR mode the screen resolution will be native. You can restore partitions using MBR mode but the 'Fix Boot Problems' option will not function due to PE running in MBR mode. Setting the BIOS to boot in Legacy mode varies between systems, but, if you have a 'Legacy first' option in the boot order and move this to the top, then the start up sequence should detect your external media as MBR bootable.
Be realistic for a moment. According to Nick, you're the first person who has reported this issue where the easier workarounds of PE 4 or 5 didn't resolve the issue. Do you really expect Macrium to spend engineering resources either hacking Microsoft's WinPE files or resurrecting Linux-based Rescue Media (neither of which are even guaranteed to solve the problem if this is a UEFI compliance issue) just to deliver a solution for one person, especially when you could solve this issue yourself much more quickly and with much less effort by making a simple BIOS change? And as for contacting Lenovo, if the issue is already as widely reported as Nick says, it's safe to assume that Lenovo is already aware of this issue and they've either decided not to bother fixing it on older systems, or perhaps there's a hardware limitation involved which means they CAN'T fix it with just a BIOS/Firmware update. Either way, I don't see how contacting Lenovo given these circumstances is likely to lead to a fix either.
|
By rescue2017 - 4 May 2017 5:38 PM
With all due respect, jphughan, that can not yet be acceptable! That can not be acceptable, to use Win PE 3 or make different UEFI-Settings!
I am not the only person with this issue, please look in forums, and also here Macrium Forum!
I think the reason of this issues are Windows with the Updates and Macrium Reflect. Lenovo maybe a little bit.
jphughan, thanks for your comments, but it´s time for a Macrium Statement.
Macrium Reflect has a great support, and so i hope, that the Support answer me and fix the issue in foreseeable future.
Because 640x480 in Rescue Media is not acceptable.
The alternative is to give Acronis True Image a Chance. But i think that the great Macrium Support fix the issues.
|
By jphughan - 4 May 2017 6:32 PM
It's not a Windows Update issue. The WinPE files that Reflect (and any other application) accesses are downloaded by the Windows ADK installer and just stored on the hard drive; they're never updated by Windows Update. Also, the newest WinPE version Reflect uses is WinPE 10 1607 (Anniversary) because Reflect hasn't been updated to use WinPE 10 1703 (Creators) yet, so it's not a Creators Update issue. Lastly, Reflect doesn't control the display resolutions offered to WinPE by the underlying hardware, so it's not a Reflect issue. Again, you can confirm that by booting into a regular WinPE environment such as a Windows Installation ISO where Reflect isn't even involved, and you'll still see 640x480 resolution.
I actually HAVE been looking at other forum posts, and you're the only one I've found who is having the 640x480 issue and hasn't fixed it by following the earlier suggestions Nick already mentioned -- Nick said the same thing above. Then again, you're also not willing to even TEST the WinPE 3.1 suggestion, so maybe you're the only one having this issue who's taking that stance and everyone else would rather just make the BIOS change when they need to use Rescue Media instead of not having any way to use Rescue Media. As I said earlier, I understand that a BIOS change is annoying and that you shouldn't HAVE to do it, but honestly, how frequently are you even booting into Rescue Media anyway?
The issue isn't Lenovo "a little bit" -- their firmware isn't properly supporting Graphics Output Protocol. And maybe there are some systems from other vendors that have the same issue. But you still expect Macrium to fix a hardware/firmware/WinPE problem, just so you don't have to spend 10 seconds making a configuration change because you have a laptop that doesn't comply with an official spec. That is not a reasonable expectation, for reasons I outlined above. Imagine if there was a bug in your graphics drivers, OS, or BIOS/firmware that prevented your display from working correctly in regular Windows -- would you contact the companies that make every application you use asking them to each provide an update that worked around that bug, or would you expect a fix from the people who created the problem so that all of your applications would then start running properly? Macrium is in the same position. They're an application developer that relies on the OS, drivers, and BIOS/firmware to work properly, and on your system, they don't. But that doesn't mean Macrium can fix it. You just want them to because this is the only WinPE application you use.
Why aren't you on the Lenovo forums talking to THEM about how unacceptable it is that they created a system that requires you to use WinPE 3.1 and make BIOS changes to get a usable display resolution? I personally think that if you like Reflect otherwise, it's absurd to switch to an entirely different product just to avoid 10 seconds of effort whenever you actually need to boot Rescue Media, but that's of course your decision. But you got your "Macrium statement" above; you just don't like it.
|
By rescue2017 - 4 May 2017 6:52 PM
I am in Lenovo Forums and another user has the same issues, and also users here on Macrium Forum has issues with resolution, with 640x480 ....
For example: http://forum.macrium.com/Search.aspx?Keywords=640x480
For example: http://forum.macrium.com/Search.aspx?Keywords=resolution
So it´s time for the Macrium Support. It´s time for investigation the problem.
Thanks for your messages.
|
By rescue2017 - 8 May 2017 11:34 AM
What´s new ?
|
By Bastet - 10 May 2017 2:10 PM
Same for me running PCSpecialist Windows 10 pro 64bit, with a HD resolution 17in screen, using the MR boot USB my resolution is very low/basic - either same as OP or 800x600 resolution. PC fully upto date running creator's update. I have recently upgraded from v6 free to v7 paid & both same. I'm sure in the past that resolution was much higher.
|
By rescue2017 - 10 May 2017 2:26 PM
+xSame for me running PCSpecialist Windows 10 pro 64bit, with a HD resolution 17in screen, using the MR boot USB my resolution is very low/basic - either same as OP or 800x600 resolution. PC fully upto date running creator's update. I have recently upgraded from v6 free to v7 paid & both same. I'm sure in the past that resolution was much higher.
What PC System (Brand) did you have?
|
By Bastet - 10 May 2017 2:32 PM
rescue2017 - 10 May 2017 2:26 PMBastet - 10 May 2017 2:10 PM
ame for me running PCSpecialist Windows 10 pro 64bit, with a HD resolution 17in screen, using the MR boot USB my resolution is very low/basic - either same as OP or 800x600 resolution. PC fully upto date running creator's update. I have recently upgraded from v6 free to v7 paid & both same. I'm sure in the past that resolution was much higher
hat PC System (Brand) did you have?
PC Specialist Optimus VII V17-960 Gaming Laptop, Intel Core i7-6700HQ 2.60GHz 8GB RAM, 2TB HDD, 17.3" LED, DVDRW, NVIDIA GTX 960M, WIFI, Webcam, Bluetooth, Windows 10 Home 64bit. Upgraded to Pro.
|
By rescue2017 - 10 May 2017 2:53 PM
You have no Lenovo Laptop, correct?
|
By Bastet - 10 May 2017 3:01 PM
rescue2017 - 10 May 2017 2:53 PM
ou have no Lenovo Laptop, correct?
Yes it is not a Lenovo, afaik the laptop has a Clevo motherboard/baseboard.
|
By rescue2017 - 10 May 2017 3:04 PM
Macrium says that this issue is only a Lenovo/Microsoft issue.
And macrium do not make a big effort to solve this problems with Resolution 640x480.
So Macrium please investigate this issue / problems. Thats not only a Lenovo issue. Please fix it! Thanks!
Otherwise i am looking for a better supported backup software. Sorry for my bad english, i hope you understand it.
I am a Macrium user since 4 Years and i like macrium.
I am very very disappointed, that macrium do not make a big effort to fix this problems and says only Lenovo/Microsoft can fix this.
That’s not correct, because here we have a user “Bastet” with the same issue.
|
By jphughan - 10 May 2017 3:23 PM
+xrescue2017 - 10 May 2017 2:26 PMBastet - 10 May 2017 2:10 PM
ame for me running PCSpecialist Windows 10 pro 64bit, with a HD resolution 17in screen, using the MR boot USB my resolution is very low/basic - either same as OP or 800x600 resolution. PC fully upto date running creator's update. I have recently upgraded from v6 free to v7 paid & both same. I'm sure in the past that resolution was much higher
hat PC System (Brand) did you have? PC Specialist Optimus VII V17-960 Gaming Laptop, Intel Core i7-6700HQ 2.60GHz 8GB RAM, 2TB HDD, 17.3" LED, DVDRW, NVIDIA GTX 960M, WIFI, Webcam, Bluetooth, Windows 10 Home 64bit. Upgraded to Pro.
The version of Windows you're running doesn't matter for Rescue Media; what matters is the version of Windows PE you used for your Rescue Media. If you're using WinPE 10 1607 (Macrium doesn't yet build Rescue Media with WinPE 10 1703 even if you're running Creators), have you tried the file replacement recommendation that Nick recommended in this thread yet? If that doesn't work, have you tried building your Rescue Media with WinPE 5 or 4 instead? 5 would be preferable since it supports USB 3.0 if you need that. One or both of those older versions have worked for users affected by this issue when they use WinPE 10. The last resort that rescue2017 has not been willing to try would be using WinPE 3.1 and then switching your system to boot in Legacy rather than UEFI mode when you need to use Rescue Media. That would sidestep any issues with incorrect UEFI spec implementations on the motherboard firmware, which seems to be the underlying cause of this issue on systems that experience it, although if your system and/or Rescue Media needs required them, you'd need to manually supply drivers for USB 3.0 and NVMe (PCIe SSD). Thus far that's known to exist on several Lenovo models, but they're apparently not the only ones. Would be interesting to see which of those workarounds resolves the issue for you if you're willing to try any of that.
|
By rescue2017 - 10 May 2017 3:48 PM
Hy jphughan, thanks for your answer, but please stop.
Thats no satisfying solution to use WinPE 3.1 for Rescue Media of Macrium Reflect on Windows 10 Creators Update.
|
By jphughan - 10 May 2017 4:04 PM
+xHy jphughan, thanks for your answer, but please stop. Thats no satisfying solution to use WinPE 3.1 for Rescue Media of Macrium Reflect on Windows 10 Creators Update.
Some people might prefer actually being able to use Rescue Media, even with that workaround, instead of being stuck with 640x480 resolution that makes Reflect impossible to use. Just because YOU don't consider that an acceptable solution doesn't mean that others will feel the same way. I will continue to suggest fixes that work TODAY for people who might want them. If they don't, then that is of course their decision, but don't expect me to stop trying to help people just because you personally don't like some of the options.
And in any case, I clearly labeled WinPE 3.1 with Legacy booting as a "last resort".
|
By rescue2017 - 10 May 2017 4:18 PM
Sorry, i personality think thats no acceptable solution.
|
By Bastet - 10 May 2017 4:24 PM
jphughan - 10 May 2017 3:23 PMBastet - 10 May 2017 2:32 PMrescue2017 - 10 May 2017 2:26 PMBastet - 10 May 2017 2:10 PM
me for me running PCSpecialist Windows 10 pro 64bit, with a HD resolution 17in screen, using the MR boot USB my resolution is very low/basic - either same as OP or 800x600 resolution. PC fully upto date running creator's update. I have recently upgraded from v6 free to v7 paid & both same. I'm sure in the past that resolution was much highe
at PC System (Brand) did you have? C Specialist Optimus VII V17-960 Gaming Laptop, Intel Core i7-6700HQ 2.60GHz 8GB RAM, 2TB HDD, 17.3" LED, DVDRW, NVIDIA GTX 960M, WIFI, Webcam, Bluetooth, Windows 10 Home 64bit. Upgraded to Pro he version of Windows you're running doesn't matter for Rescue Media; what matters is the version of Windows PE you used for your Rescue Media. If you're using WinPE 10 1607 (Macrium doesn't yet build Rescue Media with WinPE 10 1703 even if you're running Creators), have you tried the file replacement recommendation that Nick recommended in this thread yet? If that doesn't work, have you tried building your Rescue Media with WinPE 5 or 4 instead? 5 would be preferable since it supports USB 3.0 if you need that. One or both of those older versions have worked for users affected by this issue when they use WinPE 10. The last resort that rescue2017 has not been willing to try would be using WinPE 3.1 and then switching your system to boot in Legacy rather than UEFI mode when you need to use Rescue Media. That would sidestep any issues with incorrect UEFI spec implementations on the motherboard firmware, which seems to be the underlying cause of this issue on systems that experience it, although if your system and/or Rescue Media needs required them, you'd need to manually supply drivers for USB 3.0 and NVMe (PCIe SSD). Thus far that's known to exist on several Lenovo models, but they're apparently not the only ones. Would be interesting to see which of those workarounds resolves the issue for you if you're willing to try any of that.
I'll try that fix & report back.
|
By jphughan - 10 May 2017 4:53 PM
+xSorry, i personality think thats no acceptable solution.
And that's fine -- but you're not the only person in this thread asking for help with this issue anymore. But honestly, are you telling me that if you had a system failure that required you to use Rescue Media to restore from a backup, you would STILL refuse to use WinPE 3.1 media with a temporary BIOS change to make that possible? Would you really instead choose to just start fresh and pretend you didn't have any backups to restore from? If that's truly what you would do, then that seems completely irrational to me, but if instead you would at that point use WinPE 3.1 with a temporary BIOS change, then it seems inappropriate for you to ask people to stop suggesting a workaround that you would use yourself in dire circumstances. Most people would probably rather make a temporary BIOS change to get usable Rescue Media instead of being left completely unable to restore their backups, and would therefore appreciate being made aware of this option.
And lastly, for what it's worth, Macrium didn't say this was a "Lenovo problem". They said it was a problem with incorrect UEFI spec implementation that they were SEEING on several Lenovo systems -- and for those systems, it's a "Lenovo problem" in the sense that Lenovo controls the firmware and only they can update their UEFI. But if Clevo has ALSO implemented UEFI incorrectly, then for those systems it would be a "Clevo problem". As for the "Microsoft problem", Lenovo is the one accusing Microsoft of a bug in their KB article. I haven't seen Macrium make that claim.
|
By Bastet - 11 May 2017 10:32 AM
OK, tried Nick's fix & tested the USB - same resolution problem.
|
By rescue2017 - 11 May 2017 10:47 AM
Hehe.... :-(
So Macrium investigate the Problem!
I am not the only person with the problems, you also Basket.
Please fix the issue!
|
By Mike A - 11 May 2017 12:12 PM
Hi,
We cannot fix the BIOS / UEFI implementation directly as this is supported by your computer/motherboard manufactuer. However, a work item was raised for a suitable workaround and will be prioritised accordingly by the development department. I would still contact the manfactuer to resolve their issue.
Thanks,
Mike.
|
By jphughan - 11 May 2017 2:12 PM
Bastet - 11 May 2017 10:32 AMK, tried Nick's fix & tested the USB - same resolution problem.
What about trying WinPE 5 and then WinPE 4? For many other systems that have encountered this issue, one of those earlier versions has solved it, but different systems have worked with different versions, so you may need to try both. And then as I said, WinPE 3.1 booted in Legacy mode would be the last resort.
|
By Danskeman - 24 May 2017 8:43 AM
There is a solution that works on any Lenovo afaik.
Download this iso and create a bootable usb drive.
https://www.tenforums.com/software-apps/27180-windows-10-recovery-tools-bootable-rescue-disk.html
Macrium Reflect is one of the tools and this will boot in full resolution.
Confirm it is working ok anybody with Lenovo, and I will show you how to update the version when needed.
|
By Danskeman - 24 May 2017 8:50 AM
There is a solution that works on any Lenovo afaik.
Download this iso and create a bootable usb drive.
https://www.tenforums.com/software-apps/27180-windows-10-recovery-tools-bootable-rescue-disk.html
Macrium Reflect is one of the tools and this will boot in full resolution.
Confirm it is working ok anybody with Lenovo, and I will show you how to update the version when needed.
PS to Macrium developers, a simple pragmatic solution to the 640*480 problem would be to simply add scroll bars to the screens or reorganise where the action buttons are as the problem is not really the resolution but the fact the screens are too big for low resolution and you cannot get to the button to continue recovery.
This is 100% within Macrium's ability to resolve.
I despair somtimes when techies gold plate a solution when a basic solution would at least make it useable in low res.
|
By Arvy - 24 May 2017 12:15 PM
There is a solution that works on any Lenovo afaik.
Dunno about that as I haven't tried that particular pre-built WinPE "rescue" ISO. I can tell you, however, that my own experience with "customized" WinPE building (mostly with WinBuilder) shows a lot of variation in results for screen resolution switching regardless of the hardware involved. Windows 10 seems to be the least consistent. Resolution settings with some builds using various W10 ADK boot.wim bases and install.wim extractions work well and some don't work at all. It's pretty much a "try it and see" process.
|
By Danskeman - 24 May 2017 12:47 PM
+xThere is a solution that works on any Lenovo afaik.
Dunno about that as I haven't tried that particular pre-built WinPE "rescue" ISO. I can tell you, however, that my own experience with "customized" WinPE building (mostly with WinBuilder) shows a lot of variation in results for screen resolution switching regardless of the hardware involved. Windows 10 seems to be the least consistent. Resolution settings with some builds using various W10 ADK boot.wim bases and install.wim extractions work well and some don't work at all. It's pretty much a "try it and see" process.
Fair enough but I bet it does work. In any case, there is a simple solution i.e. make the screens usable in low resolution. This is not rocket science!
|
By Arvy - 24 May 2017 12:57 PM
Well, as Mike A said, they are working on it. I'm sure they'll come up with further improvements, but my own experience suggests that it's going to take some considerable amount of "trial and error" to accommodate all of the variables involved. If you think it's bad now, you should have seen their single pre-set WinPE "rescue" resolution before they added that Other Tasks switcher. 
|
By Danskeman - 10 September 2017 8:53 PM
Actually, it is not specifically the low resolution that is the problem. The problem is the design of the recovery screens do not allow you to click the buttons as they are 'off screen'.
It would be a trivial fix to either move buttons so visible in a low res screen, or add scroll bars.
Not all solutions have to be high tech!
|
By jphughan - 10 September 2017 10:17 PM
+xActually, it is not specifically the low resolution that is the problem. The problem is the design of the recovery screens do not allow you to click the buttons as they are 'off screen'.
It would be a trivial fix to either move buttons so visible in a low res screen, or add scroll bars.
Not all solutions have to be high tech!
This would be a workaround, not a solution, and in fairness to Macrium, I don't believe anyone designs their UIs to target a 640x480 canvas anymore. I also don't know enough about Windows UI design to know for certain whether placing the Back/Next/Finish wizard navigation buttons inside a scroll-enabled area would in fact be trivial, but I wouldn't assume that it is -- and even if it IS trivial, I don't think that would align with UI best practices. Certain elements are deliberately intended to be pinned to the bottom of the window, independent of any scroll-enabled content that may exist within it.
However, mulling this issue over myself as a result of your post, one idea I've just had would be for the wizard windows to size themselves dynamically based on display resolution AND make sure that the main content area is always scroll-enabled, but keep the buttons fixed to the bottom of the window. This would maintain existing UI design norms, and the dynamic window sizing behavior means people with 640x480 resolution are accommodated, while people who are NOT stuck at 640x480 will not be dealing with tiny wizard windows that always require scrolling/resizing to see everything and asking themselves why Macrium isn't taking advantage of the extra display area that's been available for (most) PCs manufactured over the last 20 years. 
In fact I may add this to my "Aggregated quick win requests" Wish List thread, since this certainly sounds easier than working around bad UEFI implementations/display drivers and possible WinPE bugs that have been implicated as the cause of this issue where it exists.
|
By Gork - 1 October 2017 4:37 AM
I'm having the same issue with v7.1.2614 - Windows PE 10 UEFI. I don't believe it was a problem with my rescue media created with the last MR v7.x version, but I can't be sure. I am unable to use scroll bars to see all the information in 800x600 resolution, but it appears I can at least access enough of the GUI to be able to use the restore option. As others have posted, the change display resolution option in the MR GUI only has 800x600 listed. I'm sporting an an Alienware 13 R3.
|
By Nick - 1 October 2017 12:13 PM
Hi Gork
The resolution in PE is unchanged in 7.1. This is a pre-existing UEFI issue.
|
By jphughan - 1 October 2017 2:02 PM
Gork - 1 October 2017 4:37 AM
'm having the same issue with v7.1.2614 - Windows PE 10 UEFI. I don't believe it was a problem with my rescue media created with the last MR v7.x version, but I can't be sure. I am unable to use scroll bars to see all the information in 800x600 resolution, but it appears I can at least access enough of the GUI to be able to use the restore option. As others have posted, the change display resolution option in the MR GUI only has 800x600 listed. I'm sporting an an Alienware 13 R3.
Based on Nick’s answer, if you’re right that this didn’t exist before, has your BIOS revision maybe changed since the last time you tried Rescue Media? Although that would suggest that the update made things worse. Only having a single resolution in UEFI mode isn’t necessarily a problem (I only have 3200x1800 in UEFI), but obviously the resolution should match the native resolution of the panel. That said, yours is the first post I’ve seen being locked at 800x600 rather than 640x480. Maybe try a BIOS update if you haven’t? Otherwise, another possible cause of this according to a Lenovo KB appears to be a bug specifically in Win10 1607, so it might be fixed when Macrium supports Win10 1703.
|
By Diazruanova - 5 October 2017 3:13 PM
Hi,
On the first page of this thread, Nick suggests:
"You could also try DiskRestore. This should work with 640x480"
http://knowledgebase.macrium.c...
If I simply use the suggested command to open the "Restore Dialog":
"x:\program files\macrium\diskrestore.exe"
...do I get the ALL the options that the regular UI window provides?
Thanks
|
By jphughan - 5 October 2017 3:29 PM
No. According to this KB article, you will not have the option to rearrange or resize partitions on the destination compared to how they exist in the source image, although it appears you still have the option to exclude certain partitions entirely.
|
By Diazruanova - 5 October 2017 3:39 PM
Thanks jphughan
Well, at least it seems a good option to restore your partitions in case of a fatality! but certainly, this issue has taken too long without having a solution from Macrium, because, I really doubt there will be a fix from the Hardware manufacturers (Lenovo mainly)
|
By jphughan - 5 October 2017 4:55 PM
In my "Aggregated quick-win feature requests" thread in the Wish List section, I've linked to a suggested workaround that involves scroll-enabling and dynamically sizing that disk restore UI. I can't know for certain how easy that would actually be (and testing in a VM, wow 640x480 is an absurdly tiny space to work with these days!!), but I agree it would be great to have a fix or at least a workaround given that so many users seem to be affected. And even before that suggestion was posted elsewhere, Macrium posted in this thread that they're looking into how to get around this, but I do sympathize that they are application developers, not OS or firmware developers, and as such they depend on the underlying OS and hardware to perform properly, just as any other application developer would. In the analogy I gave earlier in this thread, if "real" Windows itself were locked at 640x480 due to an OS or firmware bug, no reasonable user would go to the vendor of every software application they used demanding that they each develop independent workarounds for this issue. They'd go to Microsoft or their PC manufacturer demanding that they fix for the underlying problem so that ALL of their applications can function as intended. It just so happens that for many users, Reflect is the only application they need to run in WinPE (and possibly Windows Setup, but that works fine in 640x480 because it has a simple UI), so this is the only application where they encounter this issue.
|
By Gork - 10 October 2017 3:42 PM
+xBased on Nick’s answer, if you’re right that this didn’t exist before, has your BIOS revision maybe changed since the last time you tried Rescue Media? ... Maybe try a BIOS update if you haven’t?
The BIOS (UEFI) revision wasn't changed - but again, I can't be sure that the problem didn't exist before. The only thing I can be sure about is that I didn't NOTICE that the problem existed before... :/ I did just update the firmware and there is no change though.
EDIT:
And yeah, I get it - I believe Macrium (and others) have indicated this is not something they will and/or can address, but I just wanted to share that my make/model of laptop is having the same issue. I didn't post necessarily hoping a fix could be offered for the issue.
|
By g.raab - 12 November 2017 4:32 PM
Hi
I'm having the same issue with v7.1.2646 - Windows PE 10 UEFI , Toshiba Qosmia X70
Is there a solution
Thanks, Gerhard
|
By jphughan - 12 November 2017 4:55 PM
+xHi I'm having the same issue with v7.1.2646 - Windows PE 10 UEFI , Toshiba Qosmia X70 Is there a solution Thanks, Gerhard
Hey Gerhard,
Try building with WinPE 5.0 instead. It has basically everything from WinPE 10 except support for unlocking BitLocker volumes that use the newer XTS mode and support for Storage Spaces,which are very uncommon, and some users have found that it works as expected on PCs where WinPE 10 doesn't
|
By g.raab - 12 November 2017 5:13 PM
+x+xHi I'm having the same issue with v7.1.2646 - Windows PE 10 UEFI , Toshiba Qosmia X70 Is there a solution Thanks, Gerhard Hey Gerhard, Try building with WinPE 5.0 instead. It has basically everything from WinPE 10 except support for unlocking BitLocker volumes that use the newer XTS mode and support for Storage Spaces,which are very uncommon, and some users have found that it works as expected on PCs where WinPE 10 doesn't
Hi
Works for me with PE 50.
Thanks
|
By jphughan - 12 November 2017 6:05 PM
Great! In that case whenever Macrium adds support for WinPE 10 1703 (or maybe 1709 by now), that will work for you. There seem to be at least 2 possible causes of the 640x480 lock. One is non-compliant UEFI firmware and another is a bug specific to the 1607 release of WinPE 10, so if your laptop is affected by the latter issue, it may be fixed in a future release.
|
By rasa - 8 January 2018 12:11 AM
+x
The URL http://updates.macrium.com/reflect/utilities/pe/bootx64.efi is 404 (not found)
|
By jphughan - 8 January 2018 1:21 AM
^ PMed you
|
By Nick - 8 January 2018 8:50 AM
+x
Hi, Thanks for pointing this out. It is now available, though this might not help.
|
By bobart - 16 January 2018 11:10 PM
+x
Yeah, I had the same screen resolution problem on a Lenovo Flex 3 and changed PE version and now I just boot from USB if needed (hope I never have to} and choose between Windows and Macrium on the fist menu that comes up - then everything looks fine and restores the image perfectly. Thank you for that suggestion.
|
By jphughan - 16 January 2018 11:24 PM
+xYeah, I had the same screen resolution problem on a Lenovo Flex 3 and changed PE version and now I just boot from USB if needed (hope I never have to} and choose between Windows and Macrium on the fist menu that comes up - then everything looks fine and restores the image perfectly. Thank you for that suggestion.
If you see a choice between Windows and the Reflect Rescue environment, it means you did NOT boot from USB; instead, you booted from the hard drive and you have the boot menu recovery option enabled. If you're seeing that menu even after you believe you booted from USB, then something is wrong with either that USB stick or your system that's preventing booting via that USB stick, in which case I would look into that now rather than when you might really need to boot from USB.
|
By bobart - 16 January 2018 11:43 PM
+x+xYeah, I had the same screen resolution problem on a Lenovo Flex 3 and changed PE version and now I just boot from USB if needed (hope I never have to} and choose between Windows and Macrium on the fist menu that comes up - then everything looks fine and restores the image perfectly. Thank you for that suggestion. If you see a choice between Windows and the Reflect Rescue environment, it means you did NOT boot from USB; instead, you booted from the hard drive and you have the boot menu recovery option enabled. If you're seeing that menu even after you believe you booted from USB, then something is wrong with either that USB stick or your system that's preventing booting via that USB stick, in which case I would look into that now rather than when you might really need to boot from USB.
Okay, I'll look at it again later. Thanks.
|
By bobart - 17 January 2018 10:07 PM
+x+xYeah, I had the same screen resolution problem on a Lenovo Flex 3 and changed PE version and now I just boot from USB if needed (hope I never have to} and choose between Windows and Macrium on the fist menu that comes up - then everything looks fine and restores the image perfectly. Thank you for that suggestion. If you see a choice between Windows and the Reflect Rescue environment, it means you did NOT boot from USB; instead, you booted from the hard drive and you have the boot menu recovery option enabled. If you're seeing that menu even after you believe you booted from USB, then something is wrong with either that USB stick or your system that's preventing booting via that USB stick, in which case I would look into that now rather than when you might really need to boot from USB.
Okay, jphughan, I reloaded the USB with PE version 5.0 and the video driver folder from my hard drive, then removed Reflect from my hard drive (just to be sure) and booted into the USB. It loaded Reflect at the correct screen resolution. I then reinstalled Macrium Reflect to my computer, and, now it should be fine. Thank you for the heads up.
|
By jphughan - 17 January 2018 11:17 PM
Awesome! I didn’t realize Reflect would actually load video drivers in the Rescue environment, in fact I didn’t even realize WinPE allowed user-supplied video drivers. I thought it only used whatever it had built-in. Interesting!
|
By rasa - 16 March 2018 6:17 AM
I thought I fixed it by creating a PE 5 boot stick, but it's now coming up in 640x480. Spent hours to no avail trying everything suggested in this thread. So I have to ask:
Why when I click the "Image this disk" link ,does a "Disk Image" window come up, but then I can't select the buttons by pressing Enter, but instead am required to click the button with the mouse, but then I can't make the window small enough to move the button onto the screen so I can click it?
|
By rasa - 16 March 2018 6:23 AM
And why is the "Disk Image" popup window not shrinkable so the user can make it smaller than 640x480 so the button that must be clicked with a mouse can be made visible? This makes no sense!
|
By rasa - 16 March 2018 6:04 PM
And why does the "Disk Image" popup window not have an Alt-key option to select the [Next] button or the [Finish] button? Other popup windows allow the buttons to be selected by tabbing over to them and pressing enter, but none of the buttons in the "Disk Backup" window do. This can easily be fixed in programming. Please advise if/when these issues will be addressed, as they continue to impact your users.
|
By jphughan - 16 March 2018 6:47 PM
This issue has been in the Rescue section of my "Aggregated quick win features requests" thread (here) for a while. Over there I suggested making the main content portion of the wizard scroll-enabled, which would allow making the overall window size small enough to fit within a 640x480 display area, perhaps with dynamic sizing so that users that have higher resolutions in Rescue don't unnecessarily see a relatively cramped window that requires scrolling when more space is available.
|
By Danskeman - 10 May 2018 9:48 PM
+xThis issue has been in the Rescue section of my "Aggregated quick win features requests" thread ( here) for a while. Over there I suggested making the main content portion of the wizard scroll-enabled, which would allow making the overall window size small enough to fit within a 640x480 display area, perhaps with dynamic sizing so that users that have higher resolutions in Rescue don't unnecessarily see a relatively cramped window that requires scrolling when more space is available.
The next imminent update sorts this issue (on their test machines). Basically they have ported some boot code from an older version of Windows where it did work, and you can optionally select it.
You will also be able to use wifi in next update I believe.
|
By habermehl - 6 June 2018 8:43 PM
For what it's worth, building rescue media with PE 5 fixed the screen resolution issue on my Lenovo X1 Carbon Thinkpad Gen 3 running their current BIOS version N14ET47W (1.25 ).
|
By RefDM - 18 June 2018 9:02 AM
I recently installed and configured a Lenovo Thinkpad X250. When I tested the MR recovery environment after installing, everything was fine. The workstation is scheduled to be deployed to the user next week, so I did some last software updates today, and just to be sure everything was still ok, I also booted up the MR Recovery Environment...
Due to the Lenovo FW bug I had originally built the recovery environment using Windows 8.1 based PE, as recommended. That worked around the screen resolution problem. After testing the RE I had enabled BitLocker on all the disks without realizing that it could cause any problems.
Today I noticed that the Windows 8.1 PE does not support BitLocked in XTS mode (which is nowadays the default mode). So, since I had used BitLocker in XTS mode, I was not able to unlock either the operating system disk or the backup disk any longer in the recovery environment.
So I'm currently in a dead end: With Windows 8.1 PE I get around the screen resolution bug - but cannot unlock BitLocker protected disks due to missing operating system support. On the other hand, with Windows 10 PE I can unlock the disks but cannot perform backups or restores due to the Lenovo FW bug...
I wonder if "the next imminent update" (referred to above in this thread) is expected to be out in the very near future - or should I switch back to the old CBC mode for all the disks in this workstation?
|
By jphughan - 18 June 2018 12:49 PM
I may have a workaround for you, essentially doing manually what the next release does with a checkbox. Let me experiment for a bit and I’ll report back.
|
By jphughan - 18 June 2018 1:15 PM
Ok @RefDM, try doing the following. I'm assuming you're using USB flash drive Rescue Media. If you need to use discs, you'll need to be able to create a bootable ISO from a modified file set, which I can help with if needed.
1. Back up your WinPE 5.0 Rescue Media files somewhere (or generate a new ISO that you can mount and extract files from in Step 3 later).
2. Build new Rescue Media based on WinPE 10.
3. Copy the following files from your WinPE 5 Rescue Media to your WinPE 10 Rescue Media, overwriting the files in the latter:
- \bootmgr.efi
- \EFI\Boot\bootx64.efi
If that fixes your issue, just stash those two files from your WinPE 5 Rescue Media somewhere. That way if you ever need to update your WinPE 10 Rescue Media for some reason in the future, which would overwrite those files with the normal PE 10 versions, you can just copy those two files to your updated Rescue Media again. You would NOT need to also create new WinPE 5 Rescue Media each time there's an update because those two files above do NOT change with new Reflect releases, build selections, etc. They're part of the WinPE 5 environment from Microsoft, which is static.
|
By RefDM - 18 June 2018 5:55 PM
@jphughan, You are my hero! Thank you once again.
Actually not all of the files you listed existed on my rescue media, but I copied the files that did exist, and it indeed did the trick: Now I have a Windows PE 10 based rescue environment with AES-XTS support for BitLocker, together with the workaround for Lenovo firmware bug.
|
By jphughan - 18 June 2018 6:01 PM
Excellent! The list I provided above was admittedly the result of comparing a standard WinRE 10 1803 Rescue Media build to a WinRE 10 1803 build with the same configuration except having the "Legacy EFI" option checked, so I suppose a WinPE 5 build might not have some of those files. Anyhow, glad you've got a workaround in the meantime, and hopefully that "PowerShell not installed" issue you reported elsewhere gets fixed soon as well so that your persistent set numbering works!
|
By jphughan - 18 June 2018 6:14 PM
UPDATE: Upon further investigation, there are fewer files that need to be overwritten. The "normal" build I had been testing with was created a while ago, and when I enabled the Legacy EFI option, the Rescue Media had to be rebuilt from scratch. Since I'm using WinRE rather than WinPE, the Rescue Media gets built from the contents of my Recovery partition, and it appears its contents changed from the time of my older "normal" build, presumably due to Windows updates. I just generated two new builds both from scratch today, and now the only difference that Legacy EFI made was in two files, so I've updated the post above to reflect that. Should be easier in case you need to rebuild your Rescue Media in the meantime.
|