![]() ![]() ![]() I have a habit of checking processes in perpetually running ProcExp once in a week or two and MaskVPN has been eradicated a few days before I noticed the Ctrl-N problem (not using it frequently). MaskVPN has a deamon that's visible in ProcExp but you can't spot it unless you are checking. The only suspicious thing within the past few days was that I've found a MaskVPN process and eradicated the whole thing manually (MaskVPN is nominally legit but is used by some malware as "self protection", Win Defender never screamed a fault so it was probably from some game on AppStore - they only things I installed for the past week+). It took some time for the logoff/lock/switch screen to show op => Windoze does perform a light UI-related reset on Ctrl-Alt-Del and something was stuck or slightly messed up. The Ctrl+ Alt+ Del and then Esc (to simply go back - the whole point is not to interrupt your running stuff). On-Screen keyboard ( Win+ R OSK Enter) served as a diagnostic tool, showing that Ctrl-N was really not getting propagated but that a browser (or editor) does receive Ctrl-N from OSK. Only Ctrl-N didn't work and it looked like a text editor glitch, but then it didn't work in browsers and the only "solution" visible on the net was ridiculous (reinstall driver - yeah right :-). I came across an equivalent problem today but "Windows Key" was not affected which made it harder to find a solution. I also wonder, because the Win key can mess up a game pretty badly, maybe some games have ways of disabling that while they are running? Or disable the driver, without disabling your last input device, and test again. Do you have any AutoHotkey scripts running? Do you have any shortcut programs running, like special launcher software, or special mouse or keyboard or touch drivers/software? Temporarily stop that software in Task Manager, and/or temporarily stop the services that it runs on. Data: 0 to disable restriction, or 1 to enable restrictionĬheck for other software running.Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.Then check this key as well while you're in there: They will ask you to push the Windows Key and R at the same time. That value disables it, you would remove the key completely to have it work normal. Yes No JF jfybel Replied on AugReport abuse In reply to Jian20's post on JanuWarning Some scammers will call and say you have a virus and that they will 'help' you 'fix' it (they will upload a virus to your computer). The Windows logo key is a keyboard key which was originally introduced on Microsofts.Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout.Instead, go halfway down the page to "Let me fix it myself", run regedit, and see if the following key exists there: Go to Microsoft KB216893, and do NOT run the "fix it" (XP). Hit Shift 5 times quickly - is Sticky Keys working? Now check Ctrl+ Alt+ Del, which should bring up the Windows Security screen (menu), and Ctrl+ Shift+ Esc, to open Task Manager - are they working (malware test)? To work around this issue, press and release the Windows logo key again after you return to the local computer.Quick check Win+ Tab, Win+ P, Win+ L and Win+ R - are they also not working? If you selected On the remote computer, go to step 4.ĭisconnect the Remote Desktop session, or switch from the Remote Desktop session window to a window on the local computer. If you selected Only when using the full screen in step 1, expand the Remote Desktop session window to full screen. ![]() Yes, 'super' is the generic name for the key that could be Windows key, Command key, etc. I have the /dev/tty keycap set for work and Im waiting on my susuwatari keycap set to show up for my setup at home, both have the 'SUPER' key. To start the Remote Desktop session, select Connect. It only became a 'windows' key when computers started being sold with windows preinstalled on them. This issue occurs if you use particular settings for your Remote Desktop connection and you take the following steps:īefore you connect to the remote computer, open the Local Resources tab of the Remote Desktop Connection dialog box, and set Apply Windows key combinations to either On the remote computer or Only when using the full screen. When you press the E key, File Explorer starts. For example, when you press the R key, the Run box opens. This article provides a workaround for an issue where your local computer behaves as if you are always pressing and holding the Windows logo key after you start a Remote Desktop Protocol (RDP) session to a remote computer.Īpplies to: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 10 - all editions, Windows 7 Service Pack 1 Original KB number: 4467266 SymptomsĪfter you start a RDP session to a remote computer, your local computer behaves as if you are always pressing and holding the Windows logo key. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |