Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
6

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

Community Beginner ,
May 30, 2025 May 30, 2025

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.

TOPICS
General troubleshooting , Install update and subscribe to Acrobat , PDF
28.3K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
1 ACCEPTED SOLUTION
Community Beginner ,
Jun 17, 2025 Jun 17, 2025

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.

View solution in original post

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 30, 2025 May 30, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 02, 2025 Jun 02, 2025

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?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 02, 2025 Jun 02, 2025

Hello @Patriopat!

 

Thank you. Do let us know the status. 

To address your questionyes, 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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 18, 2025 Jun 18, 2025

Curious, did you resolve this?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 04, 2025 Jun 04, 2025

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?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 05, 2025 Jun 05, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 11, 2025 Jun 11, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 17, 2025 Jun 17, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 18, 2025 Jun 18, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 01, 2025 Jul 01, 2025

It appears that this issue has arrisen on our secondary TS server. I have repeated the same fix for the previous TS server and it is not working with the new TS.

 

Is there any update regarding when a patch will be applied to fix this? It seems odd to recieve technical advice from Adobe to Disable packages that are included with their software. This seems like a poor and temporary solution that will lead to greater issues in the future.

 

A little more transparancy with the community is desired. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 01, 2025 Jul 01, 2025
  • TS1: Version 1607 OS Build 14393.8148
  • Adobe Acrobat (64 bit) 25.001.20531
  • Adobe Genuine Service 9.0.0.29
 
  • TS2: Version 1607 IS Build 14393.8148
  • Adobe Acrobat (64 Bit) 25.001.20531
  • Adobe Genuine Service: 9.0.0.29

 

The error has remained resolved for the TS1 server, but has now started being an issue for TS2.

The repeated resolution did not work for the TS2, and I am back where we started.

 
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 04, 2025 Jul 04, 2025

Greetinx,

I made a CMD script to do this task, please check outside production:

Userpath: C:\Users\USERNAME\AppData\LocalRoaming\Adobe

 

CMD:

@ECho off
setlocal enabledelayedexpansion

REM Root directory for user profiles
set "USERPROFILES_ROOT=C:\Users"

REM Target subfolder to delete
set "TARGET_SUBFOLDER=AppData\LocalRoaming\Adobe"

echo Searching for folders to delete...

for /d %%G in ("%USERPROFILES_ROOT%\*") do (
set "TARGET=%%G\%TARGET_SUBFOLDER%"
if exist "!TARGET!" (
echo Deleting folder: "!TARGET!"
rmdir /s /q "!TARGET!"
)
)

echo All done.
pause

 

Best, 

Alf

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 22, 2025 Jul 22, 2025

Here's another script I set up with logging as well going after the other approach of renaming AdobeCollabsync.exe.

 

It has a couple of Checkers as renaming will only work until Adobe re-inserts that file, so my script will rectify that:

 

#########################################################################################
###Check AdobeCollabSync.exe for rename, if exists = rename to AdobeCollabSync-OLD.exe###
###Created 07/14/2025 #########
#########################################################################################
 
$FilePath = "c:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeCollabsync.exe"
$NewName = "c:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeCollabsync-OLD.exe"
$Test = Test-Path  "c:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeCollabsync.exe"
$TestRename = Test-Path "c:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeCollabsync-OLD.exe"
$Date = Get-Date -Format "dd:MM:yyyy_hh:mm"
 
 
if ((($test) -and ($TestRename)) -eq 'true'){
    Write-Host "Both Original and renamed files exist"
    Add-Content -Path "C:\%WorkingRepo%\Log\ScriptLog.txt" -Value "$Date Both files exist, removing original"
    taskkill /IM 'AdobeCollabsync.exe' /F
    Remove-Item "c:\Program Files\Adobe\Acrobat DC\Acrobat\AdobeCollabsync.exe" -force
}
if (($test) -eq 'true') {
    taskkill /IM 'AdobeCollabsync.exe' /F
    Set-Location "c:\Program Files\Adobe\Acrobat DC\Acrobat"
Rename-Item "AdobeCollabsync.exe" "AdobeCollabsync-OLD.exe"
    Add-Content -Path "C:\%WorkingRepo%\Log\ScriptLog.txt" -Value "$Date File Name changed"
}
else {
    write-host "File Name is unchanged"
    Add-Content -path "C:\%WorkingRepo%\Log\ScriptLog.txt" -Value "$Date File Name Unchanged"

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 05, 2025 Jun 05, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 11, 2025 Jun 11, 2025

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

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 12, 2025 Jun 12, 2025

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

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 12, 2025 Jun 12, 2025

Not really a prober solution.

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 13, 2025 Jun 13, 2025

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 27, 2025 Jun 27, 2025

Continuo con el mismo problema y la version es 20531

podeis ayudarnos

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 30, 2025 Jun 30, 2025

Hi,

 

did you try the following:

- Replace the file with a dummy.exe (e.g. https://github.com/Flightkick/DummyExe)

- Add another admin user (all rights granted), just in case you need to deliberately delete it when errors occur during updates

- Deny write/change etc. for all users incl. Administrator (the user, not the group)

 

Adobe Reader DC should not be able to "repair" it. 

 

This should help until Adobe eventually cares and delivers the due fix for 1607 based systems.

 

brgds

FortiSecond

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 02, 2025 Jul 02, 2025

Any updates from Adobe regarding this issue?

 

It seems to be affecting multiple users, and the only solution provided is a third-party app to end any tasks generated from Adobe's software.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 24, 2025 Jul 24, 2025

news?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 24, 2025 Jul 24, 2025

Solved it myself.

 

Resolution is on a different comment thread, follow my steps.

 

I don't enjoy providing free labor for something Adobe should be able to provide.

 

Good luck! 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 28, 2025 Jul 28, 2025
LATEST

In my opinion, the temporary solution you provided is not optimal for these reasons: deleting the Adobe folders from %APPDATA% or %LOCALAPPDATA% will not resolve the underlying error, which is caused by incompatibility between the Adobe application and the operating system, not by temporary files or user cache.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines