Comment 12 for bug 1366546

Windows 8 does and it seems to be bootmgfw.efi as it looks on my laptop (it has 3 drives, 1 HDD for Windows, 1 HDD for Ubuntu LTS and Fedora, 1 SSD for the latest Ubuntu, all UEFI):

livewire@za21:~$ unset LANG
livewire@za21:~$ mount | grep ^/dev
/dev/sdb3 on / type ext4 (rw,errors=remount-ro)
/dev/sdb1 on /boot/efi type vfat (rw)
/dev/sdd1 on /media/livewire/SANDISK type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sda1 on /mnt/test type vfat (rw)
/dev/sda2 on /media/livewire/Windows 8 T530 type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
livewire@za21:~$ grep -v microsoft -U /mnt/test/EFI/Boot/bootx64.efi
Binary file /mnt/test/EFI/Boot/bootx64.efi matches
livewire@za21:~$ md5sum /mnt/test/EFI/Boot/bootx64.efi
bad97e7203aec2bd026403a7f70688b9 /mnt/test/EFI/Boot/bootx64.efi
livewire@za21:~$ md5sum /media/livewire/Windows\ 8\ T530/Windows/Boot/EFI/bootmgfw.efi
bad97e7203aec2bd026403a7f70688b9 /media/livewire/Windows 8 T530/Windows/Boot/EFI/bootmgfw.efi

I don't want to screw around with NVRAM on that machine, but I recorded a video on another machine:
https://dl.dropboxusercontent.com/u/15877132/w8_bcdboot_bootx64.mkv

It's only 504,2kB in size (30 fps desktop capture with vlc, no audio and nothing else particularly fancy).

I mounted the ESP with `mountvol b: /s` in Windows, renamed the existing bootx64.efi and ran bcdboot, which created a new ~1.5 MB bootx64.efi-file. Unfortunately, this being another machine (another disk/partition layout or another license/edition) the hashes don't match.

Also my experience from previously mentioned case is that manufacturers put a customized Windows loader in that location which tries to blend POST and Windows boot phase together by displaying the same company logo the whole time (probably to give the impression of a faster startup).