Forum Discussion
RunTimeBroker.exe crashing - many machines impacted and crashing taking gigs of space
We are seeing Runtimebroker.exe crashing on 20-30+ machines per day and the crashes are taking up gigs of disk space. Is anyone at Microsoft aware of a fix for this? We opened a support ticket and ...
Hi ArcticMyst
I found this article, obviously not about this application , but maybe it will show the direction , which will help to fix it:
Thanks for reply, already tried but no luck
I would like to mention that every single machine with the crashing has runtimebroker.exe 10.0.19041.746. And also we have hundreds of machines with this same version of runtimebroker.exe which are *not* crashing. Can someone working at Microsoft please confirm what the latest version of runtimebroker.exe is? Is this a known issue? Can someone help escalate our ticket? We gave the actual dump files and query data from defender of the crashes, but despite the specific/actionable data we gave, the support is asking us to provide non-relavant/useless information when the case just needs be be escalated to someone who is an actual software developer
I would like to mention that every single machine with the crashing has runtimebroker.exe 10.0.19041.746. And also we have hundreds of machines with this same version of runtimebroker.exe which are *not* crashing. Can someone working at Microsoft please confirm what the latest version of runtimebroker.exe is? Is this a known issue? Can someone help escalate our ticket? We gave the actual dump files and query data from defender of the crashes, but despite the specific/actionable data we gave, the support is asking us to provide non-relavant/useless information when the case just needs be be escalated to someone who is an actual software developer
I understand, but in MTC - you can get a response from other users, (who are not Microsoft employees)
Try asking a question, a new question in a space I shared earlier.
But, it is worth analyzing the configuration of machines that do not have failures, and then perform a check.
No one will speed up the work of Microsoft support - these are separate spaces
Best regards
"Faulting package full name: Microsoft.Windows.Search_1.14.7.19041"
I re-read this thread and it seems that the problem is due to the incorrect implementation of Windows updates (KB installation is missing) or has been corrupted
