Windows 11

MCT is 22631.2715 (Nov 2023) because it's working off a later build.

For you beginners, there's no functional difference between the ISO & MCT versions except MCT is one update later, and MCT is shipped in compressed ESD format. Both are legitimate install images for 23H2.
 
Now that 23H2 has been out for awhile. After a Ntlite cleaning how are things generally going with the newer one. Any difference noticeable? Any kind of news is good news for me.
 
Personally (I didn't exaggerate with NTLite: no App, no MSStore, no MSEdge, "lightened" scheduled processes, optimized Services, no Media Player, no Notepad) I use the same Preset - Corporate Enterprise version - for both Windows 11 22H2 and Windows 11 23H2.

The software I added in post-setup are the same (7Zip, Firefox ESR, Thunderbird, PotPlayer, Notepad++ and WUMT for MS updates) for both versions.

I apparently don't see any substantial differences.
 
Necrosaro said:
Now that 23H2 has been out for awhile. After a Ntlite cleaning how are things generally going with the newer one. Any difference noticeable? Any kind of news is good news for me.
Click to expand...
Only anoying thing i notized is, that i've to keep Spellcheck to avoid a stackbuffer error with CTFMON - both from updated 22621/ enabling package and fresh install!
 
francis11 said:
Only anoying thing i notized is, that i've to keep Spellcheck to avoid a stackbuffer error with CTFMON - both from updated 22621/ enabling package and fresh install!
Click to expand...
Thank you for your experience so far. I usually keep spell check so shouldn't have any issues there.
 
clarensio said:
I apparently don't see any substantial differences.
Click to expand...
This is because it is the same build 22621 with a few added features, the Windows core is the same.

francis11 said:
Only anoying thing i notized is, that i've to keep Spellcheck to avoid a stackbuffer error with CTFMON - both from updated 22621/ enabling package and fresh install!
Click to expand...
Maybe this is an issue nuhi needs to work on.
 
Think he do as few other posts mentioned the ctfmon problem and Garlin explained about new dependecies from OSK in 23H2.
Exept Spellcheck i need Magnifyer and Screen Keyboard. Not a biggie.
1700663731048.png
 
Necrosaro said:
If the windows core is the same, should I even update or wait till the next?
Click to expand...
Well that's personal, it depends on whether you want the new features or not.

Below is a more detailed and official explanation:

"Windows 11, versions 22H2 and 23H2 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 11, version 23H2 are included in the latest monthly quality update for Windows 11, version 22H2 but are in an inactive and dormant state. These new features will remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 11, version 23H2 features."
https://support.microsoft.com/en-us/help/5027397

In my opinion there is no reason not to update if you are already on 22H2 as you are constantly receiving new features so if you are already in hell you better embrace the devil.

"Starting with Windows 11, version 22H2, new features and enhancements are introduced periodically to provide continuous innovation for Windows 11. These features and enhancements use the normal update servicing channels you're already familiar with. At first, new features are introduced with an optional nonsecurity preview release and gradually rolled out to unmanaged clients. These new features are released later as part of a monthly security update release."
https://learn.microsoft.com/en-us/w...se-cycle#continuous-innovation-for-windows-11
 
Last edited:
All the 23H2 Enablement Package does is to increment the build to 22631, and flips a list of Feature Controls (like ViveTool, but en masse).
If you were to uninstall the Enablement, Windows would return to 22H2.

23H2 code has been hiding inside the last few month's 22H2 CU's. The 23H2 ISO is basically the latest 22H2 ISO + pre-installed Enablement.
 
francis11 said:
Garlin explained about new dependecies from OSK in 23H2.
Click to expand...
There is also the possibility of it being a new dependency. Spell checking is mainly used on touchscreen devices on the touch keyboard 'On-Screen Keyboard (Tablet PC)' but in 23H2 there are new features or expanded features like Voice access that apparently uses Spell checking as well.

"You can now dictate complex and non-standard words through the new spelling experience, and the corrections functionality will fix words that were recognized incorrectly."
https://blogs.windows.com/windowsex...ndows-11-experience-begins-rolling-out-today/

But with the exception where Spell checking is actually used, nuhi may be able to remove the component and keep only necessary files and registry keys so as not to break or generate errors in the rest of the OS. He often manages to do this.
 
I am getting the idea that there isn't much benifits for me to go to 23H2. Just some new apps, has there been any tests done through this forum for general performance improvements.

The tests don't have to be benches, they can just be "butt dynos" if you get my drift. Any general noticeable improvements.

I have a hard time with others doing tests that are showing considerable improvements. Just don't trust those.
 
AeonX said:
But with the exception where Spell checking is actually used, nuhi may be able to remove the component and keep only necessary files and registry keys so as not to break or generate errors in the rest of the OS. He often manages to do this.
Click to expand...
I hope so even it seems more and more difficult as MS is moving Windows towards a system fit all devices like (c)Apple talking together.
Just observe all the effort they do to mirror phones to a big screen without cable - it's all about pleasing mobile users which most people have pledged their brains to.
 
If you edit the policy you can reverse the settings to allow CoPilot, and turn off the System tag om Apps. You're just reversing them.
 
Its this thing right? If I switch to US then I may need to edit C:\Windows\System32\IntegratedServicesRegionPolicySet.json to gain edge removal feature. Even tho i don't have it installed, it would make me feel good to see everything is as it should be.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\DeviceRegion]
"DeviceRegion"=dword:0000005e

here are country codes; https://learn.microsoft.com/en-us/windows/win32/intl/table-of-geographical-locations


EU will have it by default it seems...
 
I installed 22631.2787 (en-US), and ran ViveTool. Nothing I changed in IntegratedServicesRegionPolicySet.json worked for me :mad:

Wondering if someone left out a key detail...
 
You must log in or register to reply here.
Back
Top