Quique M

I found a workaround to this, working at least in my case. I hope this helps to others to fix this bug/issue. In my case, the Elevated property is always set to "No" for both Outlook and GCSM processes. So, same user and same elevation level always. Also, I always had an OUTLOOK.EXE process already in memory. So, when GCSM starts and tries to sync, it creates temporarily (a few seconds only) another second instance of OUTLOOK.EXE (again, same user and not elevated) that suddenly disappears just before...

I found a workaround for this issue, at least working for me: https://sourceforge.net/p/googlesyncmod/bugs/1413/#b169

I found a workaround for this issue, at least working for me: https://sourceforge.net/p/googlesyncmod/bugs/1413/#b169

I found a workaround to this, working at least in my case. I hope this helps to others to fix this bug/issue. In my case, the Elevated property is always set to "No" for both Outlook and GCSM processes. So, same user and same elevation level always. Also, I always had an OUTLOOK.EXE process already in memory. So, when GCSM starts and tries to sync, it creates temporarily (a few seconds only) another second instance of OUTLOOK.EXE (again, same user and not elevated) that suddenly disappears just before...

I am having EXACTLY the same issue here, after installing latest version of GCSM (4.2.1) in Windows 11. I have also confirmed both applications (OUTLOOK.EXE and GCSM executable) are both launched by the same windows user (my standard user). I've tried reinstalling a few times, but still same errors. I've been using GCSM since 2020 and first time seeing this error.

I am having EXACTLY the same issue here, after installing latest verion of GCSM. I am Windows 11 user: