Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

osquery.png

this has never happened before, after thousands of osquery deployments. i ran `msiexec /i C:\Windows\Temp\osquery-4.0.2.msi /qn` on a windows 10 endpoint, and it restarted the endpoint

<@U6EFFT5FG> <@UF63BUA3A> possible issue with new packaging?

Is this an upgrade or a new deployment?
I've only seen reboot required when Windows wasn't able to stop the previous running service.

It seems it should be possible to append `REBOOT=ReallySuppress` to the installation command and block that behavior, unless it's a custom action.
We can have a look into it but I don't think something custom is there.