# Bitlocker with Pin and windows updates. — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/a708052de4ea35b1

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-11-18 22:09 ingested 2026-11-19 02:38

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1xzsdox/bitlocker_with_pin_and_windows_updates/)

## retained text



```
Looking for second opinions. I work with US government systems. This is on a specialized off line network with limited access to normal COTs or cloud systems. I've been tasked with implementing full disk encryption with TPM and PIN data at rest protection and to also minimize impact on users.

To solve this I automated the roll out of bitlocker along with shutdown and startup scripts. When a system shuts down, the shutdown script runs and if the shutdown was a restart, it suspends bitlocker protection. This was done to allow updates to apply over a number of reboots without failing at the bitlocker pin screen. Then when the system starts it runs another script to resume protection. 

The prototype on a development network is already done and now management is unhappy because they believe the data is not being protected. Which is maybe arguable. They instead want to pivot to network unlock. Except this organization does not use DHCP and doing so would require major changes.

Lastly, the design I did has already passed an inspection and does not violate any government rules I know of.

Is there a better way to deal with reboots in a TPM+PIN setup? I'm probably going to have to argue my case tomorrow.

Edit: Do not just run this request through AI. I have access to AI too and I know what it will say already.
```



document fetched 2026-11-19 00:38 · canonical https://reddit.com/r/sysadmin/comments/1xzsdox/bitlocker_with_pin_and_windows_updates
