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.

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.

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

Sorry, i personality think thats no acceptable solution.

I'll try that fix & report back.

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.

OK, tried Nick's fix & tested the USB - same resolution problem.

Hehe.... :-(

So Macrium investigate the Problem!

I am not the only person with the problems, you also Basket.

Please fix the issue!

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.

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.