You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2020. It is now read-only.
I just wanted to try this with the normal not test-signed version and after launching the program and granting it elevated permissions the process closes immediately again and the normal Windows 10 OSD stops working too until I reboot. Could this be incompatible with Windows 10 2004 Build 19041.329?
The text was updated successfully, but these errors were encountered:
(To restore Windows 10 OSD you could simply restart explorer.exe, no need to restart the machine)
So the app crashes before creating the window (but after hiding the OSD). Did you test the normal ("AudioFlyout.zip") one, right? If it crashes too, it means there is an issue with GSMTC or when enumerating audio devices.
Also I heard that GSMTC as WinRT api is broken in 19041.x (doesn't get notified when an app closes SMTC (e.g. when you close Groove Music))
(To restore Windows 10 OSD you could simply restart explorer.exe, no need to restart the machine)
So the app crashes before creating the window (but after hiding the OSD). Did you test the normal ("AudioFlyout.zip") one, right? If it crashes too, it means there is an issue with GSMTC or when enumerating audio devices.
Also I heard that GSMTC as WinRT api is broken in 19041.x (doesn't get notified when an app closes SMTC (e.g. when you close Groove Music))
Ah I did try to restart ShellExperienceHost but that didn't work so I thought maybe DWM itself was handling the OSD, interesting that Explorer handles that too, the more you know.
Yes I did try the normal one, I didn't even bother with the other seeing that the normal one didn't work but if it helps you I would try it too. It crashes like you said, after hiding the normal OSD but before doing anything else. Any log files I can send your way or any other way I can help?
I just wanted to try this with the normal not test-signed version and after launching the program and granting it elevated permissions the process closes immediately again and the normal Windows 10 OSD stops working too until I reboot. Could this be incompatible with Windows 10 2004 Build 19041.329?
The text was updated successfully, but these errors were encountered: