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

You need to login to view this posts content.

 

I have a 13 years old Asus laptop; I created an ISO with uupdump and applied Win 11 Boot And Upgrade FiX KiT

 

You need to login to view this posts content.

 

Regular have tpm limitation and more

 

You need to login to view this posts content.

 

Should there be a 26100 and 26120 thread then?

 

Can you give more details on how you see incompability
Cause I definitely can install 26100 CUs on 26120 machine.
And If I install enablement, I get 26120, right?

 

https://forums.mydigitallife.net/posts/1807795/
https://forums.mydigitallife.net/posts/1763564/
https://forums.mydigitallife.net/posts/1764510/
https://forums.mydigitallife.net/posts/1758215/

you did not use 22H2/23H2? it's the same debate / situation

enablement package itself does not affect LCU installation, it only affect what WU offer for you
if you installed it on e.g. non-insider 26100.1000, WU will not offer 26100.1150 on patch tuesday
you need to enroll to Dev channel to get 26120.1252, and its installation might fail

 

26100 is my first production W11 system, so am newbie in some questions.

I have installed the leaked 26100.1 LTSC when it arrived. Later I added EP, so got something 26120.x
When LCU 1000 and 1150 appeared, I installed them both.
Now I have 26120.1150:

Code:

Edition    Windows 11 IoT Enterprise LTSC
Version    24H2
Installed on    ‎19.‎04.‎2024
OS Build    26120.1150
Experience    Windows Feature Experience Pack 1000.26100.6.0

It is 26120, but still not Beta?
1152 update fails:

Code:

Windows11.0-KB5038603-x64.msu

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.1150

Processing 1 of 1 -
[==========================100.0%==========================]
[===========================73.0%==========                ] An error occurred - D:\10.0.26120.1152\UUPs\Windows11.0-KB5038603-x64.msu Error: 0x800f081f

Error: 0x800f081f

DISM failed. No operation was performed.

My HKLM\\SOFTWARE\Microsoft\Windows NT\CurrentVersion\BuildLabEx says "26100.1.amd64fre.ge_release.240331-1435"
That means, I can't update to CUs of ge_release_svc_betaflt_upr right?

And if I install ge_release_svc_betaflt_upr full OS or LCU from UUP, I won't be able to install LCUs from ge_release_svc_prod1 anymore?

Thanks!

 

And second question on beta builds, if you can help me to understand it
What would be a difference in installed 26100.1150 vs 26120.1150
As I see it now, the EP, made my 26100 show 26120 doesn't affect system seriously. And it won't update to new branch itself.

And where to find, what are the new features of 26120.1152 (ge_release_svc_betaflt_upr) comparing to 26120.1150 (ge_release_svc_prod1)?

 

You need to login to view this posts content.

 

Guess, I made a mistake when installed that EP on production system, and made a clean-up later
Now I am in strange situation, 26100 updates are applicable but don't come in WU, I need to do them manually?
1152 doesn't install as is from other branch.

What am I supposed to do now?

 

better to stay on 26100.1150 for now. (unless we want to test)
being late for a subway is not a big deal unless there is a fire at home

 

try this:
Launch command prompt as trustedinstaller (use NSudo or PowerRun...)
copy and paste

Code:

set "k=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages"
set "p1=Package_for_KB5037898~31bf3856ad364e35~amd64~~26100.380.1.2"
set "p2=Microsoft-Windows-Ge-Client-Server-Beta-Version-Enablement-Package~31bf3856ad364e35~amd64~~10.0.26100.380"
set "p3=Microsoft-Windows-Ge-Client-Server-Beta-Version-Enablement-Payload-Package~31bf3856ad364e35~amd64~~10.0.26100.380"
reg add "%k%\%p1%\Owners" /f /v %p1% /t REG_DWORD /d 0x20070
reg add "%k%\%p2%\Owners" /f /v %p1% /t REG_DWORD /d 0x20070
reg add "%k%\%p3%\Owners" /f /v %p1% /t REG_DWORD /d 0x20070
dism /Online /NoRestart /Remove-Package /PackageName:%p1%

 

Did it.
Reg add worked, DISM gave an error message.
Running with NSUDO -U:T -P:E
WhoAmI says ntauthority\system

 

Can you check or share CBS.log?

 

I was able to uninstall specifying MUM file from uncompressed update

 

I wonder how this is implemented?
I know about the method -

Code:

Dism /Mount-Wim /WimFile:boot.wim /index:2 /MountDir:Mount
Reg load HKLM\SSYSTEM Mount\Windows\System32\Config\SYSTEM
FOR %%A IN (TPM SecureBoot) DO Reg Add HKLM\SSYSTEM\Setup\LabConfig /v Bypass%%ACheck /t REG_DWORD /d 1 /f
Reg unload HKLM\SSYSTEM
Dism /Unmount-Wim /MountDir:Mount /commit

I looked at boot.wim there are no these entries.