After installation of PGP Desktop 10.3.2 MP13 on brand new HP 820 G3's Windows updates installation of new cumulative patches will take 20ish hours to complete.
The computers will stay at the blue patch screen at "Completed 72%" to "Restarting" for almost one day. Apart from extremely slow patching the computer performance is totally normal. PGP is just used for email encryption and all other functionality are disabled by server policy. All computers disks are encrypted by BitLocker.
The conclution that it is PGP that brakes Windows Update is based on a 30 user PoC where 10-ish computers with problems have PGP Installed and 20ish computers without PGP doesnt have these problems. Extensive testing of 4 computers revealed that with just PGP Desktop installed patching failed.
All HP 820 G3 computers have i5, 8 GB Ram, SSD, Windows 10 Enterprise x64, BitLocker, deployed by SCCM and patched thru SCCM/WSUS. For testing patches has been applied by running the msu files directly.
For testing we have also installed PGP Desktop on a HP 820 G1 (i5, 8GB, SSD, Windows 10 Enterprise x64, BitLocker) with same result and a standalone version of PGP Desktop (without server policies) on a HP 820 G3 also failing Windows Update after PGP installation.
As I can't find any reports of this kind of problems on the Internet I started to think there might be problem when BitLocker is used for disk encryption and PGP Desktop is installed as this might be a rare combination. To verify this I took a standard 820 G3 installed as described above, turned off BitLocker and let the disk be decrypted, installed PGP Desktop and installed next Cumulative patch. Its now one hour since I manually started the installation of KB3206632 and its still at "Working on updates - 71% complete". So this seems to be another dead end.
We need a solution. The usage of BitLocker is a Company Policy and about one third of our users need PGP encryption of emails.
Having 100 users computes in an unusable state for 24 hours once a month isn't very productive...
