Issue 1:
Apologies if this is a duplicate -- I search the issues for Zone Editor and could not find anything comparable.

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.815]

PowerToys version: 0.16.1, 0.16.0, 0.15.2

PowerToys module: Fancy Zones

Zone Settings: {"app-zone-history":[],"devices":[],"custom-zone-sets":[]}

Steps to reproduce

Install Power Toys

Enable Fancy Zones

Navigate to Settings > Fancy Zones > Edit Zones or press Win + `

I've tried all combinations of the PowerToys versions listed above along with running as Administrator, rebooting, using the msi or msix installers, and also deleting the zone settings.

Potentially unrelated: the Window Walk also only works for a few seconds at startup before the hotkey does nothing.

Expected behavior

The Zone Editor window is displayed allowing me to interactively configure what will become the Zone settings JSON file.

Actual behavior

Cursor gets a loading spinner while in Task Manager a process named Windows Problem Reporting appears briefly. The PowerToys Settings does not crash and remains functioning normally.

Are there logs or something that I can provide that contain the result of the crash?

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.19041.330]
PowerToys version: v0.19
PowerToy module: Keyboard Manager and Shortcut Guide

Steps to reproduce

Open PowerToys -> Keyboard Manager -> Remap Shortcuts. If PowerToys is already open, disable Shortcut Guide and turn it on again.

Once you are in the Remap Shortcuts window, click '+' to create a new shortcut.

Click Type Shortcut and when prompted, press the Windows key for about 3 seconds, release the key, and Win + VK207 will appear1.

Expected behavior

Clickable windows and a peaceful moment while thinking of a good shortcut key to pair with the Windows key.

Actual behavior

I am unable to click anything on the Remap shortcuts prompt and window and PowerToys window except for the buttons in their title bar. After holding Esc, I can only use Tab/Shift-Tab, Space, Enter (and arrow keys) to navigate the Remap shortcut window and PowerToys window.

My Windows Terminal was also open during this moment, and as soon as the bug appeared, I cannot click the title bar of Windows Terminal to add more tabs but the keyboard and hotkeys for Windows Terminal are still working.

Fixes

A) Turn off Shortcut Guide to temporarily solve the issue.

After hours of figuring out how to consistently replicate the bug , I found out that the Shortcut Guide hotkey (hold Windows key) can conflict the Keyboard Manager when the Windows key is pressed long enough during the input of shortcut combination in the Keyboard Manager -> Remap a shortcut -> Type a Shortcut prompt. Here's a trivial explanation on how to temporarily solve the bug:

Hold Esc to exit the Type Shortcut prompt.

Use Tab or Shift + Tab to navigate to the Cancel button of Remap shortcuts window. Press Enter once the button is navigated to exit the window.

Once in the PowerToys Settings window, use Shift + Tab or Tab to reach the left sidebar. Once there, use the arrow keys to navigate to Shortcut Guide.

Press Enter to go to the Shortcut Guide settings (you may need to press Enter twice).

Navigate to Enable Shortcut Guide and use Spacebar to toggle off Shortcut Guide.

By this moment, everything is back to normal2. The PowerToys window is now clickable, yaay!

B) Run Shortcut Guide at least once every time it is re-enabled.

Just press the Windows key until the Shortcut Guide overlay appears and the bug will not happen anymore after following the above Steps to reproduce. During my investigation, this must be done every time Shortcut Guide is re-enabled in order to prevent future conflicts with the Keyboard Manager during a session.

Notes

This is my first time contributing to an actual project here in GitHub so please guide me. Thank you!

1

The VK207 does not necessarily need to appear because the bug happens even if it does not appear. I am putting the virtual keyboard code because it might give the developers an idea of what is happening here. From what I have observed, pressing the Windows key for the duration indicated in Shortcut Guide -> Appearance and Behavior -> Press duration before showing (ms) is the key to replicate the bug. This bug can also be replicated in the Remap keys option by holding the Windows key during the input prompt.↩

2

I still have no idea why the Windows Terminal was affected by this bug. I guess this has something to do with the unexpected behaviour of Shortcut Guide.↩