KB5124010 (build 26200.9550): Goodix fingerprint not ready for ~85 s after cold boot, error 0x80098057 - fine on 26200.9457

Question

KB5124010 (build 26200.9550): Goodix fingerprint not ready for ~85 s after cold boot, error 0x80098057 - fine on 26200.9457

Banyong Lawhiranthaworn 0

Since installing KB5124010 (Windows 11 25H2, build 26200.9550), my Goodix fingerprint sensor needs 85–92 seconds after a cold boot before it is ready. Fingerprint sign-in does not work at the first sign-in screen, and Settings > Accounts > Sign-in options freezes until the sensor is ready. Unlocking later works normally.

Device

ModelMSI Prestige 16 AI+ C3MG, BIOS E2622IMS.11ASensorGoodix MOC Fingerprint, USB\VID_27**&PID_60**Driver3.12144.0.130 (latest from MSI)Fast StartupDisabled (full cold boots)## What the logs show

In Microsoft-Windows-Biometrics/Operational, the Windows Biometric Service fails to configure the Goodix sensor (event 1109) with 0x800706D9 (EPT_S_NOT_REGISTERED) and then 0x80098057, six times per boot. It retries about every 20 s, and the biometric unit is only created (event 1108) after about 85 s.

BuildSensor ready after bootGoodix 1109 errors26200.9457 (without KB5124010)15–27 s026200.9550 (with KB5124010)85–92 s6 every boot- Uninstalling KB5124010 fixed it: 3 cold boots took 27 / 15 / 20 s, with no errors.

Reinstalling it brought the problem back: 8 cold boots from 2026-09-30 to 2026-10-03 took 85–92 s, with 6 errors each.
Disconnecting all external devices made no difference.

Already tried (no effect)

BIOS reset and EC reset
Fingerprint data reset and driver reinstall
Restarting the Windows Biometric Service (only helps after sign-in, not at boot)

Reported

Feedback Hub: https://aka.ms/AA13q3dw (ID 92778057-77d1-4c33-85e9-407329e8049d)
MSI support ticket. MSI could not reproduce it with Fast Startup on, which is the default.

Questions

Is this a known regression in KB5124010?
Can it be escalated to the Windows Biometrics team?

If you have a Goodix (27C6) sensor and see the same thing after this update, please reply with your device model and upvote the Feedback Hub item.

0 comments

2 answers

Your answer

Answer 1

Update: the October 2026 cumulative update fixed it for me.

I installed KB5127648 (build 26200.9711, released 13 October 2026) through Windows Update on 14 October. Nothing else changed: same Goodix driver, Enhanced Sign-in Security still on, Fast Startup off.

Time from OS start to the Goodix sensor being ready (Biometrics event 1108):

Build 26200.9550 (KB5124010), last two cold boots: 89 s and 86 s, 6 failures each (event 1109)
Build 26200.9711 (KB5127648), cold boot: 19 s, no failures. Fingerprint sign-in worked straight away at the sign-in screen.

The Biometric Service now starts the secure component once (a single event 1601) instead of retrying for about 85 seconds.

Pureinfotech's summary of the update lists "Windows Hello: Fixes an issue that could prevent fingerprint sign-in after a cold boot on some devices", which matches this problem.

If you have a Goodix fingerprint sensor and are still on build 26200.9550, install KB5127648 from Windows Update (Settings > Windows Update > Check for updates) instead of uninstalling KB5124010.

Answer 2

Alex-L 13,165 Microsoft External Staff Moderator

Hi Banyong Lawhiranthaworn

Thank you for the detailed investigation and for providing the Feedback Hub ID. Based on the before/after testing, the repeated Windows Biometric Service errors, and the fact that uninstalling KB5124010 consistently resolves the issue while reinstalling restores it, this does appear to point to a regression introduced in build 26200.9550 rather than a hardware or driver problem.

Community members cannot directly escalate issues to the Windows Biometrics engineering team, but submitting Feedback Hub reports is the correct path, especially when accompanied by logs and reproducible steps. If other users with Goodix (27C6) fingerprint sensors can reproduce the same behavior and upvote the existing Feedback Hub item, that can help increase its visibility to Microsoft engineers.

In the meantime, continue monitoring newer Insider builds and MSI driver/firmware updates for a fix.

Banyong Lawhiranthaworn 0 Reputation points

2026-10-06T06:50:49.94+00:00
Thank you, Alex-L. That matches what I'm seeing.

A few notes for anyone who finds this thread:

This PC is not on the Insider Program. KB5124010 came through the normal Windows Update channel as the September 2026 optional preview (build 26200.9550).

The delay happens only at boot. If the Windows Biometric Service (WbioSrvc) is restarted while I'm signed in, the Goodix sensor is ready within about 1 second with no errors. After a cold boot it takes about 85 seconds, with 6 failures logged (Biometrics event 1109, 0x80098057 / 0x800706D9), and the sensor becomes ready only after event 1601 (secure component started). Enhanced Sign-in Security is enabled, so the problem may be in the boot-time ESS/VBS biometric path.

Workaround: uninstall KB5124010 (cold boot goes back to about 20 seconds and fingerprint sign-in works), or sign in with your PIN after a cold boot.

I'll test the October 2026 cumulative update when it's released on 13 October and post the result here.

If you have a Goodix (27C6) fingerprint sensor and see the same thing, please send your own report in Feedback Hub (Devices and Drivers > Biometrics), mention KB5124010, and add a reply here. Separate reports from different PCs help Microsoft see how many people are affected.
Alex-L 13,165 Reputation points Microsoft External Staff Moderator

2026-10-07T14:29:43.0433333+00:00

Hi Banyong Lawhiranthaworn

Thank you for the additional findings and for documenting the results so thoroughly. At this point, the evidence points to a regression introduced with KB5124010 affecting the boot-time initialization of the Goodix fingerprint sensor on your system, while normal operation after sign-in remains unaffected.

You've already submitted Feedback Hub and MSI reports, documented a reproducible workaround, and committed to testing the October cumulative update. Those are the right next steps. Hopefully Microsoft can correlate additional reports if other users encounter the same behavior.

For now, I'll mark this as awaiting further information from future updates and user reports. Please feel free to return and post your findings after the October cumulative update is installed. Thanks for sharing the detailed troubleshooting data with the community.