How to make NTLite support Windows 11 26H1

26H1 is targeted for specific ARM-based PC's coming out next year. Just like W11 25H1 was released early for ARM PC's.

Normal x64 PC's will get 26H2 later. When a stable 28000 (or later) preview build is available, NTLite will probably support it like it always has for other W10 or W11 pre-release builds. It's too early to be expecting this right now.
 
Windows 11.26h1 x64 amd64 was released on November 8, 2025. After installing the system, there is no expiration date, no watermark, and it can be digitally activated for normal long-term use.
 
Indeed, 26h1 is for amd64 and ARM now, Nuhi will probably add compatibility this week (he wasn't available before).
 
Testing, will release tomorrow if no big changes.
They add more changes as Previews go along, I don't expect any issues for now.
 
What's the CPU instruction requirement for this new 26H1 28000.x branch?
Has anyone tested this with older CPUs, i.e. 1st/2nd/3rd gen?

Also, from earlier posts here, this build doesn't have the watermark or any expiry date, so can this be considered as RTM candidates?
Those who've been using this 26H1 build in their daily drive, how's the experience? stable enough to use this? Compared to 25H2, is there any difference in terms of performance & stability?
 
I have this installed in a bootable vhd so I can cold boot straight into it. This runs on a Acer Laptop i5-13470, I'm going to copy the vhd to an Asus Laptop i3-11700 and setup for cold boot.
 
I have this installed in a bootable vhd so I can cold boot straight into it. This runs on a Acer Laptop i5-13470, I'm going to copy the vhd to an Asus Laptop i3-11700 and setup for cold boot.
Let me (us) know how it performs on real HW in comparison to stable (retail) 24H2/25H2.
 
OK, I changed my mind, I installed 28000.1 directly onto Asus Vivobook i3-1115G4, 16GB Ram, Crucial 512GB NVMe, Initially stage 1 setup i had to install Intel RST driver for setup to see NVMe, after stage 1 reboot I had 'Inaccessible Device', I rebooted into BIOS, disabled 'VMD Controller', and hey presto everything was fine after that, I have also made some changes in Group Policy to make life easier (image attached). Hope this helps.

PS: I never activated this, checked activation status and it shows as 'Windows is Activated with a Digital Licence'

I like it, very smooth..

Cheers
 

Attachments

  • gpo.png
    gpo.png
    335.2 KB
26H1 is targeted for specific ARM-based PC's coming out next year. Just like W11 25H1 was released early for ARM PC's.

Normal x64 PC's will get 26H2 later. When a stable 28000 (or later) preview build is available, NTLite will probably support it like it always has for other W10 or W11 pre-release builds. It's too early to be expecting this right now.
I'm afraid this isn't accurate.

26H1/26H2 will be released for all PCs, not just for ARM. Just like 25H2 is. But all supported ARM-based PCs are getting an earlier release. Not just specific ARM-based PCs but for all supported ARM-based PCs.

And the first build is already available on the insider canary channel. So the request is very much relevant xhisp !

I wish NTLITE already supported it (at least experimentally) because I need to stay on the bleeding edge to make sure everything works.

I cannot go and tell my colleagues and clients things like "sorry, just stay on the old version because I cannot yet support 26H1" . For the moment I am using dism to modify 26H1 images. For the moment it is very buggy so you are probably not missing out on much xhisp. But still, for a paid tool, this should be supported as soon as possible, and thus I second your request.
 
I'm afraid this isn't accurate.

26H1/26H2 will be released for all PCs, not just for ARM. Just like 25H2 is. But all supported ARM-based PCs are getting an earlier release. Not just specific ARM-based PCs but for all supported ARM-based PCs.

And the first build is already available on the insider canary channel. So the request is very much relevant xhisp !

I wish NTLITE already supported it (at least experimentally) because I need to stay on the bleeding edge to make sure everything works.

I cannot go and tell my colleagues and clients things like "sorry, just stay on the old version because I cannot yet support 26H1" . For the moment I am using dism to modify 26H1 images. For the moment it is very buggy so you are probably not missing out on much xhisp. But still, for a paid tool, this should be supported as soon as possible, and thus I second your request.
There is currently no known issues on 28000, latest version of NTLite does support it as indicated in the changelog.
Feel free to open a new topic if you see any issues.
 
There is currently no known issues on 28000, latest version of NTLite does support it as indicated in the changelog.
Feel free to open a new topic if you see any issues.
I'll test it to see if I discover any potential problems.
I've finished the other tests
 
Back
Top