@john thanks for letting us know! It may well still be an issue, but was alleged to have been remediated a while ago. If you can successfully cause osqueryd to still be running, while the service state has been thrashed, please open an issue and our teams will take a look. We have an integration test that simulates rapid test stops and starts, and checks for residual osqueryd.exe processes after each run, and this test has consistently been passing on master, so I'm under the impression this is no longer an issue, but we can definitely take a look, as that bug was pretty terrible and we'd wanna ensure that it's completely fixed 🙂