New
#510
Yes, and I think that it's this: Win32 apps aren't supposed to be suspended.
"Traditional desktop applications have only two states: they are either running or they are not running. UWP apps have a third possible state called suspended."
I wonder if some of the new features that they've been laying groundwork for, like Sets and Timeline, are inadvertently responsible for this.
The next problem to solve, since we'll be living with 17046 for perhaps another week or more, is why I have so many dllhost.exe (the infamous COM Surrogate) application errors in this build. It's tripping over a part of Office called mso20win32client.dll several times a day and is very annoying. There's a lot of history to search through for that one.