I think I may have uncovered a bug with Trellix FRP. We have Trellix FRP (version 5.4.3.170) deployed to a series of servers that run internal application which generates files for ACHs . The keys and the policies are assigned to the Servers themselves. We were having some intermittent problems where the servers were losing the ability to read the encrypted files that contained the bank account information. We determined that the issue occurs after the servers are patched (they are running Windows Server 2019) and rebooted. Once the servers are restarted this way Trellix FRP is not able to read the encrypted files until someone logs onto the servers (console or RDP). As soon as the user session is created, Trellix FRP (and the bank file creation application) works normally. The user does not need to stay logged on either. All that needs to happen to get Trellix FRP to start working after a reboot is for a member of the IT group to log on, and then log off. The users in question is not a member of any group that is even authorized to use Trellix FRP. Is this a known issue? Does some part of Trellix FRP need to have an interactive logon session created in order to start working? Our Trellix FRP implementation only went live in February, so it took some time to track down the specific triggers.