Search Issue Tracker
By Design
Votes
3
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b5
6000.2.0a2
6000.3.0a1
6000.4.0a1
6000.5.0a1
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The usage of the windows API SetWindowsHooks was never an officially supported feature, this issue will be tracked internally as a feature request to suppress the Windows keys.