Windows 8.1 is forgetting Ctrl+1,2,3,4,5 shortcuts designated for keyboard layout switching after wa


Recommended Posts

I have a configuration of Ctrl+1,2,3,4,5 shortcuts for switching keyboard layouts on Windows 8.1.

 

Once I boot up my laptop they work just fine and the layouts shortcuts setup window looks like this if I open it:

original?v=mpbl-1&px=-1

 

However now when I close my laptop, putting it into sleep mode, and then open it again, the keyboard shortcuts stop working and if I open the aforementioned setup window, it also looks as if I have none configured:

original?v=mpbl-1&px=-1

 

To get my shortcuts back after sleep mode I have either to reboot the laptop, or assign the shortcuts again manually.

 

This is a problem I've experienced before on this same machine (Lenovo Yoga 13) with Windows 8 (before the 8.1 update) and I guess at that time it dissapeared after some editing of the list of layouts I use.

But now I've added some layouts to the list, and then removed some of them and so on and here is what I get again.

Maybe there is some branch of Windows Registry involved with the layouts and keyboard-shortcuts messed up and I could simply remove the registry branch and start with a clean slate?

It looks like these settings are stored here:

HKEY_CURRENT_USER\Control Panel\Input Method\Hot Keys

 

Defaults are loaded here:

HKEY_USERS\.DEFAULT\Control Panel\Input Method\Hot Keys

 

I assume that your machine locks and you need to login after it wakes from sleep?

  Quote
It looks like these settings are stored here

 

Thank you!

 

If I just remove the HKEY_CURRENT_USER\Control Panel\Input Method\Hot Keys branch, will Windows recreate it clean, or will it cause some further error?

 

  Quote
I assume that your machine locks and you need to login after it wakes from sleep?
 
Yes - it does. I was just about to ask how it matters, but actually now I see that the same problem appears once I do Win+L and log-in back. Is it some known bug then?
  On 22/06/2015 at 20:41, eugrus said:

 

Thank you!

 

If I just remove the HKEY_CURRENT_USER\Control Panel\Input Method\Hot Keys branch, will Windows recreate it clean, or will it cause some further error?

 

 

 
Yes - it does. I was just about to ask how it matters, but actually now I see that the same problem appears once I do Win+L and log-in back. Is it some known bug then?

 

 

I would assume that the keys will be re-created from values in the .DEFAULTS key if you wipe what's in HKCU. However, I would still export any existing values so that you have backups to restore. I'm skeptical that the values of these keys are being rewritten on logout/login, but it's worth a look.

 

I'd be curious to see whether rewriting the .DEFAULTS with your custom settings is sufficient to resolve the issue, or whether this arises with a different (fresh/local) user profile.

What really seemed to help was rewriting the .DEFAULTS with my HKEY_CURRENT_USER settings!

 

Thank you a lot! I would have never figured this out myself and using Ctrl+1,2,3 is a huge part of my typing process!  :D

 

Ofcourse now one should remember to do it every time after changing the layout shortcuts settings! I guess we should make some kind of bug report for Microsoft out of it! :)

 

I am attaching my old (messed up) defaults and the new ones (these are .reg-files with extensions changed to .txt) for the record  :shiftyninja:

default hotkeys.txt

new default hotkeys.txt

  Quote
What really seemed to help was rewriting the .DEFAULTS with my HKEY_CURRENT_USER settings!

 

Glad you got this resolved.

 

Anyone on W10 Preview able to reproduce the issue? If so, may be worth a bug report if it's not already in feedback.

 

Edit: I'm not seeing this on Windows 8.1; my user's Standard/non-admin, linked to my MS account. So far only have two shortcuts assigned to languages, and tried locking and logging back in.

 

got it to work, have loaded Chinese, French? ??Occitan, assigned them to 1 -4 similar to that described in the first post. My hotkeys get wiped on lock and logging back in.

Looks like it is in fact an old legacy bug, apparently going at least from the times of Windows XP: https://superuser.com/questions/327479/ctrl-space-always-toggles-chinese-ime-windows-7
I would love to have it included into the Microsoft's bug tracker, but I don't seem to find my way through connect.microsoft.com  :/
  • 2 months later...
  • 4 months later...
  • 4 weeks later...
  On 14/01/2016 at 12:08, Stanislav Syarkevich said:

There is no access to attached .txt files

Expand  

Here are my user settings: http://pastebin.com/MdM86MQD

My current defaults: http://pastebin.com/KUajUV6E

And this is what the problem-plagued registry entry looked like: http://pastebin.com/434JXMEG

