I tried following your instructions as much as possible but it just won't work like your pictures I created a bootable usb window 7 using rufus I created a mount folder (C:\mount) and started DISM++ 64 version I clicked mount image, unchecked the read only box, chose boot.wim on my bootable usb and chose the mount folder I've created It mounts fine and I'm able to click open sesion I clicked "Drivers" but it doesn't show any drivers, but when I checked "Display in-box driver" it shows a lot of drivers I searched for storage controllers and checked "advanced micro devices, inc." box When I tried to click delete it just shows me error "invalid parameter" or something, same thing happened when I tried it again with install.wim
But to clarify, does it crash in PE (installer) when you boot from USB, or installed system booting from HDD?
@reyzafany Maybe integrate 7 doesn't add that driver to boot.wim, which is why dism++ does not show any 3rd party drivers for boot.wim. If it shows ahcix64s.sys in your screenshot, it must have been added to the install.wim. Are you sure you mounted the correct image from install.wim?
Yes, that window only shows third party drivers. The image you mounted has no third party drivers integrated.
Yes I'm able to finish the installation but the second I restarted and choose win7 through windows boot manager I'll still end up stuck at starting windows screen. if I were to use clean win7 iso it will crash at starting windows screen (right before the installer window), when I used @Atak_Snajpera's tool I managed to boot into the installer, install the windows, but still stuck at starting windows if I were to boot the installed windows 7 I'll try mounting the iso to windows and use DISM++ just to check if the drivers show up or not.
So that what you mean, I only managed to install windows till I prompted to restart by the installer. Once I restart the PC and choose Windows 7 in Windows Boot Manager I'll end up stuck at starting windows screen again.
removing those drivers won't help. What you see, is the LAST driver that was SUCCESFULLY loaded. I don't know a way to get to know the failing driver
As he said he's stuck on the logo screen I think the VGA emulator is not loaded correctly. That's why safe mode also gets stuck. If uefiseven or vgashim doesn't work for him, the only way is to install everything using dism, disable standard vga and slipstream a signed and compatible display driver. That was the old way before these 2 int10h emulators were used.
Yes, but at least you can boot the installed win7,even if you get no safe mode, bsod etc. There are many modified driver for the 8th and 9th generation, there is for the moment a high chance you can find one.
I am also having an issue loading windows 7 x64 enterprise using the vgadisable method for a pre setup windows 7 install cloned to the ssd/msata, vgashim or this uefiseven v1.22. I am on a third gen i5 3337u cpu with integrated hd4000 graphics on an acer w700 11.6" touch tablet. This tablet supports 1022x768 in any of the operating systems currently installed as well as in efiseven per the verbose screen output. I have windows 10 enterprise, ubuntu 18.04lts. max osx 10.11 el capitan (fully functional due to natively mac supported hardware and coding some kexts, dsdt, and ssdt files myself for sleep, audio from speaker and hdmi out, as well as wifi, intel speedstep, ssd trim features etc), and android x86 8.1. all booting pure uefi. I have no csm mode. it is either legacy OR uefi, not a mix of both. I cannot boot windows 7 in uefi period on this device and I really need to as windows ten is terrible. This isn't a question of windows 7 video drivers availability as its an older system and drivers for this chipset and integrated video card are readily available. For some reason I cannot upload photos to this site and its really annoying. so on the fat32 formatted usb drive with uefi enabled and security disabled: it loads uefiseven unlocks the memory with EfiLegacyRegionProtocol fills in the vesa information a (c000:0200) locks the memory with EfiLegacyRegionProtocol and @ c0000 and says: unable to claim IVT area @ 0000 INT10h IVT entry could not be modified and currently pointing at wrong memory area (0000:0000 instead of c000:0200) press enter int10h ivt entry points at location (0000:0000) outside vga rom memory area (c0000.D0000) rejecting handler pre-boot int10h sanity check failed press enter found simple file system protocol opening volume opened file '\efi\boot\bootx64.original.efi' for reading found windows boot manager at '\efi\boot\bootx64.original.efi' address behind fileimagehandler=737c3d18 file matches an efi loader signature press enter then it freezes at windows logo only thing i note different than reyzafany is that his efiseven is using EfiLegacyRegion2Protocol not EfiLegacyRegionProtocol. any help being able to attachs pics in here, edit bcd and regsistry on usb drive to disable vga to try that method, or getting efiseven to work would be greatly appreciated been at this for a while now.
Here is the problem. It refuses to install the int 10h emulator, so system will crash when int 10h is called. A bit of guesswork on my side, but it looks like the "unable to claim IVT area" is where it fails, and the remaining errors are because it tries to access wrong memory range. Unfortunately fixing this is above my pay grade.
i would assume that manatails could change the memory area the vga emulator is looking for. It doesnt seem like it would be that difficult but then again i haven't looked at the source code to try to figure it out and maybe it goes deeper than just changing a memory address. I really dont have that kinda time to devote to getting that in depth right now so I'm hoping someone can help me out.
can you try this build and check if it makes any difference for you? --test build deleted. Use 1.23 from the git repo--
Hi there. I tried their solution and it still doesn't work. I guess there must be some other reasons that I cannot boot into Windows 7. I guess one reason might be the storage system. My Mini PC uses eMMC as storage media which might not be supported by Windows 7. So I finally decided to use Windows Embedded 8.1 Industry Pro. It also costs little memory (500 MB) and lower disk space (7 GB). Since this version of Windows 8.1 has full UEFI supports and such low costs, I think my problem solved. Thanks for your help and the amazing work of UefiSeven! In case there is someone who has a similar situation like mine: Everyone can get a free copy of Windows Embedded 8.1 Industry Pro from Microsoft website for 180 days.