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?

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?

 

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?

 

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

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.1.2016 at 1:08 PM, Stanislav Syarkevich said:

There is no access to attached .txt files

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

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!