I killed a LOT of brain cells on this yesterday and today with both Microsoft and Google tech support and the Google tech owned up to the problems with the new version of GWSMO. While I still can't synch my contacts, "airline" mode solution was brilliant. Here's the message that I just received from Google:
"Google workspace synch stopped working with Outlook in Windows 11 24H2. After reviewing the information you provided, we believe that you may be affected by an issue we've become aware of: Using GWSMO version 4.3.73.0 causes the Outlook client to crash. Here are some details about the issue: The customer reported that while using the GWSMO version 4.3.73.0 with Windows 11 machines causes the Outlook client to crash.
There's no workaround available at this time, but we'll let you know if we learn of one. Action Recommended: We are troubleshooting an issue with Outlook client crashing with the latest GWSMO v4.3.73.0. We recommend downgrading to the previous version here: https://tools.google.com/dlpage/gssmo/# ****
We are writing to inform you about an issue some users may be experiencing with the latest version of Google Workspace Sync for Microsoft Outlook (GWSMO) (version 4.3.73.0), where the Outlook client may unexpectedly close or crash, particularly on Windows 10 and 11 machines during contact synchronization. Our engineering teams are actively investigating the root cause of this issue, and this investigation is ongoing.
In the meantime, we recommend that affected users revert to GWSMO version 4.3.68. You can download this version from our official GWSMO download page: https://tools.google.com/dlpage/gssmo/#. All download links on that page point to the previous, stable version v4.3.68.0. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this situation. We will provide further updates as more information becomes available. Sincerely, The Google Workspace Team"
BTW, I tried to do the rollback as they suggested with the provided link but it still doesn't work but maybe it's a rollback user error on my part......thought that their link would be a turn key solution :-(