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

    • A coalition of publishers sued OpenAI and Microsoft over scraping content without consent by Hamid Ganji Image via Depositphotos.com AI companies often rely on readily available internet content to train their chatbots and provide users with instant answers. This method of AI training is fast and relatively inexpensive, but using a website’s content without permission or compensation is not something publishers like to see, and this is exactly why Microsoft and OpenAI are now being sued. As reported by Bloomberg, a group of publishers that collectively own nearly 400 newspapers has filed a lawsuit against OpenAI and Microsoft. The coalition argues that the two companies scraped their content to build AI chatbots like ChatGPT and Copilot without paying any compensation. The complaint, filed in the U.S. District Court for the Southern District of New York, argues that while AI products have generated billions of dollars in market value using publishers’ work, none of that value has been shared with the publishers. The plaintiffs are seeking statutory damages and injunctive relief for alleged copyright infringement and violations of the Digital Millennium Copyright Act. “Defendants systematically and secretly crawled the Publishers’ websites—including content behind paywalls and other access restrictions—and copied the Publishers’ articles, stories, and other original works onto their own servers without authorization,” the complaint states. The publishers also described the AI boom as a “death knell for local journalism” if AI companies that scrape content for free are not held accountable. Former New Jersey Attorney General Matthew Platkin and his law firm, Platkin LLP, are representing the publishers. “Our models empower innovation, are trained on publicly available data, and are grounded in fair use,” OpenAI spokesperson Drew Pusateri told Bloomberg. This is not the first lawsuit involving the unauthorized use of publishers’ content by AI firms, but it is one of the largest coalitions ever formed against the free use of content by AI chatbots. In 2024, OpenAI and Microsoft also faced a similar lawsuit from eight newspapers that claimed AI products were benefiting from their content without permission.
    • Rufus alternative Ventoy now supports Windows 11's mandatory update, fixes major boot bug by Sayan Sen While Microsoft has its own official Media Creation Tool used for making bootable USB media, there are some popular third-party utilities as well which offer additional options like bypassing system requirements, Microsoft Account creation, and more. One of these is Ventoy, and the software has received its latest update today. In fact, the app actually got a slew of updates over the last couple of days, three version releases in total, to be specific. The first release, version 1.1.13, was pulled as there was some unspecified error in the update, and as such, the corrected version 1.1.14 was pushed out. Following that on very short notice, 1.1.15 was published as well. For those unfamiliar, Ventoy is an open-source utility that lets users create a bootable USB drive once and then simply copy ISO, WIM, IMG, VHD, or EFI files onto it without repeatedly formatting the drive. It supports both legacy BIOS and UEFI boot modes, Secure Boot, and a wide range of operating systems, making it one of the most versatile tools in the category. The biggest change in version 1.1.14 is an updated Secure Boot shim file aimed at resolving the UEFI CA 2023 issue, which is basically a compatibility problem that has affected Secure Boot environments on some systems. If you recall, we reported about severe boot issues on HP devices following the release of updated Secure Boot 2023 keys. For anyone who may not be aware, back in early 2024, Microsoft announced that it was updating Secure Boot keys as they were going to become 15 years old in 2026, which is also when they are set to expire. As such, the new 2023 certificates have been rolling out with the newest Windows 11 updates. Updated boot manager and Secure Boot certificates are crucial for protection against malware like bootkits. These are mandatory updates. Alongside that, the VentoyPlugson graphical plugin configurator was updated in sync with the release. The update also introduces a new VTOY_SECURE_BOOT_POLICY option within the Global Control plugin, giving users more flexibility in managing Secure Boot behavior. Ventoy has also received a fix for a startup issue when Secure Boot was disabled. Microsoft does officially allow users to boot systems without Secure Boot as long as the PC is Secure Boot capable. The full changelog is given below: Update secure boot shim file to solve the UEFI CA 2023 issue. The new release use a new CA, so you need to enroll the new key for the first boot time. VentoyPlugson update synchronously. Global control plugin add a VTOY_SECURE_BOOT_POLICY option. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. You can download the latest version of the app here on Ventoy's official GitHub repo or from Neowin software stories.
    • Windows 11 is fine, no issues on any of the machines I've run it on since release. The stricter security requirements are a good thing, sometimes the baseline needs to change and people will winge, but it is what it is. Happened with the move from 9x to NT - broke compatability Happened with XP SP2 when security started to become a serious consideration Certainly happend with Vista that brought in UAC, the concept of not running as admin (something that has been the norm in Linux/Unix from pretty much the start) and a completely new driver stack. Windows 11 will probably get looked back at as the point where even consumer and SMB IT was dragged kicking and screaming into a somewhat secure by default configuration.
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!