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.

+x

 

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.

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.

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 ).

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?

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.

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.

@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.

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!

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.