FDESetup popup after Global Protect client update on macOS

[Otar_Chomakhidze]

Hello everyone,

After users update the Global Protect VPN client from version 6.2.4 to 6.2.5, all users get "fdesetup" popup on their macOS devices, please see the attached.

It does not matter if the user clicks OK or "Don't Allow", the popup comes back again and again and it is annoying. And by clicking OK, it actually does not encrypt the drive or do anything.

Looks like the command "fdesetup" is deprecated by Apple.

The only fix so far is to downgrade the client app back to 6.2.4.

Reference to the "fdesetup" command: 

https://support.apple.com/guide/deployment/manage-filevault-with-mdm-dep0a2cb7686/web

Please advise.

Thanks,

Otar

[Otar_Chomakhidze]

Additional screenshot for the process

[BPry]

@Otar_Chomakhidze,

This appears to be a bug in GlobalProtect that you might want to report just so that they're getting more tickets about it and therefore more eyes onto the matter. So far, I've only been able to replicate the issue if you have FileVault disabled for some reason. I haven't had reports of this popping up when FileVault is enabled and I haven't been able to replicate on any FileVault enabled machines.

[Otar_Chomakhidze]

That is correct, we are getting complaints only from the users who do not have FileVault enabled. 

[Dirk_Melchers]

Could this be the issue / fix in 6.2.6:
GPC-21247: Fixed an issue where GlobalProtect HIP set the Filevault encryption status to unencrypted on macOS running devices, which denied access to the end-point machines.

[JoeCheng]

MacOS GlobalProtect upgraded 6.1.4 to 6.2.5.

I also encountered the same problem. ==It does not matter if the user clicks OK or "Don't Allow", the popup comes back again and again and it is annoying. And by clicking OK, it actually does not encrypt the drive or do anything.

[Otar_Chomakhidze · Accepted solution]

We decided to update the GP client to version 6.3 and it resolved an issue. Looks like 6.2.5 has a bug and in later versions it is fixed.

[Otar_Chomakhidze]

Could be. We did not test that 6.2.6 version, we decided to go with version 6.3 and it resolved the issue, no more fdesetup popups since the update.