This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The case:
My wife and I share the same home PC for work, that we use independently throughout the day. We would like to be able to switch between our users without having to log out and close/reopen our respective documents and apps. Kinda like how it works on a Mac when you switch between multiple active user login sessions.
The Problem:
Whenever we try to use the "Switch User" functionality, the taskbar freezes (doesn't load) on whichever user you switch to. The only way to unfreeze the taskbar is to log out completely on one user (and subsequently close all apps/documents), and then login to the other user afterwards.
What I have tried:
Extra info:
Both users have Admin account type and our Windows 10 is updated to the latest version.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
It is very discomforting to see that relatively simple and ubiquitous peripherals like mice and keyboards can interfere with the OS so badly. Disabling HID devices is a poor workaround for something that MS should fix in the OS or the OEM manufacturers like RAZER should comply with MS specs. But then you have a MS intellimouse freezing the taskbar on an MS OS, it seems that MS itself has an internal interoperability problem.
solo hamid
123456xsasdf
MS have little reason to care about Razer O think. Ms even sell their own mice , so they don't mind if others' gear isn't so great.
BTW when I installed windows 11 from scratch (ie not upgrade from 10) the problem stopped for me.
Razer isn't ever going to fix it on their own. It's too much work. The only thing we can do is keep complaining until MS tells Razer they have to fix it.
