Setting up E2B on a Surface Pro 7 Tablet
Hello,
I have been trying to set up an Easy2Boot drive using my new Surface Pro 7 Tablet over the past week. I have followed all of the procedures I have seen for using UEFI booting from a USB drive, disabling secure boot, changing the priority list in settings. I have confirmed that both of the two USB drives I've flashed are working after testing them with a laptop running Windows 10. Both have E2B on Partition 1 and agFM on Partition 2 (set up as FAT32). I've seen some information online that says Surface products have compatibility issues with BIOS, only opening UEFI. I have ran the Easy2Boot QEMU_MENU_TEST and it will run alright on the tablet, when I try turning on the tablet and booting from the USB it stays locked on the bootup screen, never completing.
Has anyone here had experience using Easy2Boot on a Surface tablet that could steer me in the right direction?
Thanks,
Nick
Hi
So is the Surface Pro 7 a UEFI64 system or UEFI32?
Both should work.
If it says 'locked' then maybe Secure Boot is not disabled or possibly the Kaspersky EFI boot file is blacklisted in the BIOS.
Why not disable the Kaspersky Secure Boot shim (menu item in the E2B Main Menu) using QEMU and try it?
Make sure you don't use the 'disable UEFI booting' menu item by mistake!
Steve
Hello,
My Surface is a UEFI64 system. Sorry, I just realized saying locked was incorrect there. I meant that the device gets stuck in bootup and cannot progress. I have the red bar with an unlocked padlock displaying across the top during bootup and my UEFI settings are set to disable secure boot.
I just tried disabling the Kaspersky Secure Boot Shim while in the E2B Main Menu using QEMU like you mentioned but it returns "FAT Error: (2) Assertion Failed" each time I try. I've tried it also in agFM but when I do that the screen turns black for a short while then returns to the main menu without showing what may have happened.
Thanks,
Nick
try Legacy booting on another machine to disable Kaspersky shim.
Thank you very much, this solved the problem right away