It's just my test config with all boxes ticked for @mxman2k to review: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-525#post-1823841
I can't see them releasing an official version of LTSC if it doesn't come with the latest security updates.. Posted ISO's don't have them and are dated 8/23/2023.
Later this year it will be officially released for the public, most likely another build As said before, this leaked build is just a IP based ISO, unverified and from august 2023.
No need to talk, the expiration date talks for itself. Expect the release one month or so before that date, and leaked, final, not timebombed ISOs circulating a couple of months before.
i installed it and got download update but when install update jump from10% to 100 and got failed then restart again and so on
i installed it and got download update but when install update jump from10% to 100 and got failed then restart again and so on View attachment 66543 View attachment 66544
It's trying to install latest Canary build, but WU/UUP never offer or include EnterpriseS edition files, so it fail
after downloaded more than 5 giga from update finally fail so i used script of abbodi OfflineInsiderEnroll and stoped feature update
I get an error message on my EliteBook 860 G10 with an Intel i7-1355U when booting the image: BlueScreen with Stop code: UNSUPPORTED PROCESSOR Could this be a bios bug?
I want to get 99% of the updates but not erroneous version updates that fail to install and just keep being redownloaded, since they never should have been offered to LTSC in the first place. So no, I'm am not looking for a way to disable WU. I want to hide the version updates that MicroSloth doesn't have enough brains not to offer to LTSC.
It's just 25941 IP build with a little LTSC sauce as in license files, it doesn't get 5 or 10 years support, it doesn't have any other LTSC parts, it will expire in september, it's just a showcase for the new license files.
Yes but it is the only LTSC 11 we have now and I able to stop my VM from being offered erroneous version updates in my above post, it worked flawlessly.