Windows
SentinelOne and DNSfilter were missing after Autopilot
A newly set up Windows computer finished Autopilot without SentinelOne or DNSfilter installed. The technician reported that the machine now has both installed; the likely blocker was a legacy script that installed a conflicting antivirus and stopped the download.
Killed once by someone from XL.net, on 2026-03-11.
Affects
Apps
- Autopilot
- SentinelOne
- DNSfilter
What you see
- SentinelOne is not installed after Autopilot setup.
- DNSfilter is not installed after Autopilot setup.
- A different antivirus was installed by a legacy script during provisioning.
Why it happens
Likely A legacy provisioning script likely ran during Autopilot and installed a conflicting antivirus, which prevented SentinelOne and DNSfilter from downloading.
When it shows up
A Windows device completes Autopilot but the expected endpoint tools are missing and another antivirus appears instead.
You are in this case if:
- SentinelOne is absent after provisioning.
- DNSfilter is absent after provisioning.
- A legacy Autopilot script installs a different antivirus during setup.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Keeping it away
- Remove or retire legacy provisioning scripts that install conflicting antivirus software before the next Autopilot setup.
Someone from XL.net killed this on a Windows computer on 2026-03-11. It is written up from that one repair, so it cites no outside page.