Replies: 3 comments 5 replies
-
Do you have any scheduled queries in place? That is the most likely culprit. If you have a few, you can start disabling them one by one until the system is stable. |
Beta Was this translation helpful? Give feedback.
-
We have also been having this issue since around early October. So far we have not found a solution outside of removing the osquery agents from our machines. We were also hoping it would be a temporary bug but we still haven't had any luck. |
Beta Was this translation helpful? Give feedback.
-
@PatWhitlock @MDCAllan If possible, can you please share what scheduled queries you have running? Also, I would suggest checking in with the osquery Slack - https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
About 2 months ago we started getting reports of the Teams app randomly closing(crashing?) on computers in our environment. We traced the problem to the fleet/osquery agent deployed to the computers. When we disable the LauncherSoLauncherSvc on computers, Teams works normally without randomly closing/crashing.
I was expecting this was probably going to be a temporary bug that would get discovered and resolved along the way, but so far, the problem persists.
I'm wondering, has anyone else had this problem, and is there a way to resolve it without disabling the agent service? Also, where would I go to report a bug related to this service? I am already in contact with Microsoft to work the problem, and they are looking into it from their end, but I'd like to get eyes on the problem from the other side as well.
Thanks for any ideas/input!
Regards,
Eric
Beta Was this translation helpful? Give feedback.
All reactions