Please tell me how I can use the lock screen window recommendation background when I log in from 24h226100 LTSC. There are a lot of Windows repack masters here, but I don't have a solution to this one. I'm curious and want to solve it. Please help
Hello guys, Since the last update none of the isos I produce work. I use the mvs ltsc 26100.1742 (fr-FR) version as a base to build the iot ltsc 26100.2033 (fr-FR), I also use the latest W10UI 10.47. As soon as I boot I receive this message: "install driver to show hardware". I am stuck. Can someone help me? Thanks PS: I use virtualbox 7.1.2 to test my isos in VM
Hi Guys, i downloaded the "en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814" from the 1st page, copied it to USB stick via Rufus, and the stick boots from the BIOS, but the OS doesn't load up to install, and the laptop restarts and opens the already installed windows 10 iot ltsc OS. This had happened with the 1st ISO u guys had put up too the OEM one, and i thought maybe thats a non bootable one. But Rufus would make it bootable anyway isn't it. Tried the upgrade method too, and it didn't install stating some msg about Boot which i cant remember now. Its an old laptop but upto now never had any problems doing a clean install after using Murphy's script. But for windows 11 iot ltsc, someone on this forum had said it doesnt do any TPM check or secure boot chk. Any ideas what i maybe doing wrong?? P.S Laptop is legacy BIOS so i copied in Rufus on MBR mode.
it could be related to boot.wim, sources folder and different setup.exe someone just needs to test this properly recommended steps: 1. use W10UI, update only regular Enterprise LTSC with full updates set 2. use create_virtual_editions.cmd to create IoT Enterprise LTSC, you can also config it to remove Enterprise LTSC you need full sse 4.2 support, check your CPU
Thanks mate. Do i check that through cpuZ? And if the laptop doesnt have that support, why windows 10 iot ltsc installed? Doesn't windows 10 need this requirement? Update: Yes it doesnt show up on cpuZ, So does that mean i can't install any windows 11 OS?
SSE 4.2 requirements have been added since build 26080, so you cannot install 26100 on your system if you want to install any Windows 11, then try 22631
I have been searching about the SFC /Scannow bug and apparently according to one User the error occurs with the cumulative update for Windows 11 Version 24H2 for x64 based systems (KB5043178) he says that once uninstalled the problem is fixed