Settings Screen is blank
See original GitHub issueEnvironment
W10 Pro V1903 Build 18362.295 PowerToys: 0.11.0 Settings Screen
Windows build number: [run "ver" at a command prompt]
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):
Steps to reproduce
Just installed and attempted to open settings. Screen is totally blank/empty. I 'repaired - same issue. Uninstalled, reboot and reinstall - same issue.
Expected behavior
Expect to see config options
Actual behavior
Blank window.
Screenshots
Issue Analytics
- State:
- Created 4 years ago
- Reactions:23
- Comments:236 (92 by maintainers)
Top Results From Across the Web
why is settings screen blank
1. Disconnect the USB cable from the iPhone, iPad, or iPod touch and leave · 2. Turn off the device: Press and hold...
Read more >Troubleshooting black or blank screens in Windows
If your computer is showing a black or blank screen in Windows, these troubleshooting tips could help get your system back up and...
Read more >Blank screen in settings App
Power off your phone. Hold down volume down+power button. ... choose wipe data and cache, and then choose wipe cache. Select reboot. Hopefully...
Read more >Windows 10 update screen blank in settings Fix - YouTube
Windows 10 update screen blank in settings Fix. 11K views · 2 years ago ...more. The Geek Page. 87.4K. Subscribe. 87.4K subscribers.
Read more >How to Fix iPhone Blank Screen
Hold the "Volume Down" button and release it. Step 2: Hold the "Power" button until the Apple logo appears. Your iPhone is now...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The fix will be in the 0.18 release, it is being tested right now.
Ok, just tried 0.18 and the issue is fixed for me.