r/Windows10•
fphazer

Bug: UWP Interface Broken, constant input makes interface unusable.

Bug

Sorry to post a bug issue here, but I have not had much luck fixing this issue.

A few weeks ago if found my UWP apps interface all became unusable. The issue behaves as if the interface is constantly receiving input.

Example: Microsoft Edge, if I click the "..." menu in the upper right the menu appears and disappears constantly, and the button flickers as if receiving constant input. Photos, Mail, calculator, all experience the same behavior where I am unable to interact with the interface.

The Settings Panel does work, and does not experience this issue.

Is there some way to default out the UWP interface settings?

I have tried the "Settings --> Updates and Security --> Troubleshooting --> Windows Store Apps -- Troubleshooter" And this did not work.

Any other suggestions would be great.

Thanks

Posted Mar 28, 2018, 2:52 AM UTC

22
aveyo•

(d)com configuration that is probably broken in your os is as close to a black box as it can be, not even Microsoft has working troubleshooters / Fix-it.

The only known 100% solution is Create Windows 10 installation media - Download tool now
Just start the setup over your current installation, it will offer you a choice for what you can keep (files, settings apps).

2
fphazerOP•

I figured out what the issue was. Not a bug. I disconnected all the inputs from the computer and found that there was a button on a game controller that was stuck, and constantly issuing an input, that affected only the UWP apps when in use. Glad to have this fixed.

2
aveyo•

Great of you to follow up!
But was not that implied to first check your input devices, specially if you have game controllers? At least I've implied that.
Thing is, only yesterday I've experienced such bug after a windows update (defender and store) that was 100% dcom, since I've disconnected all devices, only kept mouse, only kept keyboard, and still any context menu's or right-clicking uwp apps was instantly canceled. It just briefly flashed. Yet it worked under Firefox or TotalCmd! So I simply run setup over since it's so fast on 1803, and it went away.

1
fphazerOP•

Thanks! What I feared but at least it is a solution.

1