This topic is now closed to further replies.
  • Posts

    • https://shop.royalmail.com/special-stamp-issues/monty-python
    • Microsoft disables a key graphics feature in Edge by Paul Hill Microsoft has released its new security baseline for its Edge browser version 139, it includes the addition of one setting and the removal of one other. For those that are unaware, these security baselines allow admins to set an organization’s Edge browser settings to the default that Microsoft recommends at any one time. You can download the new package from the Security Compliance Toolkit. With this update, the company is enforcing the default to disable the EnableUnsafeSwiftShader policy. This will help to mitigate potential risks as malicious web content could exploit vulnerabilities in the renderer. SwiftShader is a software-based renderer that serves as a fallback for WebGL in environments without GPU acceleration, such as virtual machines. With Microsoft’s disabling of it, it seems as though this compatibility tool is now seen as a liability. The disabled SwiftShader was the most relevant in virtual machines which are widely used in enterprises, so this change poses the risk of causing a bit of disruption. While the move is a good one for security, those who it affects may want to deviate away from Microsoft’s security baselines. The security baseline announcement also mentions a new Edge for Business security connectors feature which is designed to integrate the browser with security software for DLP and authentication. Microsoft said that these connectors can close critical gaps in enterprise security. You can learn more on the feature’s landing page. Microsoft doesn’t seem to have made the change to SwiftShader due to existing vulnerabilities, instead the move seems to be a proactive security improvement. If you rely on it with your virtual machines, feel free to deviate away from Microsoft’s security baseline, but understand you’re no longer following the company’s security advice.
    • Edge 139 is out with big performance boost, password improvements, and more by Taras Buria Microsoft has released Edge 139 to all users in the Stable Channel. The latest version (139.0.3405.86) introduces some notable changes to the browser, performance improvements, and bug fixes. It also removes some of the existing features, as Microsoft strives to streamline the browser and its features. Microsoft Edge 139 brings a reworked Settings section, which is now built with WebUI2. This enables significant improvements in performance and responsiveness, which Microsoft recently detailed in a blog post. Additionally, Microsoft optimized Settings for a more cohesive user experience by simplifying the number of pages and reorganizing various options. Though it also disables an important graphics feature with this update. Wallet in Settings is discontinued. It now redirects users to the new "Passwords, Payment, and Personal Information" experience in settings. Speaking of passwords, the built-in password manager now has real-time notifications for compromised passwords. If one of your passwords is found in a known data breach, Edge will prompt you to take immediate action and create a new password. Other changes in Edge 139 include the following: Open external links in another profile when recommended by external applications. When Microsoft Edge is set as the default browser to open external links from applications, Microsoft Edge must determine which profile to open the links. Introducing a new policy that can enable/disable Microsoft 365 Copilot Chat in Edge for Business from showing in the toolbar. Edge for Business now has a dedicated policy, Microsoft365CopilotChatIconEnabled, to enable and disable Copilot in Edge from showing in the Edge toolbar. New Autofill Personal Information Settings Configuration. A web form field collection consent toggle will be available in Autofill settings (edge://settings/autofill/personalInfo). This allows users to consent to Microsoft Edge collecting web form field labels (e.g., "First Name," "Email") to improve Autofill suggestion accuracy. Web AI APIs for prompt and writing assistance. Microsoft Edge now implements the Writing Assistance APIs and the Prompt API (for Edge extensions) with a local language model, Phi-4-mini, that is built into the browser. These easy-to-use JavaScript APIs are made available via Edge flags (set to Enabled, by default only for the Summarizer and Prompt API for extensions) so that sites and extensions can apply AI capabilities on the web. Enhancements to Performance and Secure network. Browser essentials is now separated into two distinct experiences (Performance and Secure Network) - both available from the Settings and more menu (“…” on the menu bar). Reset Microsoft Edge enterprise sync. For users having problems syncing browsing data across other signed-in devices, they can reset sync data from the Microsoft servers via Edge Settings edge://settings/profiles/sync/reset. Update to Microsoft AutoUpdate policy. The MAUEnabled policy allowed admins to continue using Microsoft AutoUpdate on macOS. Finally, Edge 139 contains eight security fixes for vulnerabilities originating from Chromium. Microsoft also published a security guideline with details about a key graphics feature, which is now disabled. You can update to Microsoft Edge 139 by heading to edge://settings/help. By the way, if you uninstalled the browser and do not know how to get it back, check out this guide.
  • Recent Achievements

    • Week One Done
      harveycoleman123 earned a badge
      Week One Done
    • First Post
      EzraNougat earned a badge
      First Post
    • One Month Later
      westDvina earned a badge
      One Month Later
    • Community Regular
      Bern@rd went up a rank
      Community Regular
    • Week One Done
      Joey Solo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      667
    2. 2
      +FloatingFatMan
      196
    3. 3
      ATLien_0
      154
    4. 4
      Xenon
      132
    5. 5
      wakjak
      102
  • Tell a friend

    Love Neowin? Tell a friend!