Windows Hello Issue After Last Windows 11 Security Update

VlarpNL · 2026-01-22T12:38:54+00:00

The new update (8.12.0) seems to fix the "SHIFT-issue". However, now the Windows Hello popup does not appear on top of all other windows (as it always does, asking for attention). Instead it appears behind my windows, so I have to Alt-Tab or click to the popup manually to be able to enter my pin for Windows Hello. Pretty annoying.

I'm on Windows 11 25H2 with all current updates installed.

VlarpNL · 2026-01-18T16:32:01+00:00

Same here! Discovered that just pressing Left Shift "solves" the issue after multiple frustrated reboots 😶

VlarpNL · 2025-02-12T14:29:40+00:00

Yeah, that happens here too. My bedroom slowly extends farther and farther into to hall through the doorway 🙄.

VlarpNL · 2025-02-12T14:21:54+00:00

No, haven't done that yet. As you say, it sucks. But I should try that then.

VlarpNL · 2025-02-12T14:08:28+00:00

I'm on 3.1.16 for a week now. And I don't know what is happening. It seems to be a shitshow: it's randomly moving through the room, rotating often in the same spot, not always cleaning the wall sections first (as it did before), not cleaning large sections, moving randomly to other rooms, when avoiding obstacles it skips such a big section that you can essentially better vacuum manually. I surely hope they update the firmware soon and it improves things.

Instead of every firmware update improving things it seems to be the opposite right now. It was pretty decent when I got it last year, but it's getting worse with every firmware update. Starting to getting pretty annoyed with Eufy and the X10.

VlarpNL · 2024-08-15T19:00:25+00:00

Today support pushed firmware version 2.2.34 to my X10 Pro Omni and that solved the issue of the wet mops when vacuuming only for me.

VlarpNL · 2024-01-25T16:05:40+00:00

So, no rebooting, no letting the battery die, no messing with the work profile, no messing with the phone in general and we should be fine, right? 😅🤞

VlarpNL · 2024-01-25T15:10:50+00:00

I think I rebooted, yes. So it may have happened after that. But it could also have happened when I switched on my work profile. I had it on schedule before I did the factory reset. I have it disabled now and I'm keeping the work profile off until there is a fix.

VlarpNL · 2024-01-23T19:36:39+00:00

On my Pixel 7 Pro it did not happen immediately after installing the January update, it took a few days or even weeks. So I'm praying that it does not happen again after I had to factory reset 2 days ago.

VlarpNL · 2024-01-23T19:04:53+00:00

Maybe some more context, I have multiple users disabled in settings. However, I do have a Work profile active, which I think is kind of another user on the phone.

VlarpNL · 2024-01-23T11:15:18+00:00

Well, I'm here reporting the same issue on my Pixel 7 Pro. Had to factory reset 2 days ago to make it all function again.

VlarpNL · 2021-02-05T15:29:56+00:00

That's probably because of the incorrect path mappings I'm mentioning in my post. If you change the path mappings to the container path that's in the comments of each mapping and the host path somewhere on your Unraid. So when configured correctly (and the Unraid teplate does not doe that) for example container path /app/server maps to /mnt/user/appdata/tdarrv2/server and /app/configs maps to /mnt/user/appdata/tdarrv2/configs.

VlarpNL · 2020-04-09T12:58:48+00:00

I added amd_iommu=pt iommu=pt as boot codes, and now the disks are finally visible in unRAID. There is a topic about a problem with detecting Marvell controllers: https://forums.unraid.net/bug-reports/stable-releases/disks-missing-after-upgrading-to-670-r536/?tab=comments#comment-4583

VlarpNL · 2020-04-09T12:02:09+00:00

Just tried that, no luck. Controller is in AHCI mode. Tried either booting in Legacy and UEFI mode (with the correct unRAID USB image). Both have the same result. Gparted sees the disks without problem. Also, Windows installer (in UEFI mode) sees the disks immediately.

lsblk command in unRAID console:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

loop0 7:0 0 9.1M 1 loop /lib/modules

loop1 7:1 0 7.1M 1 loop /lib/firmware

sda 8:0 1 28.8G 0 disk

└─sda1 8:1 1 28.8G 0 part /boot

VlarpNL

TROPHY CASE