I've encountered another problem after a recent Microsoft Office update on our Remote Desktop Services (RDS) 2016 servers. Specifically, after updating to Build 19328.20158, we're unable to open Word at all. The error message reads: "The procedure entry point SetThreadDescription could not be located in the dynamic link library C:Program Files (x86)Microsoft OfficerootOffice16wwlib.dll." As usual, we've found that turning off automatic updates and reverting to the previous version (which is 19328.20216) is a good workaround. I wanted to share this to warn anyone who might be using similar server setups before it affects them! Luckily, it only impacted five servers before we caught it, but it sure disrupted what was supposed to be a peaceful Friday workday!
5 Answers
You might want to try setting your target version to 19231.20216 instead since 19328.20216 has been problematic for a lot of folks. I had a similar issue with Outlook errors popping up when trying to view new emails after this update.
I'm facing the same problem with rolling back to an older version on our RDS servers. I set an older version in the configuration file, but it keeps installing the latest. Any suggestions?
Make sure to fully download the Office package with the Deployment Tool and then configure it; that helped in my case.
I spent around four hours trying to fix this by uninstalling and reinstalling Office, plus applying the latest cumulative updates. To roll back to that specific Office version using the Office Deployment Tool, you can check out this link: [Microsoft Support Guide](https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841). That's how I did it!
For those dealing with this, I found running a command as an admin works to revert the Office version. Open CMD and type the following commands: 1. cd %ProgramFiles%Common FilesMicrosoft SharedClickToRun 2. OfficeC2RClient.exe /update user updatetoversion=16.0.19231.20156. This rolls it back to an earlier version. After that, just disable updates to avoid future issues.
I tried that, and it worked! Thanks for the tip!
This really saved my day, appreciate it!
I was in the same boat! This post kept me from wasting more time troubleshooting. We had to uninstall and then reinstall an older version on our server, plus we switched to the Monthly Enterprise channel to avoid these problems. Also, watch out for firewalls that might block your installer—it was a big issue for us since we had content filters in place.
That happened to me as well. I did an online repair after setting the version, and it finally worked!