[DISCUSSION] Windows 11 Build 26100 (PC) [24H2 Retail- GE-release]

Thank you but i do not know which esd is the ref esd too. Any body knows exact wimlib-imagex or wimexport command with -ref switch and ref esd file name?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thank tou so much. Genious

 

when disabling the check TPM and SecureBoot on build 24H2 - FOR %%A IN (TPM SecureBoot) DO Reg Add HKLM\SSYSTEM\Setup\LabConfig /v Bypass%%ACheck /t REG_DWORD /d 1 /f

I get an installation error.

before the release 24H2 it worked perfectly.
have to use installer from 23H2

 

2024 LTSC IoT has no TPM/CPU-Restrichtions at all -- all others have .

Admin CMD:

Code:

wsreset -i

wait a moment, store appears. Is normal Ent then.

 

@Enthousiast sorry for disturbing, but for the best of my old brain, i can't remember the complete 'old' name of the uup dump creator, before he changed it to that whatever**.

Would be nice if you cou could post or PM me ... my brain ist rotating ... but ...

 

Are the lockscreen cards enabled for 24h2 rp ?

 

Is there a way to change edition of Windows 11 23h2 Iot to IOT LTSC?
Thanks beforehand

 

no, try to perform in-place upgrade to the ltsc edition, if it's blocked then you need to edit upgrade matrix

 

Thanks for your answer, when you say upgrade matrix, you mean the ISO?

 

If you can't upgrade because of upgrade matrix then you should edit it in your installation media
Edited matrix with the script is pinned on uup dump discord server, no idea where it is located on this forum

Upgrade matrix location is
\Windows\servicing\Editions\UpgradeMatrix.xml

 

Isn't it easier to modify the value of HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionID to EnterpriseS or IoTEnterpriseS and then try again doing the in-place upgrade?

 

Both ways are easy enough, registry edit was working fine before, didn't tested it with build 26100

 

I did it works on build 26100

 

@Enthousiast please check pm .

 

anyone have a problem installing 26100.1301 through windows update from 26100.1150?