I have another question...sorry for my ignorance... Does XP2ESD v1.6 Allow?: -Run on older computers (such as PCs with processors without SSE2 Support) -Run without the classic problem presented in v1.4 which is the "reserved partition" problem, "HAL error", etc. -Support with SATA drivers? I ask this question because I would like to create an iso with support for old computers and not so old computers that do have support greater than SSE2 I appreciate your answer and thanks for this tool
Don't include Embedded Update Packs in that case, this have nothing to do with XP2ESD, it's just how MS decided to do it with some newer Embedded updates. If you use supported base/engine ISO you will never encounter this And if you use unsupported, can be easily added as supported (must be reported which Windows 10 build was used). As XP2ESD use hacked diskpart MUIs to support all languages output in English, then partition is safely removed without issues. There was needed some touch during development (mainly for Windows 10 21Hx or newer), but it was solved long time ago before 1.6 release And missing HAL, you can easily simulate it. If you set different partition ID in POWIS Launcher. For example I will set it as 2 and install on 1. Now you encounter "classic" HAL missing problem. In 99% cases in 1.4 it was caused by this (user installed on 2 even there was written limit in first post it must be 1). Thats why this option was added. And of course it was added to support dualboot with newer systems. Now you can install for example Windows 10 on partition 1, Windows 7 on partition 2, then XP to partition 3 and you will have automatically rebuilded bootloader with all three systems after XP2ESD install finish it's job
wow not bad... thanks... does booting windows 10 21h2 19044 build 1165 work? It is the iso that I have most current at the moment
You can check it with 7z. Just inspect boot.wim. Code: (You can use Windows 8.0 / 8.1 / 10 [1507 (10240) 1607 (14393) 1809 (17763) 2004 (19041) ]) Code: Win10_21H2_English_x32.iso\sources\boot.wim\2\Windows\servicing\Version\10.0.19041.1220\ Code: if exist "%TEMP%\boot\Windows\servicing\Version\6.1*" set LPVER=7 if exist "%TEMP%\boot\Windows\servicing\Version\6.2*" set LPVER=8 if exist "%TEMP%\boot\Windows\servicing\Version\6.3*" set LPVER=81 if exist "%TEMP%\boot\Windows\servicing\Version\10*10240*" set LPVER=10\1507 if exist "%TEMP%\boot\Windows\servicing\Version\10*14393*" set LPVER=10\1607 if exist "%TEMP%\boot\Windows\servicing\Version\10*17763*" set LPVER=10\1809 if exist "%TEMP%\boot\Windows\servicing\Version\10*19041*" set LPVER=10\2004 If it match current servicing pattern, then it can work. If not and there exist official ISO, link me it and I can add it (of course, there must be WinPE packages available too).
this was what i got from the iso with 7zip in the boot.wim 19044.1165.210806-1742.21H2_RELEASE_SVC_REFRESH_CLIENTPRO_OEMRET_X86FRE_ES-ES.ISO\sources\boot.wim\1\Windows\servicing\Version\ 10.0.19041.1161
@George King Hi, I haven't tested it yet. Someone successfully generated the Chinese version of ISO according to the tutorial.（only windows xp sp3 vl). It works well under the virtual machine. I have an old laptop.It natively supports winxp and win7.I don't think it's useful for testing.I wonder if it can work on 700 series motherboards?Does this mean that the 12th generation processor is supported? EDIT:Working OS:Windows 11 ISOs:Windows XP（zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-74070.iso cn_windows_7_professional_with_sp1_vl_build_x86_dvd_u_677939.iso The latest version of Windows 10 Pro 21H2 x86 Besides, I'm sorry about my English.
@jiafei2427 You need to try it on 12 gen CPU Let ke know if you got any BSOD. Our default ACPI is compiled one from leaked and modded sources. And as bonus I applied standard A5+A3 BSOD hacks to suppress well know errors (hopefuly not needed, but just for sure)
@George King @daniel_k I have tried to backport I2C HID Miniport driver from windows 8 (NT 6.2) in order to work on Windows XP/Vista/7 using the ntoskrn8.sys and WppRec8.sys files but every time I try to start the driver from boot automatically (at services it is set to boot=2) I get 0x7E BSOD when booting after pressing F8 to disable driver signature enforcement on Windows 7 on real hardware. My laptop's touchpad driver uses I2C HID Miniport in order to work. Without this driver, the touchpad doesn't work and I have to rely on plugging a USB desktop mouse on the laptop to use windows 7. The driver is not compatible with versions of Windows older than Windows 8 (nt 6.2) so I have to backport this to Windows Xp/7/Vista using your ntoskrnl emu extender files. On Dependency Walker, there are no missing dependencies so I wonder what it's missing that needed to be done in order for this driver to work. I have heard that security_cookie needs to be refreshed but I don't know how to do that in CFF Explorer, so may you please have a screen capture showing me how to refresh security_cookie on driver files? I uploaded the backported hidi2c.sys custom driver I made so you can test this driver on a laptop with I2C HID TouchPad. The hardware ID is ACPI\PNP0c50 or PNP0c50 which depends on Intel(R) Serial IO I2C Host Controller -9DE9 (PCI\VEN_8086&DEV_9DE9&REV_30) to be used in order for the mouse driver to even show in the device manager.
19044 is fake but 20348 (sever2022) is not, should be taken in account given how easy is to use server 2022 as a client system (as is or properly switching it to client)
I tried to apply my installer hacks to Windows 11, but it doesn't work. I think Server 2022 should have same problem. I'm not talking about suppressing TPM and other stupid installers limit, but about many other patches that must be applied to installer.