[DISCUSSION] Windows 11 Build 26x00 (PC) [24/25H2 Retail- GE-release]

Windows Hello Face broken post-CU in 26200 — provisioning ghost?

Before last week’s cumulative update, Windows Hello Face worked flawlessly on my 26200 system. Since the CU, it’s broken — and I’ve traced the failure to a provisioning ghost:

• Hello.Face.20134~~~~0.0.1.0 is marked as Installed, but DISM shows 0-byte footprint — no binaries, no payload.
• Hello.Face.Migration capability is entirely absent — not even listed as NotPresent.
• Shell still invokes Hello Face on wake (e.g., “move closer to the camera”), but IR sensor doesn’t activate, and Win32_BiometricDevice class is missing.
• Device Manager shows no biometric device, and WMI confirms the class isn’t registered.
• This is a false-positive provisioning state — shell logic is present, but the backend is missing.
• ISO/FOD audit confirms no viable source for the full Hello.Face stack in 26200.

This was working perfectly before the CU. Now it’s a stub install with no functional support.

Seeking confirmation from @Enthousiast or @abbodi1406 — is this a known regression or intentional deprecation?

 

the updated taskmanager uses up 10% cpu, so you cant monitor idle speeds anymore

 

Look how many instances u have running, got bug with taskmanager hungs in backgrund and old instances being not closed at close X(only manual kill works) Can open/close taskmgr 100 times and i will have 100 processes hung , checked again and they not closing with delay when i still open/close Every new instance eat up more ram, so i think it will crash on low RAM scenario setups.

 

You are right, it went from 0% to 3-5% and now to 10%. Despicable. I use solely System Informer now.

 

I'm using resource monitor now, hopefully the task manager will get fixed at some point

 

You need to login to view this posts content.

 

@TairikuOkami
What app is that GUI menu from?

 

I'm trying to update my Win 11 PC but the update (KB5067036) keeps failing with "Install Error: 0x80070302)." I've tried several times as well as using WUMT (x64) - both fail.

Help?!

 

NextDNS

 

You need to login to view this posts content.

 

Thanks for info, for now i skip task manager and use system informer portable. Dont think power plan messing with task manager as i have custom one for 9800x3d, got disabled via vivetool WebView2 spawning from SearchHost and disable the "resume" process but after reverting still same bug appears.

 

@Suzerain KB5067036 is meant for Insider builds 26120 and 26220 in both Beta and Dev Channels. Not recommended to install it on a retail build.

 

lol probably in future antiAI tools to disable/adjust just like telemetry, privacy, bloat, unnecessary apps etc

 

You need to login to view this posts content.

 

I have no idea

 

Thanks for the reply @abbodi1406 — appreciate the honesty.

I’ve run a full audit across build 26200 post-CU and wanted to surface the specifics in case they help others triangulate:

• Hello.Face.20134~~~~0.0.1.0 shows as Installed via Get-WindowsCapability, but DISM reports a 0-byte footprint — no payload, no binaries.
• Hello.Face.Migration is completely absent — not listed as Present or NotPresent.
• Shell logic still triggers (e.g., “move closer to the camera”), but the IR sensor doesn’t activate, and Win32_BiometricDevice class is missing.
• Device Manager shows no biometric device, and WMI confirms the class isn’t registered.
• FOD ISO audit (latest known 26200) reveals no viable source for the full Hello.Face stack.

Unless there’s a hidden migration path or undocumented capability shift, this looks like a false-positive provisioning ghost — shell logic present, backend missing.

If you or Enthousiast spot any ISO or CU delta that restores full biometric provisioning, I’d be grateful for the heads-up. For now, I’ll treat this as a regression unless proven otherwise.

PS: Just a heads-up @Enthousiast or @abbodi1406: KB5055523 caused this same biometric provisioning ghost in earlier builds too. It’s now fully breaking Hello.Face in 26200. If you’re in touch with anyone at Microsoft or tracking internal deltas, this might be worth flagging.

 

Updated to 26120.6928 classed as a "quality" update lol. Still had no dark mode improvements so enabled it with vivetool. Also get the 10% task manager bug.

 

im trying to integrate the following updates into my image but the script keeps crashing and the content of the updates folder changes (using the latest W10MUI / W10UI) imgur /a/5BfuCPj
this is before I ran the W10MUI script imgur /a/A8iaLqh

the base image used is 26100.1 and I havent had such issues before (been doing this for months) I can try running the script from CMD to see where it crashes

Didnt reach the post limit for links yet and wasnt sure how to share images otherwise