Thanks for checking. Something must be wrong with my ISO. I'll rebuild it again from the original (1288) and see if that fixes the problem.
Last response from, first sigh gamers and ltsc... (please don't be offended) and second, the 22H2 EP doesn't install on 2021 LTSC, the mum file workaround changes 21H2 to 22H2 and 19044 to 19045, wouldn't the simple registry change do the same trick for the game? Wouldn't it be lovely when MSFT stops Windows 10 support for the xbox app entirely now with the official EOS for 10? This is coming up every 3 months it seems...
Hi, I haven't really checked that batch, but it is probably missing the instruction to CD (change directory) to the directory it sits on: Code: pushd "%~dp0" Below @echo off on a new line. As a workaround you can run cmd.exe as administrator, cd to the directory, and then invoke the batch. My two cents. Thank you.
Forgot to update... It was a corrupted ISO and the new ISO installed fine. And thanks abbodi1406 for the W10UI update. Everything updates flawlessly.
The Bitlocker is turn off.The current condition happen because I turn off Secure boot.Enable secure boot , the warning icon disappear. It only happen after windows 10 update to latest 14th October update. What I can do to disable the warning Icon ?
If you want to revert back to 21h2 just change Add to Remove in the command like this: Dism /Online /Remove-Package /PackagePath:"microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum" Dism /Online /Remove-Package /PackagePath:"microsoft-windows-22h2enablement-payload-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum" Hope this helps some people who didn't read ahead (like me ). Update: After removing/reverting back WU seems to give a message some security updates are missing and won't look the updates that are necessary. Will look into it. WIP. Update 2: Seems reinstalling from image is the only option as from now.
Just to add that in case the above still doesn't definitely work for you, then you may first need to unlock the C:\ drive with the following command from Command Prompt (as admin): Code: manage-bde -unlock C:
What's happening is when you convert over to 22H2, in the background ESU data is being downloaded from Microsoft. When you remove 22H2 and go back to 21H2, 21H2 gets confused by the ESU data, hence the security errors. IMO, it's not worth potentially bricking your OS in order to show "19045" instead of "19044".
What ESU data? it just WU detection metadata, and it's evaluated on each scan you can manually install KB5068781 on "hacked" 22H2 LTSC 2021, and it will work no one should install 22H2 EP on LTSC anyway
Don't bother with it. There never was an official 22H2 LTSC. Why are people trying to create a "22H2 LTSC" from 21H2, which would pretty much qualify as a frankenbuld?
The entire purpose of LTSC/B is that the build doesn't change. It never "Updates" or "Upgrades" to a newer build. It only receives security patches. If someone wants an updated build of Win10 with less online features, they need to run the latest win10 iso through some kind of lite'ing script or program.