Group: Forum Members
Rescue Media Builder to my knowledge does not create partitions when you use the recovery boot menu option. It can create partitions on flash drives if needed, but not to my knowledge on internal drives. I'm not sure how your recovery boot menu files ended up over there, or even how that partition came into existence.
I wouldn't recommend deleting the Windows Recovery partition, because the recovery boot menu option in Reflect will absolutely NOT recreate that. In fact if you delete the Windows Recovery partition, you won't be able to build Rescue Media using WinRE anymore (at least until a Windows 10 feature update makes you a new Recovery partition) because the WinRE option uses the Windows Recovery WIM file as its baseline. But you can always delete Reflect's files because Reflect will rebuild them if needed. They're just the file set for Rescue Media, but the "raw" files from which it assembles a Rescue Media build come from the WinRE partition (or WinPE files located in its ProgramData folder if you build with WinPE instead).
The default build option is Windows RE, not PE. And the download option is PE, not RE. You seem to have gotten those mixed up. As I mentioned above, using WinRE causes Reflect to use the Windows Recovery files that are already on your system. That saves you having to download anything and also means that you'll be building with the same Windows kernel that your main OS uses. WinPE can be used to build with a specific Windows PE kernel. This can be necessary if you're building Rescue Media to be used on other systems that might require an older or newer Windows kernel than you're using on the system from which you're building Rescue Media. If you choose WinPE 10, Reflect currently will download WinPE 10 1709, regardless of which Win10 release you're running. In general, sticking with WinRE makes sense, but there have been times for example when Microsoft's new Win10 release (and therefore its new WinRE release) contain bugs. The initial release of Win10 1809 for example had a bug that broke Rescue Media's automatic driver loading at startup. In those cases, staying current isn't necessarily a good thing, because people who used WinRE-based Rescue Media found that their Rescue Media broke after updating Win10. And even apart from that, the WinRE environment gets customized on a per-system basis. By comparison, using WinPE 10 as I said always uses WinPE 10 1709 (for now, anyway), and it does NOT get customized on a per-system basis before Reflect uses it. Sometimes there's something to be said for using a stable, Macrium-tested "foundation" rather than the latest and (allegedly) greatest that gets customized per-system. I personally use WinPE 10, because there's nothing in any newer WinPE/RE 10 kernels that I need in my Rescue Media. HOWEVER, if you need WiFi support in your Rescue Media, you have to use WinRE. As for drivers, Rescue Media Builder should take care of any drivers you need. But of course verify that by testing that your Rescue Media works properly with all hardware you'd need it to use.