2 ms·
> clearly the crashed process was considered so vital that the UI had to wait for it This is not a case of it being important enough, this is the case for ever
by alt227 4y ago
> clearly the crashed process was considered so vital that the UI had to wait for it
This is not a case of it being important enough, this is the case for every single application:
https://devblogs.microsoft.com/oldnewthing/20120611-00/?p=7413 https://devblogs.microsoft.com/oldnewthing/20120611-00/?p=74...
- alkonaut 4y agoI mean that RuntimeBroker.exe was considered so important that the UI process (Explorer.exe?) couldn't proceed to show the start menu while it wasn't running, and instead had to wait for it to run. That RuntimeBroker couldn't restart until the last instance was dumped is what's true for all processes. But that doesn't explain why the UI block waiting for it and not show the start menu. RuntimeBroker may be required to show the complete/correct start menu because it relates to app permissions for store apps and similar, but Microsoft (again) likely overestimated the importance of their app store.