26200 is fake build number it will never get Features on Demand ISO (or any ISO except Windows ISO) use 24H2 ISO, then add latest cumulative update
Similarly to other people above, after I integrated .7015 update into my 26100.1 base, the start menu remains the same old garbage style. It didn't switch.
What do you mean by fake build number? If I understood correctly it's better to install 24H2 and then upgrade it to 25H2? But why?
Fake as in by registry only, as with 1903 > 1909 as with 19041>2>3>4>5 as with 22621 > 22631 and now with 26100 > 26200, not real Upgrades but buildnr bump only. All updates and such are still baseline 26100.
Pretending to have a new release every year and after a year or 2 or 3 a real new major release. All can be different soon because there were major new changes at the MSFT offices.
The start menu has simply stopped working and OneDrive keeps opening and closing on its own. This build is garbage!
Oh, I hope so! And for the better. They were pretending to work as fast as possible while dragging themselves as slow as possible. Start menu is an example of that
I downloaded the old media creation toolkit code from github and updated it with claude code 4.5 after 10 minutes I was able to pull the newest 25H2 Enterprise ISO with a couple clicks if anyone wants the updated media creation toolkit - I will share it - otherwise it takes about 20 min to replicate what I did probably
Hi Enthousiast or abbodi1406 or BaffledSoftware, I’ve staged WindowsHello.Face~~~~0.0.1.0 on build 26200 using the 26100 FOD ISO. Capability shows as Installed, WbioSrvc is Running, and the IR camera is recognized as a biometric device in Device Manager. However, the shell UI for Windows Hello Face is fully suppressed: No FaceLogon.dll in System32 No biometric plugins in WinBioPlugIns No IR LED activity on wake No fallback message (“camera blocked”)—just a straight PIN prompt AllowSignInOptions policy is set to 1, and the device is not domain-joined or MDM-managed. This looks like a shell-side block, possibly tied to CU logic or incomplete shell extension staging. Can you confirm whether Hello Face UI is expected to surface on 26200 with this capability staged? Or is the shell gating biometric exposure until a future CU? (SEE BELOW POST FOR UPDATE)
Update: Hello.Face.20134~~~~0.0.1.0 is installed and was working fine until the latest CU. Now the biometric class GUID {53D29EF7-377C-4D14-864A-EB3A85769359} is missing from HKLM\SYSTEM\CurrentControlSet\Control\Class, and no biometric drivers are staged. No shell extension is provisioned. Can you confirm if the CU de-staged the biometric class or if a rehydration CAB is needed?
@tariq Wrong thread, here is 23H2. || Edit: Moved. Homebrew is not allowed to be posted here, publicly at least. Documenting the process is the correct option.
Got bug with task manager app, it wont close and starts new instance at each start-up. Can anyone check on 26200.7015?
I'm using (temporary, only for these months) Win11 25H2 and I have installed 26200.7015 (same as you). I don't have that nasty bug. But of course, Win11 is very slow, buggy and horrible. File Explorer is really slow, the same as Task Manager that takes several seconds to load (unlike Win10).