[mdt] 1903 Task Sequence blocked by Windows Defender!!!!

[FragglePete]

Just fine tuning my new 1903 image, GPOs, etc along with the MDT Task Sequence but noticed on a couple of older machines that the sequence just stops after the initial windows os install. Reboots and just drops to the desktop - as if it's forgotten what to do next.

 

Then, saw that Windows Defender had blocked a threat!!! The threat being the script that starts the next phase of the sequence! Now, I need to check everything but really.... How has this happened?

 

 

Pete

[FragglePete]

Just pulled off the scripts that the machine had copied to the C:\MININIT\SCRIPTS folder and virus scanned them with Sophos - all clear. If I restore the file on each device and restart, the sequence carries on and works normally. So, Windows Defender has taken offence to Microsoft's own script!

 

Interestingly, a newer model of PC works with no issues.

 

How to fix this? Recapture my base image (which doesn't really have much on it!)? At least it might have a more up to date Windows Defender Database.

 

Pete

[Pauljm]

I am getting the exact same issue suddenly today both on virtual and new PC's. Did you find an answer to this?

[free780]

There's another thread with the same issue. Is it worth disabling defender within the answer file via reg setting. You can turn it back on via GPO if you use it. You may need a staging OU where defender is disabled.

I'm also curious as to why people are choosing 1903 when 1809 has been out longer and will be supported for a longer time.

Edited July 18, 2019 by free780

[Arthur]

I'm also curious as to why people are choosing 1903 when 1809 has been out longer and will be supported for a longer time.

Apparently 1909 will be a CU for 1903 so it will be supported longer than 1809.

Edited July 18, 2019 by Arthur