Windows 11

[wylietech]

WinPE Setup for 24H2 defaults to a new Setup client.

Some users claim to have install problems with it, while others think it's too ugly. If you prefer seeing the "Classic" client, you can apply this reg file to boot.wim (Setup):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="X:\\sources\\setup.exe"

Pardon my ignorance. how would you apply the reg file to the boot.wim I am experiencing the same issue with a 24H2 iso I have from my work

 

[tistou77]

Pardon my ignorance. how would you apply the reg file to the boot.wim I am experiencing the same issue with a 24H2 iso I have from my work

You have this option in NTLite, in the Settings page : System => Boot/setup - Legacy
Otherwise, with the reg file, you loaded the boot.wim (Index 2) and in the Registry page : Add => Registry File

 

[wylietech]

You have this option in NTLite, in the Settings page : System => Boot/setup - Lagacy
Otherwise, with the reg file, you loaded the boot.wim (Index 2) and in the Registry page : Add => Registry File

Thanks, I am found the option and I am testing it.

 

[luckscent]

Why do websites recognize my machine as Windows 10 and not Windows 11?
Could it be because I removed so much from 11 that it looks like 10? lol
Any settings in NTLite about this?

 

[garlin]

Why do websites recognize my machine as Windows 10 and not Windows 11?
Could it be because I removed so much from 11 that it looks like 10? lol
Any settings in NTLite about this?

Websites cannot detect your PC's architecture and OS version unless you allow them to run some Javascript or Java detection tool. Your browser normally sends an UserAgent string to the website, with many reporting W10 & 11 as the same OS.

Most browsers or browser add-on's will allow you to spoof (fake) the UserAgent string.

A common trick if you want to download the official Windows ISO and avoid being redirected to the MCT page, is to change your UserAgent to a non-Windows platform like MacOS or Linux. Since you identified as non-Windows, MS will offer the ISO instead.

 

[mirt81]

Pardon my ignorance. how would you apply the reg file to the boot.wim I am experiencing the same issue with a 24H2 iso I have from my work

Does also not give a Usable install menu . . . always become issue of "missing hardware Driver" ! ?

Any Tip . . . Please !!!

 

[garlin]

Switching to the old Setup will not fix a missing driver issue. You need to find the required driver, and update boot.wim.

 

[mirt81]

Switching to the old Setup will not fix a missing driver issue. You need to find the required driver, and update boot.wim.

Th@nks for Responce !

Dont know there is a mess Issue for me . . .

If i use a Boot Wim without Winpeshl.ini or RegFile then there is the Option to chose the Classic Partition Menu they Microsoft give to Chose . . . but if i select this Option i become the same "missing hardware Driver" issue !
If i use the new bad Usable Option with the same boot Wim then its works . . . also so that i have afterwards a Windows.old Folder on a yet not so Clean Install

So maybe the Issue is by me when removed one component to much or so on . . .

 

[luckscent]

I created an ISO just updating the system and some components, the ISO created was 8GB, so I used this ISO to apply my component removal preset and it was almost 8GB too. I don't care about the size of the ISO, I just wanted to know if there is something wrong.

 

[garlin]

I created an ISO just updating the system and some components, the ISO created was 8GB, so I used this ISO to apply my component removal preset and it was almost 8GB too. I don't care about the size of the ISO, I just wanted to know if there is something wrong.

June 2025 LCU is about to give birth to 25H2 in a few months (via an Enablement Update). The baby's getting very big now (3 GB)!!

Seriously they're beginning to sneak in hidden 25H2 features in the summer months, because you can't have everyone install a 3-4 GB update when 25H2 gets officially "released". Since 25H2 is already pre-installed and hiding, it can suddenly appear after a single reboot.

This is what MS did with 23H2, except it wasn't so massive an increase in update size.

 

[tistou77]

Indeed, MS added MSIX files for features related to AI and Recall in the latest CUs
But these features are only for NPU machines, my image size had not changed after integrating the CU (files were not integrated into the image)

