@Arrowhead-IT
Obviously, you’ll have to adjust paths.

1. Install windows ADK
2. Launch Deployment and Imaging Tools Environment (basically a glorified cmd prompt). I always run this as administrator, but I’m not sure it’s required here.
   a. mkdir c:\temp\winpe
   b. copyxpe x86 c:\temp\winpe\x86
3. (Optional) Add drivers as per https://technet.microsoft.com/en-us/library/hh825070.aspx
   a. dism /Mount-Image /ImageFile:c:\temp\winpe\x86\media\sources\boot.wim /index:1 /MountDir:C:\temp\winpe\x86\mount
   b. dism /Image:C:\temp\winpe\x86\mount /Add-Driver /Driver:d:\share\winpe10.0-Drivers-A01-6XFM6\winpe\x86 /recurse
   c. dism /Unmount-Image /mountdir:C:\temp\winpe\x86\mount /commit
4. Delete bootfix.bin (to get rid of the ‘press any key’ prompt)
   a. del c:\temp\winpe\x86\media\Boot\bootfix.bin
5. Create ISO
   a. MakeWinPEMedia /ISO c:\temp\winpe\x86 c:\temp\winpe_x86.iso
6. Copy the ISO to the FOG server so we can access it via http
   a. mkdir /var/www/html/winpe-build2
   b. cp /mnt/myshare/winpe_x86.iso /var/www/html/winpe-build2/winpe_x86.iso
7. Create a new menu item from the FOG UI Fog Configuration->iPXE New Menu Entry
   a. Parameters:

initrd http://${fog-ip}/winpe-build2/winpe.iso   
chain memdisk iso raw
boot || MENU

Like:

8. Test

@Sebastian-Roth I decided to try to figure out how to add a WinPE option on the menu, and after I got that working (using an ISO, not wimboot btw), I noticed that boot from hard disk started working again.

I’ll see if I can repro the original bug tomorrow morning.

I tried to reproduce this with 5686, and the boot menu looks fine, so I’d call it fixed . For anybody who’s seeing this issue, I’d recommend just changing anything in the iPXE Boot Menu, saving it and changing it back.

Now, to mark this as solved…