FortiClient 7.0.7 App becoming unresponsive after a few weeks and no longer able to sync with EMS

We are experiencing odd behavior with FortiClient 7.0.7 on Windows 11.  We have been using it successfully for a few weeks now, and the EMS configuration profiles haven't changed, but some problematic issues are beginning to arise.  More and more clients are starting to not sync with the EMS server and therefore can't get updated profile information.  Additionally, the FortiClient App itself becomes unresponsive once you click on either the profile tab OR if you click on the menu under the Zero Trust Telemetry Tab to check the details of the EMS connection status.  You need to close and reopen the FortiClient App to be able to access the other tabs.  I am unable to try  uninstalling/reinstalling the FortiClient software because the policy currently applied does not allow you to quit the App or disconnect from the EMS server.  If I try to uninstall from Windows Add/Remove programs I get a message that it can't be uninstalled because it is managed by an EMS server (I've tried unregistering it from the EMS side, but because the App no longer syncs correctly, the clients think and indicate they are still registered when they are not.  If I try to uninstall using the FortiClient support tools, it says it can't because there is a running instance of FortiClient and that I need to stop it first, but I can't stop it because the applied policy does not let you shut it down.  This same behavior is slowly trickling down to every machine in our environment.

Not sure if this is the cause, but I've also noticed that with 7.0.7 installed our EMS server name/address gets added/listed repeatedly in the "Remembered EMS List" in the client over and over again after each successful connection.  We only have one EMS Server, and it used to only get listed once prior to 7.0.7.  It seems like the problematic machines are the ones that are used more frequently and therefore have our EMS server in the list more times then you can even see in the display.  Not sure if this is causing some kind of memory problem with the App, but the machines where it hasn't been listed as many times (because they haven't connected as much) seem to work fine.

You can see in the image below that the same EMS server is listed over and over again in the Remembered EMS List.  You can also see that the client is stuck in it's last known state, it says it's status is Connected to EMS, it is not, and it also says it is syncing, it is not. 

I've tried unregistering all machines in EMS and having users re-register, but only those machines that were still working properly (the ones that haven't been used as frequently) are able to re-register with EMS successfully, the problematic machines can't re-register because the FortiClient App on those machines still think they are registered.

Thankfully the profiles currently in use are still good so users can still connect to the VPN, but if anything changes in the future they will not receive the configuration changes.

All devices in the environment have the exact same hardware.

Help....