I removed these MSIX files from the CU to have a smaller CU size

 

[luckscent]

Indeed, MS added MSIX files for features related to AI and Recall in the latest CUs
But these features are only for NPU machines, my image size had not changed after integrating the CU (files were not integrated into the image)

I removed these MSIX files from the CU to have a smaller CU size

View attachment 14477

Did you use the Expand command to unzip? I tried and it wasn't possible.

 

[tistou77]

Did you use the Expand command to unzip? I tried and it wasn't possible.

No, I use DISM
I'll give you the command when I get home, if you like.

Expand, this is for .cab files if I remember correctly.

 

[luckscent]

No, I use DISM
I'll give you the command when I get home, if you like.

Expand, this is for .cab files if I remember correctly.

Ok! thank You!

 

[tistou77]

Ok! thank You!

dism.exe /Apply-Image /ImageFile:Windows11.0-KBXXXXXXX-x64.msu /Index:1 /ApplyDir:Update /NoAcl:all

Replace Windows11.0-KBXXXXXXX-x64.msu with the name of your msu file and create a folder (Update for me, in the same directory as the msu file) for extracting the files

 

[luckscent]

I was able to unzip it using this command, but I don't know how to compress it again or which files to leave. Anyway, I left it with the default NTLite update. Just for information, now it gives an error every time it restarts. In my preset, this component is actually deleted, but before it didn't show this error.
Edit: I solved it by adding the item marked in the second image.

 

[tistou77]

I was able to unzip it using this command, but I don't know how to compress it again or which files to leave. Anyway, I left it with the default NTLite update.

If you want to do it, say so

Just for information, now it gives an error every time it restarts. In my preset, this component is actually deleted, but before it didn't show this error.
Edit: I solved it by adding the item marked in the second image.

If you didn't have an error before, there has probably been a change to cause you to have an error now
settings or something else changed ?

It seems that there are traces of this component left (other than those kept voluntarily) according to your message for CrossDeviceResume.exe
I have nothing about this .exe and no errors

EDIT : I'm going to do a test, to check something

EDIT 2 : No, I don't have any files related to CrossDeviceResume by deleting Client.CBS

 

[luckscent]

If you want to do it, say so


If you didn't have an error before, there has probably been a change to cause you to have an error now
settings or something else changed ?

It seems that there are traces of this component left (other than those kept voluntarily) according to your message for CrossDeviceResume.exe
I have nothing about this .exe and no errors

EDIT : I'm going to do a test, to check something

EDIT 2 : No, I don't have any files related to CrossDeviceResume by deleting Client.CBS

Sorry for the delay, I intend to modify it after the 10th, but here are the two presets if you want to take a look.

It seems I missed a dll to seeing the battery cycles.
C:\Users\Administrator>powercfg /batteryreport
The Power Efficiency Diagnostics library (energy.dll) could not be loaded.

 

[tistou77]

With the last, you no longer have the "CrossDeviceResume.exe" error ?

I'll look into which component this .exe belongs to (if different from Client.CBS), since I don't have this error

 

[Anonymous Internet User]

With the last, you no longer have the "CrossDeviceResume.exe" error ?

I'll look into which component this .exe belongs to (if different from Client.CBS), since I don't have this error

CrossDeviceResume.exe is a part of the new Apple-like handoff feature called Resume and it's baked into Windows Feature Experience Pack - Desktop. The feature can be toggled off (it's on by default because reasons) in Settings->Apps->Resume or disabled in the ISO using a reg file but the CrossDeviceResume.exe executable remains running which is typical Microsoft bullshit. I have been looking for a way to prevent this exe from running. No luck so far. Other than having Process Lasso kill it on sight, but that's not optimal.

It's located in C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy and can't be simply renamed or removed as you'd get an error when logging in to Windows.

If anyone has an idea how to kill this unwanted exe I'd be greatful.