Hi arvindy, We were previously given a workaround that required changing the “launchCollabSyncInLowIntegrity” key from a value of “1” to “0”. [Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe Acrobat\DC\FeatureState] However, product updates change the value back to “1”. Will the registry edit you describe in message 29 not get overwritten by future product updates (assuming those updates still do not include the permanent fix)? Additionally, you described this registry edit as a “fix” and used the phrase “resolves the issue.” This is a workaround. The issue will be fixed when an update to the product permanently resolves the issue. We have a large, dispersed team of reviewers. Asking all of them to edit their registry is not feasible. In some cases, they don’t have adequate permissions. In December, we were told by Adobe that the permanent fix for this bug had “been delayed until late spring due to a dependency on a Microsoft bug fix, which is needed as part of the Adobe fix.” Can we still expect the fix by late spring? Thank you, Sean
... View more