The Peek default shortcut causes Ctrl+Space to not work in Visual Studio

[wyldphyre]

Microsoft PowerToys version

0.70.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

Peek

Steps to reproduce

• Turn on Peek with default shortcut (Ctrl+Space)
• Open Visual Studio (2022, 17.6.1)
• Attempt to use the Ctrl+Space shortcut to trigger intellisense, etc

If I turn off Peek I can use Ctrl+Space in Visual Studio as normal.

✔️ Expected Behavior

The things that normally happen when pressing Ctrl+Space in Visual Studio do not happen.

The Peek shortcut should only take effect when the user has File Explorer focused.

❌ Actual Behavior

Things that normally happen when pressing Ctrl+Space in Visual Studio do not happen

Other Software

Visual Studio 2022, 17.6.1

[Francisco-GV]

I came to report this same problem.
Just want to add: It not only causes the Ctrl+Space shortcut not to work in VSC, but in the whole system in general.

I test it with many keyboards tests and apparently when Ctrl is pressed, the system doesn't recognize the space pressed but it does when it is released.

[wyldphyre]

I came to report this same problem. Just want to add: It not only causes the Ctrl+Space shortcut not to work in VSC, but in the whole system in general.

I test it with many keyboards tests and apparently when Ctrl is pressed, the system doesn't recognize the space pressed but it does when it is released.

I figured it was a problem outside of Visual Studio, but I wanted to report a minimal reproduction. It's good to have some confirmation.

[DomenicoMammola]

Same problem in another code editor: Ctrl+Space shortcut for code completition stops to work in Lazarus too.

[leduyquang753]

I was playing Counter-strike: Global offensive and then I could not jump (Space) while I was walking (holding down Ctrl). Turns out this is the culprit heh. I'm disabling Peek for now.

[jaimecbernardo]

It's also possible to change the Peek shortcut.
/dup #26150

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!