Search Issue Tracker
Active
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-97174
Regression
No
SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
Reproduction steps:
1. Open the attached “IN-93020.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Click “Block WindowsKey 1” button
5. Press the Windows key on the keyboard
Expected result: The Windows key is blocked
Actual result: The Windows key still activates
Reproducible with: 2022.3.58f1, 6000.0.38f1, 6000.1.0b5, 6000.2.0a2
Reproducible on: Window 10 (User reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- Reproduces if Active Input Handling is set to “Input System Package (New)” or “Both”, but does not reproduce with “Input Manager (Old)”
- Reproduces both in the Editor and the Player
- Only reproduces when the Editor or the Player Window is in focus
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] [iOS] [UnityWebRequest] Requests with "UnityWebRequest" are open for SSL Proxying
- SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
- Crash on GetEffectiveBc7TextureCompressor() when loading and unloading all Assets in the Project
- Terrain Masks do not ignore the mipmap limit
- "Build And Run" the project for Web is allowed even though the directory for the non-default browser is not selected
Add comment