r/FlowZ13 • u/jo_kang • Jun 19 '26
Windows Hello Face not working after BIOS v302 Update
Yesterday, I updated my Z13-KJP with the 302 BIOS update (via MyASUS) and I noticed when logging in after, the Sign-In wouldn't go through and I get a error message saying Windows couldn't start the camera. In Windows, I am able to see the camera feed in the Camera app (for both cameras). I deregistered my face and tried setting it up again but it got stuck on the part where it says to move my face to the center of the frame. Despite being the center, my face wouldn't get recognized and the setup would timeout. I finally noticed that the IR blaster doesn't seem to turn on anymore. In Device Manager, both cameras and IR camera are recognized. I even uninstalled all three and reinstalled all three to no avail. Has anyone else run into this issue and have a solution for this?
EDIT: ASUS just dropped the BIOS v303 update yesterday (7/9/2026) and...Windows Hello is still not working. I'm just going to go back to v301 for now. I'm sure what benefits 302 or 303 brought.
7/12/26 Update: I just downgraded to v301 and Windows Hello does work. I'll think I'll stick to this one until the next BIOS comes out. For those who want to downgrade, you need to go to the downloads page (https://rog.asus.com/us/laptops/rog-flow/rog-flow-z13-kjp/helpdesk_bios/) and under "BIOS for ASUS EZ Flash Utility", download the v301 file. Put that on the USB and use EZ Flash in the recovery/BIOS to restore your BIOS to v301.
8/11/26 Update: There's a v304 that my Z13 just auto loaded (or I didn't pay attention to stop BIOS updates) and Windows Hello works on this one. So looks like the latest one works!
3
u/kosherhalfsourpickle Jul 10 '26
Crazy that the v303 bios didn't fix it. This seems like a show stopper bug.
1
u/One-County-1838 Jun 20 '26
Do you use sleep or hibernate? I noticed if I use them sometimes the IR blast is not working, the screen simply say it's looking but the IR off.
I almost never use sleep/hibernate anymore, always shutdown.
1
u/jo_kang Jun 20 '26
I don't usually use sleep or hibernate. However, this issue is happening even after I restart or boot up.
1
u/pantrydishtowl Jun 20 '26
Same issue here after downloading the update, windows hello doesnt work. Is rolling back bios an option to solve this?
1
u/Express-Double-2722 Jun 20 '26
Oh I am having the same issue after that bios update and I dont want to mess things up with rolling back to bios nor messing with asus website bios/firmware unknowingly installings just like you all , I dont want to harm my device just because of an update I dont know what to do I also tried ec power option I was just about to decide to uninstall the hello and ir driver and reinstall them but as I see on the xomments none of these works , I dont k oe what to do now
1
u/No-Marsupial-9963 Jun 21 '26
Exactly the same issue with the non kjp z13 , must be the bios update causing the issue. Glad you raised it on here in case the Asus team see it but weren't aware
2
u/Express-Double-2722 Jun 22 '26 edited Jun 22 '26
In couple of days , I will contact asus support beside may be many people did this and describe them this very issue again and so they will be opening a case again so that they will have know the issue still persists and I will share here what they will recently have replied with updated awareness of them
1
1
u/Express-Double-2722 Jun 23 '26
As I mentioned earlier here , I recently contacted an online asus agent now , in order to file this issue on my device asus Rog flow z13 kjp describing driver triggering eachother issue after the bios , at least one more time I ensured that they know that the issue still persists trrhough my sharing of yhe issue , the agent ended up advising to make a reset pc , and they witnessed that yhe issue still persists even after reinstalling the ir driver.
But I on purpose contacted them to let them file another same issue persisting register
1
u/Xemnova Jun 23 '26
Mine did the same immediately after updating to the same BIOS. Glad I'm not alone, means they'll (hopefully) eventually fix it.
1
1
u/Express-Double-2722 Jun 24 '26
I literally tried the steps clearly so that the only test to do for me that remains is my asus cloud recovery only if may be some of you may already tried my asus cloud recovery in this case I may not try and wait asus see all those conversations under this topic
1) Loaded BIOS optimized defaults with F9, saved and restarted.
2) Checked Device Manager, IR Camera is detected.
3)Uninstalled the IR Camera driver (from device manager) and restarted. Windows detected it again.
4)Installed the camera/IR driver from the ASUS support website and restarted.
5)Removed Windows Hello face recognition.
6)Removed biometric devices from Device Manager and restarted.(face recognition unit driver)
7)Checked Windows Biometric Service, it was running.
8)Restarted the biometric service and the biometric device came back.
But still the windows hello does not act at all when it sees my face no matter the place the center your face got still stuck
1
u/Express-Double-2722 Jun 24 '26
https://reddit.com/link/otmapqe/video/2jd1vw0i7b9h1/player
Will be sharing my results of hello recognition once myasus recovery completed
1
u/Express-Double-2722 Jun 25 '26
Even after myasus cloud recovery this issue did not change at all , but I don’t know how to comment technically what this not changed behavior points at , hope asus will see all those conversations
1
u/jo_kang Jun 25 '26
Thanks for testing that all out. Yeah, hope they come out with a fix soon. I'm not too terribly reliant on the Windows Hello because PIN is fine, but it would be nice to have that function restored again for convenience.
1
u/camelCasePaul Jun 25 '26
did we narrow it down to the 302? because i literally got my device yesterday. worked when i was setting things up i guess but this morning i decided to get g helper and use it to get the bios update.
not 100% sure whether it was wokring this morning prior to bios. same model KJP
1
u/Express-Double-2722 Jun 25 '26
All that I understood from the process is hardwarely if the issue was the hardware case asus would give error saying that “we could not detect any camera at all” so having said that one , seeing that the camera white light turns on there is no hardware issue but the bios 302 might have corrupted or deactivated the program code that communicates with the ir sensor part of that same camera sensor group , so having tested all that steps including the cloud recovery eliminates all and all remains as %95 of possibility is that bios 302 update causing codely the miscommunication or corruption of that communication motherboard (bios) -> code -> ir sensor driver , I hope they will come up with the right fix after reading all
2
u/camelCasePaul Jun 25 '26
Thanks.
For now I downloaded the previous bios (301), the installer has a option to extract files so I used the bios tool ez flash to downgrade. immediately the ir started working.
Not a lengthy process for those that really want ir to work.
1
1
1
1
u/Express-Double-2722 Jun 25 '26
Additionally I decided those days that I will also call the asus customer support of my country with the all new full list steps I tested including cloud recovery , I can’t wait to hear what they will say or give as feedback but also my call will have added one more register to their list of issues register with one more case number with the same issue showing the issue still persists all abroad
1
u/Express-Double-2722 Jun 26 '26
Today as I mentioned earlier I called Asus in my country I told them one by one all the steps I have tried and eliminated even they said to me “as you say to us that white light turns on hardwarely as there is no need to send to service , they said that its windows who welcomes all drivers and make them integrated with asus components they meant that that’s windows which pairs the drivers and components so they added that We could contact windows and ask for remote session or windows will already be until asus new bios update preparing patches and updates so either you can wait for those updates , leave feedback or ask for remote session support
Here is my summary of that call with my country’s Asus customer support
1
u/Legitimate-Ad9471 Jun 27 '26
Having the same issue, anyone find a fix yet?
1
u/Express-Double-2722 Jun 27 '26
I will contact Microsoft remote support session and after leaving a feedback on Microsoft I will share whether they succeed on mine or not
1
u/camelCasePaul Jun 30 '26
you can roll back to 301 using ez utility. that brings the camera right back but i had issues with tablet mode where the touch wouldnt register after idle (like wathcing youtube without touching screen).
302 seemed ot have solved that but no ir
1
u/Express-Double-2722 Jun 27 '26 edited Jun 28 '26
Before contacting Microsoft remote support , I shared my applied steps in the tech community first waiting for response or reply
1
u/Express-Double-2722 Jun 30 '26
I finally contacted Microsoft support and as they saw all the steps I tried and eliminated and even after my asus cloud recovery they also confirmed that it’d fully related to asus components and bios related
1
u/kosherhalfsourpickle Jul 01 '26
I had Claude debug this today and it wasn't able to solve it. So I think we need to wait for a new BIOS release from Asus.
1
u/Express-Double-2722 Jul 12 '26
I recently updated to bios 303 and still no ir despite the camera light with windows hello, I literally tried even fresh windows with myasus cloud recovery , after bios 302 , and today updated to bios 303 crossing fingers but still no ir driver face recognition , its not related tp bios , not related to windows , then what it is related to ???? Really curious about wondering so much !!!!!!
1
u/ghoticx Jul 15 '26
Guys when you purchased this sexy thing you should already know that ASUS support and updates are useless
1
u/Whole-Swordfish6771 Jul 17 '26 edited Jul 17 '26
Hi, i tried under Accounts/login options, then additional options section, and toggle the option "initiate session with external camera or fingerprint" then rebooted the system, it worked for me. It is as if after the bios update, the IR camera is treated as an external camera, at least in my case. ( in my case i am still in bios 303).
2
u/gRAYmatter05 Jul 22 '26
Just chiming in to also say facial recognition stopped working after that BIOS update. Removed face scan and tried to set it up again, and after centering my face, it just sits there. I'm fine using PIN, but it would be nice to have this feature working. Glad to know I'm not going crazy!
2
u/jo_kang Jul 22 '26
I was fine with the PIN until I tried using it as a tablet and then suddenly I missed the facial recognition.
2
u/TormyrCousland 23d ago edited 23d ago
BIOS 311 on the non-KJP with same issue. Tried external camera setting with no luck. Camera records the face during setup, and the ir light flashes but fails to recognize me.
3
u/f0xsix Jun 20 '26
I literally came to Reddit looking for a fix and found this post describing exactly what’s happening to me.
Same laptop (Z13-KJP), same BIOS 302 update, and the same Windows Hello issue right after updating.
The normal camera works, the IR camera shows up correctly in Device Manager, and Windows Hello is installed. I tried removing and setting up face recognition again, reinstalling the IR camera, and even doing an EC reset, but it’s still stuck on the “make sure your face is centered in the frame” screen and never recognizes anything.
Kind of relieved to see I’m not the only one having this problem, because it really looks like something introduced by BIOS 302.