Does 26H2 include "Low Latency Profile" with latest update (28000.2179)? If not, anybody knows if it will include it with a near update? I like to try this new feature. So, I could return to 25H2 it LLP is not included in 26H1.
How I can reinstall 25H2 on top of 26H2 without formatting and losing data? I tried to mount 25H2 ISO but I can not get the option of keep data and app.
26H2 does not exist yet. It's 26H1, a scoped release, made for certain new ARM hardware. 26H1 (28000) will NOT be able to upgrade to 26H2 (26x00), only to 27H2 next year. You cannot. MS made it abundantly clear that going back in branches is not supported, you have to wipe and start over. The only exception would be branches switched via Enablement Packages (EP), this is NOT the case, here.
Not yet, at least no public announcement from MSFT for 26H1. Probably gonna be ported with the future LCU with official announcement (changelogs) Meanwhile, as there's no visual toggle/option to know whether the LLP is ON or OFF, you can try this vivetool cmd in 28000.2179 and let us know if you see any improvement or not Code: .\vivetool /enable /id:58989092,60716524,61391826,48433719
This LLP feature is mainly for speeding up the launching process of Windows & START (as of now, apps not supported) for older dual/quad core CPU, by boosting the CPU clock to its peak for a short period of time (1-3 sec) If you already have a decent modern/not very old CPU [don't ask for specific CPU model/generation, MSFT didn't release any official documentation for this] with more than 6 cores, then the difference will not be noticeable.
finally, some good news for me installed kb5095676(ssu) kb5092431(netfx481) kb5089570(lcu) 28000.1340(2025-12) → 28000.2179 iotenterprise my vulkan app finally working properly i waited for six months
Any issue running this instead of 25H2 on a x64 pc? I find it to be more stable than 25H2 and is also much newer.
It kinda is newer but not mainstream yet, when 25H2 > 26H2 finally meats 26H1 all will be based on it..
Update: It appears the latest general public 26H1 build (28000.2113) is incompatible with my PC's hardware. Trying to clean install it rendered my computer unbootable (it somehow even made the installation USB drive unbootable). Machine goes straight into UEFI setup. Trying to boot again from the install USB does not work and also messes up the UEFI language (changes to chinese). WTF? This never happened before. I thought I had killed my NVMe SSD. @Enthousiast
I've seen a complaint like this, but on the ventoy forum about ventoy itself, I believe it was about secureboot compatibility. I doubt it's the windows build itself.
I used the latest untouched ISO from Massgrave. Strangely trying to reload 25H2 lead to the same errors but only temporarily.
He's right there's something wrong with the 25H2 May iso. Fresh install wasn't the same, it would restart the computer when I chose Repair PC on my way to command prompt. MS hosed this iso. But to it's own credit i installed two PCs fine with it.
Yep, looks like May 2026 MVS ISOs are botched somehow. Using Microsoft's older 28000.1896 ISO from the Insider page I was able to sucessfully install 26H1 on my system without any hiccups.