@manatails I tested it on ASUS P8H61-M LE R2 + PCIe AMD HD7450 (ROM legacy+GOP) with WinXP SP2 64-bit UEFI and it works OK UEFI_CSM_U7_forced.log - Overwriting int10h handler with fakevesa... : Spoiler Code: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.06 09:41:50 =~=~=~=~=~=~=~=~=~=~=~= fs0:\EFI\Boot> bootx64 UefiMain UefiSeven 1.24 UefiMain You are running in verbose mode, press Enter to continue Initialize Found a GOP display adapter SwitchVide Set mode 3 with desired 1024x768 resolution. PrintVideo Current mode: PrintVideo HorizontalResolution = 1024 PrintVideo VerticalResolution = 768 PrintVideo PixelFormat = 1 PrintVideo PixelsPerScanLine = 1024 PrintVideo FrameBufferBase = E0000000 PrintVideo FrameBufferSize = 3145728 PrintVideo Available modes (MaxMode = 6): PrintVideo Mode0: 720x400 PrintVideo Mode1: 640x480 PrintVideo Mode2: 800x600 PrintVideo Mode3: 1024x768 PrintVideo Mode4: 1280x1024 PrintVideo Mode5: 1600x1200 UefiMain Overwriting int10h handler with fakevesa... EnsureMemo Success unlocking memory at C0000 with EfiLegacyRegionProtocol UefiMain VESA information filled in, Int10h handler address=C0200 (C000:0200) EnsureMemo Success locking memory at C0000 with EfiLegacyRegionProtocol UefiMain Int10h IVT entry modified to point at C000:0200 IsInt10hHa Int10h IVT entry points at location within VGA ROM memory area (C000:0200) IsInt10hHa First Int10h handler instruction at C000:0200 (3D) valid, accepting handler UefiMain Pre-boot Int10h sanity check success FileExists Found simple file system protocol FileExists Opened volume FileExists Opened file '\EFI\Boot\bootx64.original.efi' for reading UefiMain Found Windows Boot Manager at '\EFI\Boot\bootx64.original.efi' Launch Loaded 'PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,MBR,0x6391A633,0x800,0x32000)/\EFI\Boot\bootx64.original.efi' Launch Addresss behind FileImageHandle=6FCF0B98 Launch File matches an EFI loader signature WaitForEnt Press Enter to continue UEFI_pure_U7_forced.log - Overwriting int10h handler with fakevesa... : Spoiler Code: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.06 09:45:22 =~=~=~=~=~=~=~=~=~=~=~= fs0:\EFI\Boot> bootx64 UefiMain UefiSeven 1.24 UefiMain You are running in verbose mode, press Enter to continue Initialize Found a GOP display adapter SwitchVide Set mode 4 with desired 1024x768 resolution. PrintVideo Current mode: PrintVideo HorizontalResolution = 1024 PrintVideo VerticalResolution = 768 PrintVideo PixelFormat = 1 PrintVideo PixelsPerScanLine = 1024 PrintVideo FrameBufferBase = E0000000 PrintVideo FrameBufferSize = 3145728 PrintVideo Available modes (MaxMode = 12): PrintVideo Mode0: 2560x1440 PrintVideo Mode1: 1280x960 PrintVideo Mode2: 640x480 PrintVideo Mode3: 800x600 PrintVideo Mode4: 1024x768 PrintVideo Mode5: 1280x1024 PrintVideo Mode6: 1400x1050 PrintVideo Mode7: 1600x1200 PrintVideo Mode8: 1792x1344 PrintVideo Mode9: 1856x1392 PrintVideo Mode10: 1920x1440 PrintVideo Mode11: 1152x864 UefiMain Overwriting int10h handler with fakevesa... EnsureMemo Success unlocking memory at C0000 with EfiLegacyRegionProtocol UefiMain VESA information filled in, Int10h handler address=C0200 (C000:0200) EnsureMemo Success locking memory at C0000 with EfiLegacyRegionProtocol UefiMain Int10h IVT entry modified to point at C000:0200 IsInt10hHa Int10h IVT entry points at location within VGA ROM memory area (C000:0200) IsInt10hHa First Int10h handler instruction at C000:0200 (3D) valid, accepting handler UefiMain Pre-boot Int10h sanity check success FileExists Found simple file system protocol FileExists Opened volume FileExists Opened file '\EFI\Boot\bootx64.original.efi' for reading UefiMain Found Windows Boot Manager at '\EFI\Boot\bootx64.original.efi' Launch Loaded 'PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,MBR,0x6391A633,0x800,0x32000)/\EFI\Boot\bootx64.original.efi' Launch Addresss behind FileImageHandle=79278418 Launch File matches an EFI loader signature WaitForEnt Press Enter to continue UEFI_CSM_U7_normal.log - Int10h already has a handler, no further action required: Spoiler Code: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.06 09:36:09 =~=~=~=~=~=~=~=~=~=~=~= fs0:\EFI\Boot> bootx64 UefiMain UefiSeven 1.24 UefiMain You are running in verbose mode, press Enter to continue Initialize Found a GOP display adapter SwitchVide Set mode 3 with desired 1024x768 resolution. PrintVideo Current mode: PrintVideo HorizontalResolution = 1024 PrintVideo VerticalResolution = 768 PrintVideo PixelFormat = 1 PrintVideo PixelsPerScanLine = 1024 PrintVideo FrameBufferBase = E0000000 PrintVideo FrameBufferSize = 3145728 PrintVideo Available modes (MaxMode = 6): PrintVideo Mode0: 720x400 PrintVideo Mode1: 640x480 PrintVideo Mode2: 800x600 PrintVideo Mode3: 1024x768 PrintVideo Mode4: 1280x1024 PrintVideo Mode5: 1600x1200 IsInt10hHa Int10h IVT entry points at location within VGA ROM memory area (C000:040E) IsInt10hHa First Int10h handler instruction at C000:040E (E8) valid, accepting handler UefiMain Int10h already has a handler, no further action required FileExists Found simple file system protocol FileExists Opened volume FileExists Opened file '\EFI\Boot\bootx64.original.efi' for reading UefiMain Found Windows Boot Manager at '\EFI\Boot\bootx64.original.efi' Launch Loaded 'PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,MBR,0x6391A633,0x800,0x32000)/\EFI\Boot\bootx64.original.efi' Launch Addresss behind FileImageHandle=6FCF0B98 Launch File matches an EFI loader signature WaitForEnt Press Enter to continue UEFI_pure_U7_normal.log - Int10h IVT entry points at location (9000:0000) outside VGA ROM memory area (C0000..D0000), rejecting handler: Spoiler Code: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.06 09:47:55 =~=~=~=~=~=~=~=~=~=~=~= fs0:\EFI\Boot> bootx64 UefiMain UefiSeven 1.24 UefiMain You are running in verbose mode, press Enter to continue Initialize Found a GOP display adapter SwitchVide Set mode 4 with desired 1024x768 resolution. PrintVideo Current mode: PrintVideo HorizontalResolution = 1024 PrintVideo VerticalResolution = 768 PrintVideo PixelFormat = 1 PrintVideo PixelsPerScanLine = 1024 PrintVideo FrameBufferBase = E0000000 PrintVideo FrameBufferSize = 3145728 PrintVideo Available modes (MaxMode = 12): PrintVideo Mode0: 2560x1440 PrintVideo Mode1: 1280x960 PrintVideo Mode2: 640x480 PrintVideo Mode3: 800x600 PrintVideo Mode4: 1024x768 PrintVideo Mode5: 1280x1024 PrintVideo Mode6: 1400x1050 PrintVideo Mode7: 1600x1200 PrintVideo Mode8: 1792x1344 PrintVideo Mode9: 1856x1392 PrintVideo Mode10: 1920x1440 PrintVideo Mode11: 1152x864 IsInt10hHa Int10h IVT entry points at location (9000:0000) outside VGA ROM memory area (C0000..D0000), rejecting handler EnsureMemo Success unlocking memory at C0000 with EfiLegacyRegionProtocol UefiMain VESA information filled in, Int10h handler address=C0200 (C000:0200) EnsureMemo Success locking memory at C0000 with EfiLegacyRegionProtocol UefiMain Int10h IVT entry modified to point at C000:0200 IsInt10hHa Int10h IVT entry points at location within VGA ROM memory area (C000:0200) IsInt10hHa First Int10h handler instruction at C000:0200 (3D) valid, accepting handler UefiMain Pre-boot Int10h sanity check success FileExists Found simple file system protocol FileExists Opened volume FileExists Opened file '\EFI\Boot\bootx64.original.efi' for reading UefiMain Found Windows Boot Manager at '\EFI\Boot\bootx64.original.efi' Launch Loaded 'PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,MBR,0x6391A633,0x800,0x32000)/\EFI\Boot\bootx64.original.efi' Launch Addresss behind FileImageHandle=79278498 Launch File matches an EFI loader signature WaitForEnt Press Enter to continue
Thank you for the detailed report, new build has been released to github. p.s. you don't have to update it, it is the same binary I uploaded yesterday
Rename bootmgfw.efi at (HDD)\EFI\Microsoft\Boot\ to bootmgfw.original.efi Copy UefiSeven bootx64.efi to (HDD)\EFI\Microsoft\Boot\bootmgfw.efi using EFI shell How do I do that, exactly? There's no EFI file in my C: drive even with hidden files on, and I have no access to EFI shell, my UEFI just says "not found". Am I out of luck with this workaround? I used Integrate7 for the initial .iso. Update: I've seriously no idea what I'm doing wrong. I create a proper Windows 7 iso using Integrate7 and I then flash it on an USB using Rufus. I change out the boot file as shown on the tutorial and add ".original" to the old one on the boot USB. I install as normal, but then Windows gives me that 10 second reboot prompt. Here I completely shut off the PC, turn it on again and boot into a Linux live environment through the BIOS. There I look at the Windows files and there's still no EFI folder in C: disc. What gives? There's a /Boot/EFI directory in the "Windows" system file folder, and there I find the files that the guide asks me to change. I do that and nope, still nothing. Windows locks up on the registry configuration with the boot animation, and pressing Enter simply restarts the whole computer and here we go again, a loop.. Update 2: exact same process, with enough waiting it configured the registry. Now it's just stuck on "Starting Windows" animation with the full flag formed.... guess I'll just stay with CSM mode, this UefiSeven doesn't work at all for me
@manatails I have a Z390 Aorus Master, F6 factory firmware. It provides CSM and I'm running EFI 7x64 on it. However I was not able to boot OS when CSM was disabled, not even with a working OEM driver installed and legacy VGA native drivers/services disabled. UefiSeven allows me to boot with CSM disabled. This is the purpose of your tool and it worked for me, so good job. What I've found however is that, contrary to Gelip, I cannot boot OS via UefiSeven when CSM is enabled. Execution seems to hang after displaying the following messages: Code: UefiMain UefiSeven 1.24 UefiMain You are running in verbose mode, press Enter to continue Initialize Found a GOP display adapter According to super nice Gelip logs, the "SwitchVide" should follow, but it doesn't. I've tried both normal and force_fakevesa runs. @Gelip Could you describe your PuTTY setup to capture those logs?
I wanted to thank you @manatails for this tool ! I'm now able to fully install and boot Win7 on UEFI Class 3 ! GOP was driving me crazy until I found out about UEFISeven !
Windows Install Boots, but it hangs saying "A required CD/DVD drive device driver is missing" Unusual as it's on an HP Laptop with no optical drive at all! Pic of Error: drive.google.com/file/d/1--0UmMBlt73i-_n6xvwIpNM3cEyd_KsC/view?usp=sharing
@manatails Thanks for your great work. Would be possible to implement replacement of ACPI tables? This would allows us to fix compatibility issues by using customized tables.
If you are trying to install Windows 7 to MMC/eMMC then there are no drivers for it, so it's imposible.
what kind of graphics card are you using? it depends if you were able to integrate the latest graphics drivers onto a custom win7 install media
Sorry to bother you. I've been following this thread for some time. Now a friend of mine has an Asus Transformer Book T100HA for me to fix/reinstall. Alas, this only uses UEFI (without Int10/legacy option) and came with Win10 pre-installed. The original installation was pretty much ruined - buggy, slackware and very slow - and while a Win10 re-installation improved the situation somewhat it now has several issues due to old/wrong drivers (which is common with the T100HA according to the Asus Transformer-Forum). Some version of Linux is also possible - as well as Windows 8/8.1, but nobody really likes the latter option. Now before I get into the nitty gritty of trying to install Win7 (with your and/or Manatail's help) my question to the experts would be, is it worth the time or should I better try to get better drivers for Win10? Thank you!
You might read the thread more carefully and discover that it is not possible to install Windows 7 on eMMC storage which your device is running. So it is better to search for drivers.
Ah, ok. I wasn't aware that this was a serious issue. And there's (still) no driver for it that could be slipstreamed into the Win7-install?
Sadly but nope. Lools like this is rare case when someone need to mess with win7 on it. If only your pc wolud have SATA interfaces then no problem.
Yeah, I've heard that before. One of the problems with the T100HA also is that it's first and foremost a windows tablet (with a dock) and not a notebook/netbook. And even with properly installed Win10-drivers the dock causes issues. Too bad, because it's a neat little package and of good quality. But not under Win8/8.1 or 10. 4GB of RAM are simply not enough to begin with and I'm really not into Win10 to say the least. This is one case which you should send over to manatails himself and see what he can do. I'm sure there are more people with similar devices who would love to tell Asus and Win10 to shove it. (I remember a 50+ pages thread - in Italian - of how to install Windows XP (with all special function keys working) onto a Sony notebook designated "only" for Vista and above. You had to read/translate EVERY single page to the very end because some procedures would be improved and/or had to be rolled back. There was no summary at the end. BUT it actually would do what it was supposed to.)
Why I got this error? P.S. I'm using VirtualBox Spoiler EnsureMenu Unable to find a way to unlock memory at C0000. Proceeding without un locking... UefiMain Unable to unlock VGA ROM memory at C0000, aborting How to fix this error?
But only don't need if you on Legacy, I want to boot in VirtualBox's UEFI, and also i have Acer Aspire A114-31, which also throws this aforementioned error