

We are going to resume protectors at that event: When updates are installed an Event ID 1042 is issued The second Scheduled Task is similar except Event ID we monitor and action. When MSInstaller starts Windows Updates it generates Event ID 1040Īt that event we want to run a command to suspend protectors on C:

We need to create two scheduled tasks (either locally or using GPO): To do that you can use Scheduler and monitor for Windows Updates event. To avoid that you can disable protectors for update time and re-enable them after.

Sometimes Microsoft updates can introduces changes locking the machine. This was shared by one of Microsoft Support Engineers. Here is an elegant technique to automate Bitlocker protectors disable while Microsoft updates are installing.
