PowerToys: [KBM] Adding a shortcut to remap crashes PowerToys
When I try to add a shortcut to remap using the KeyboardManager, PowerToys crashes.
How to reproduce
- Open PowerToys (doesn’t matter if you run as administrator)
- Go to the Keyboard Manager
- Click on Remap shortcut
- Click the + button
- It crashes.
Additional information
- Affected PowerToys versions: 0.27.1, 0.28.0, 0.29.0, 0.29.3
- What device you’re running (inc. CPU type, memory, disk, etc.)
- Dell XPS 13 9310
- CPU: Intel Core i7-1165G7
- RAM: 32GB
- Disk: 2TB SSD, 1.7TB free
- What build of Windows your device is running
- 10.0.19041.610
- Edit: Still happening after upgrading to 10.0.19042.685
- What toolsand apps you’re using
- Chrome, WinCompose
I also found the following in the Event Viewer:
Faulting application name: PowerToys.exe, version: 0.28.0.0, time stamp: 0x5fc922a4
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xc000027b
Fault offset: 0x000000000010bd5c
Faulting process ID: 0x2230
Faulting application start time: 0x01d6d7af329b469b
Faulting application path: C:\Program Files\PowerToys\PowerToys.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: f4ad0a5a-2a6b-4fc1-96a7-0115f9af034b
Faulting package full name:
Faulting package-relative application ID:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 51 (24 by maintainers)
Hi @ridesky and @seba5496 ,
I still haven’t been able to reproduce this error on my machines. Could you please send a dump file?
One way of achieving this would be by creating an entry in the Registry Editor (
regedit.msc), forComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\PowerToys.KeyboardManagerEditor.exe, according to the instructions in https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumpsIt should look something like this in the end:
After that, please replicate the bug, navigate to
$LOCALAPPDATA%\CrashDumpsin the File Explorer and upload the zippedPowerToysManagerEditor.exe.*.dmpfile to a GitHub comment.The idea is that this could show us the stack trace and help pinpoint what the issue might be.
Yes, apologies. No crashes, I can now click [+] on the keyboard shortcut remapper.
Thanks for fixing
What I seem to notice is that all the machines where this is happening recently are on the 19043 build number for Windows, patch 1110. I’ll try to update a VM and see if I can replicate it.
Same issue here
PowerToysReport_2021-07-06-14-29-43.zip
PowerToysReport_2021-04-29-15-53-55.zip
It behaves differently from previous versions, but still doesn’t work properly. When I click “+” button, the “Remap shortcuts” window closes unexpectedly, instead of the whole PowerToys crashing (previous behavior).
I also have this issue on my Dell Precision 5530, so I agree with @yoonys assumption that this problem is specific to Dell laptops. I just installed 0.35 and experience exactly what is described above.
@mykhailopylyp Thanks for your help. It still crashes. Here’s the report.
PowerToysReport_2021-03-13-14-46-04.zip
PowerToysReport_2021-03-10-16-01-28.zip
Here you are. PowerToys still crashes and closes when I click “+” button.
@mykhailopylyp Attached is the report. Note that I wasn’t able to reproduce with the private build 0.0.1 because I cannot open PowerToys (see error above), but is still a problem in 0.29.3. The report is created using 0.0.1. Thanks for your help! PowerToysReport_2021-01-21-09-42-37.zip
@yoonys run “%PROGRAMFILES%\PowerToys\Tools\BugReportTool.exe” (the double quotes are important) that will create a zip file on you desktop named like this PowerToysReport_2021-01-04-12-02-08.zip You can drag and drop it in a GitHub comment.
@evoL
Thanks for the info, but that shouldn’t have any effect on the Settings app.
@evoL open a command prompt and run
"%PROGRAMFILES%\PowerToys\Tools\BugReportTool.exe"(double quotes are important) that will create a zip file on you desktop named like thisPowerToysReport_2021-01-04-12-02-08.zipYou can drag and drop it in a GitHub comment. Thanks.Fixed for me with 0.29.3 and latest .NET Core!