Error Windows server 2016 "SetThreadDescription" "AdobeCollabSync.exe"

[Patriopat]

Hello,

We are experiencing a persistent issue on a Windows Server 2016 Datacenter (version 1607, build 14393.7969) running in a multi-user RDS environment.

Error message when user open Adobe reader x64 25.001.20474 :

"AdobeCollabSync.exe - Entry Point Not Found
The procedure entry point SetThreadDescription could not be located in the dynamic link library C:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeGrowthSDK.dll."

Actions already taken:

• Repair and Reinstall Adobe

• Removed all startup entries related to AdobeCollabSync.exe from:

  • HKCU\Software\Microsoft\Windows\CurrentVersion\Run

  • HKLM\Software\Microsoft\Windows\CurrentVersion\Run

  • HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run

• Searched the full registry for any reference to:

  • AdobeCollabSync.exe

  • Adobe Acrobat Synchronizer

  • AdobeGrowthSDK.dll

• Checked Task Scheduler for CollabSync entries – none found

• Confirmed that SetThreadDescription exists on the system via PowerShell and kernel32.dll

• Rebooted the server and sessions after all modifications

Despite all these steps, the error still appears. It seems Acrobat Reader attempts to launch AdobeCollabSync.exe internally regardless of startup configuration.

Thanks in advance for any insight or recommendations.

[AnandSri]

Hello @Patriopat!

I hope you are doing well, and thanks for reaching out.

You've already taken extensive steps—repairing and reinstalling Adobe, cleaning registry entries, and confirming SetThreadDescription exists in kernel32.dll. Here's what the evidence suggests and what you can try next:

Root Cause: 

The function SetThreadDescription is only available on Windows 10 version 1607 and later, but only with specific updates. While your server is technically version 1607, it may lack the Windows API support required by newer Adobe DLLs like AdobeGrowthSDK.dll.

The AdobeCollabSync.exe process attempts to call SetThreadDescription, which fails if the OS build doesn’t fully support it. 

Workarounds: 

Update Windows Server 2016: Ensure your server has the latest cumulative updates. Even though you're on build 14393.7969, Microsoft may have released patches that improve compatibility with newer APIs.

Disable AdobeCollabSync.exe: If you don’t use Adobe cloud sync features, you can disable or rename the executable: 

• Navigate to:

  C:\Program Files\Adobe\Acrobat DC\Acrobat\
  

• Rename AdobeCollabSync.exe to something like AdobeCollabSync-disabled.exe.

This prevents the process from launching without affecting core Reader functionality.

You can also check and refer to these discussions on a similar topic and try the suggestions: Solved: Unfortunately, AdobeCollabSync.exe is one of Adobe... - Adobe Community - 10718289

AdobeCollabSync.exe Start Booting Problem - Microsoft Community

If you still experience the issue, please share the logs from the affected machine with us. Download the log collector tool, run it, ensure all the log options are selected, try to reproduce the issue, and close the log tool. It will generate the logs and the log ID. Please share them with us for further investigation.

Thanks,

Anand Sri.

[Patriopat]

Perfect, thank you!

An update is scheduled to run on the server tonight, so I’ll let you know if the issue persists afterward.

If we rename AdobeCollabSync, would a future Adobe update restore the functionality and recreate the file?

[AnandSri]

Hello @Patriopat!

Thank you. Do let us know the status. 

To address your question, yes, if you rename or delete the file, a future Adobe Acrobat update will likely reinstall or restore the original file. Adobe's installer and updater typically verify the integrity of core program files, so any renamed or missing components may be replaced during updates.

If you want to permanently disable AdobeCollabSync.exe, it's better to manage it through startup settings, Task Scheduler, or Group Policy (in enterprise environments) rather than relying on file renaming, which is only a temporary workaround.

Thanks,

Anand Sri.

[nicolas_7600]

Curious, did you resolve this?

[nicolas_7600]

Following this thread.

I am running into this same issue. It is also on a Windows Server 2016, with the same build number.

It is also the same Acrobat version as ours. This also a multi-user enviroment.

Any resolution?

[AnandSri]

Hello @nicolas_7600!

Thank you for reaching out. Please try the registry setting shared in this community thread, and let us know if that works for you. 

If you still experience the issue, please share the logs from the affected machine with us. Download the log collector tool, run it, ensure all the log options are selected, try to reproduce the issue, and close the log tool. It will generate the logs and the log ID. Please share them with us for further investigation.

Thanks,

Anand Sri.

[nicolas_7600]

Our last step included removing and deleting the entire contents of the users %APPDATA%/LOCALROAMING/ location. Once I cleared the contents of that directory, I had the user reconnect to the Terminal and it repopulated the contents. The user attempted to open multiple files and the error never appeared.

Waiting to verify if the issue resumes tomorrow and will update this post.

[nicolas_7600 · Accepted solution]

This has fixed the issue on my end. 

I had to schedule a time to disconnect a user from a session on a terminal. Once the user was disconnected, I proceeded to delete all ADOBE folders that were located in each user's APPDATA/LOCALROAMING/.

Once I removed those folders, I had the user sign in and the error only appeared once more. After they cleared the error, it appears to have fixed it, and the error has not appeared for a full week.

The folders are re-created when the user signs in, and appears to clear the error from appearing.

[AnandSri]

Hello @nicolas_7600

Glad to know that the issue got fixed, and thank you for trying and sharing the steps which worked for you. Thank you for your time and cooperation. Please feel free to reach out if you need any assistance.

Regards,

Anand Sri.

[Patriopat]

We are still experiencing the same issue.
I renamed the file this morning, but Adobe regenerated the original file later the same day.

We are currently exploring the possibility of disabling it via Group Policy (GPO), but we would prefer that Adobe investigate and resolve the root cause of the problem.

[hannese29464685]

Same issue here on 3 Windows 2016 Terminal Servers multible users affected

[jonathan_7463]

Hello,

I made it working by running a script every hour 🙂

cd "C:\Program Files\Adobe\Acrobat DC\Acrobat\"
ren AdobeCollabSync.exe AdobeCollabSync-old.exe

[hannese29464685]

Not really a prober solution.

[AnandSri]

Hello!

I hope you are doing well, and thanks for reaching out.

Have you tried the suggestions shared above? If not, please try once and let us know if that works for you. Please ensure you have the latest version of Acrobat installed on the machine: 25.001.20531 (Win), planned update June 10, 2025. 
Check for any pending updates from the Menu > help > check for updates, install the updates, restart the app and the machine, and try again.

If the issue continues, please provide the following information: the current version of the operating system on your device and the logs from the affected machine. To collect the logs, download and run the Log Collector tool. Make sure to select all log options and attempt to reproduce the issue. After that, close the Log Collector tool; it will generate the logs along with a log ID. Please share this log ID with us for further investigation.

Thanks,

Anand Sri.