https://forums.mydigitallife.net/th...4h2-dev-ge-release.88220/page-27#post-1836307 None of them is in the beta channel
patch 26100.560 didn't fixed my issues with UI slowness repro: 1. open file explorer, edge, firefox and so on 2. shake explorer window - it's fine 3. immediately try to shake edge or firefox window - animatuion is slow for the first half of a second this is on 4k 144 Hz display with VRR disabled, it feels much more worse with VRR
Decided to check out the update & still causing random high CPU usage & temps on my end at this point. Probably just write off windows 11 24h2 in general.
For me, on build 26100.560, programs still take a long time to install :-( Especially Google Chrome takes a very long time to install (maybe MS consider it a threat) But when the programs are installed they run ok I did't se that in build 26100.1
CBSVITSEZ PREND LA IOT LTSC You will have a "healthy" version h""ps://archive.org/details/26100-ltsc-x64-enus
For some unknown reason, after installing KB5037783, the previous Servicing Stack Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1 cannot be uninstalled using the regular method, which is edit Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1.mum to remove permanence=permanent and remove package with dism. The owner in the registry is correct and the data associated is set at 0x00020070 which should allow uninstalling. The package state is 0x00000070 (112) which means installed, not superseded. @abbodi1406 any idea what is changed from previous behaviour?
lol I hope this leaked version is the real deal. I've installed it on all my computers in April. If it's fake I'm fxxked, and I'm sure so are many ppl here. I do believe this one is real though. I think this version is the best OS that MS produced so far. The only downside is you still have to manually load the NVME driver during clean install from USB. The installer is still lacking native support for some NVME.
It was the healthy part that made me respond, the ISO can't be verified so we have to assume it is ok to use but no guarantees, considering the build will be the official one in a few months we can "trust" it is ok to use too..
I tested both 26100.560 in both non-LTSC and LTSC versions and there are definitely some problems like others are mentioning (e.g. CPU spikes, Task Manager bugs/crashes, slow downs) and now I'm starting to get LSASS errors. Verified files and everything was fine so it's not corruption. Still 5 months till official release so I'm sure all the bugs will be worked out by then.
June would be the 6th month, technically that still is not the second half of 2024 but for early access we finally could get some "IP" ISOs on techbench
Version 10.0.26100.560 Nothing happens after editing the mum file to remove the permanency flag. Code: 2024-05-19 07:53:20, Info SXS TurboStack version 10.0.26100.558 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.558_none_ab5c3705b04c9468 2024-05-19 07:53:20, Info CSI 00000002@2024/5/18:21:53:20.681 WcpInitialize: wcp.dll version 10.0.26100.558 (WinBuild.160101.0800) 2024-05-19 07:53:20, Info CSI 00000003 Perf: LRU Cache Initialize @0x1cbe5bfb340; Maximum Size: 1024 MiB; Initial Elements: 8192 2024-05-19 07:53:20, Info SXS Initialized store, arch=amd64, style=Desktop, compact=true, windir=(null), sandbox= 2024-05-19 07:53:20, Info CBS Virtual Edition: Microsoft-Windows-EnterpriseEdition will be mapped to: Microsoft-Windows-ProfessionalEdition 2024-05-19 07:53:20, Info CBS Session: 31107437_3429417172 initialized by client DISM Package Manager Provider 2024-05-19 07:53:20, Info CBS Appl: detect Parent, Package: Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1, Parent: Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.26100.1, Standalone integration and parent is missing, ignore this parent. 2024-05-19 07:53:20, Info CBS Appl: Evaluating package applicability for package Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1, applicable state: Installed 2024-05-19 07:53:20, Info CBS External EvaluateApplicability, package: Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed 2024-05-19 07:53:20, Info CBS External EvaluateApplicability - Current state, package: Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1, package current state: Installed, lowest rollup current state: Installed, resulting current state: Installed 2024-05-19 07:53:20, Info CBS Skipping already installed SSU package Package_for_ServicingStack_268~31bf3856ad364e35~amd64~~26100.268.1.1. Current state Installed Target state Absent 2024-05-19 07:53:20, Info CBS Priority: Setting normal priority Just an annoyance, nothing major, but I thought this is something to be flagged in relation to this build. To revert to consistent state, I am deleting the modified mum and reinstall the older 268 SSU using the cab and dism. It looks like the 268 SSU is not superseded by the new one, but this should not impact uninstalling a non-superseded package. Edit: It may be relevant that the installation is en-us, with localisation as en-au but the language pack in use is en-us, not en-au.
Now its good some people really do the right thing when on the internet, like dont believe everything you read, or what people say, dont use third party software, be sure you know/read/download ANYTHING is from a trusted source, and so on. BUT one can take this a little too far and start wearing tin hats. A little research and applying risk management goes a long way in making ones life easier. The current 24H2 ISO we are all using IS LEGIT, but we wont get confirmation from M$ that it is so. Simply put, Just look at its contents, all downloaded from M$, it gets updates from M$. Its just not put together by M$. Look at all the users using it, no-one has found third party insertions. While I am NOT A TIN HAT wearer, I do play it safe on these things. If you are a tin hat wearer, then simple, dont use it, wait til M$ releases it.