67
this post was submitted on 13 Jun 2023
67 points (100.0% liked)
Gaming
1495 readers
1 users here now
From video gaming to card games and stuff in between, if it's gaming you can probably discuss it here!
See also Gaming's sister community Tabletop Gaming.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
plus:
minus:
nightmare:
on first boot OOBE i tried to just login with my existing personal ms account which i guess was my first mistake, but it worked fine. i added a fingerprint and it also worked fine. i then added a PIN and it also worked fine. windows downloaded updates and demanded a reboot which is fine. it rebooted and i logged in with a thumbprint just fine. then armoury crate said HEY FIRMWARE UPDATE DEMANDS REBOOT so ok fine reboot and down the spiral we go. fingerprint doesn't work. PIN fails, "something went wrong" with a side of 0xd0000225 over and over. check bios, v317. event viewer says something about some exe with "biometric" in its title failing repeatedly. looks like i have to update through armory crate again? oh, the asus app? does that require me to sign up? it sure looks like it does... ok no, just dark patterns. more updates. more failed login attempts and the most alerts from MS authenticator i've ever had in one afternoon. bios v319, windows and my asus and armoire box all claim everything's as up to date as one can get, but you're sure gonna have to get a notification and cancel a request to reset your PIN on each login
i genuinely thought it might be headed for a refund, but shift+f10 and
OOBE\BYPASSNRO
after cloud restore let me make a local account and it's been smooth since, but i've barely installed we <3 katamari reroll on itHow did you manage to launch CMD from the Ally? Is it possible using the built-in touch keyboard during setup? I don't have a USB-C keyboard to connect, unfortunately.
EDIT: I found a workaround: if you enter nonsense during the Microsoft sign-in it will fail and prompt to create a local account.
yeah, i was using an external usb-c dock/hub to get a keyboard working on that :/ fingerprint/PIN woes actually resurfaced, but i've read that it's "expected" with how win11 uses the TPM to manage that kind of data, so any firmware/BIOS updates will generally ruin those i guess, and you have to essentially remove and re-setup any biometrics on any update like that?? idunno, if that's the case you'd really think there'd be a more reliable or at least sensible error message than "something went wrong, we've tried nothing"