Sanity Check: Adobe Acrobat/Reader/Pro Error on Server 2022 VSession Host Environment

Posted by TheKingOfSpite@reddit | sysadmin | View on Reddit | 8 comments

Timeline: 14/01: We push latest server 2022 updates 16/01: Adobe release update, later that day a user from Company 1 creates a ticket for Adobe error "Adobe has encountered an error and some features may not work as expected" and being unable to save PDFs 18/01: User at Company 2 raises a ticket for the same error, this is keeping her from using Password protect. This is in Adobe Pro After blitzing Adobe using AcroClean, and following all info I can find online, I make the connection between the two tickets and investigate. I found that the error is apparent on all tested machines running server 2022 (all are on the same version). Today: I have spent an hour or two trying to debug this with Fiddler, I can see it calling URLs that don't exist when searched, calling multiple ZIP downloads with images and XML files that have been modified anywhere from the 13th to the 17th, I find the this post from a month ago for the same issue in a similar environment (also VSH but doesn't specify further) [https://www.reddit.com/r/sysadmin/comments/18hr5bu/issues\_with\_adobe\_reader\_after\_dec\_windows\_update/](https://www.reddit.com/r/sysadmin/comments/18hr5bu/issues_with_adobe_reader_after_dec_windows_update/) Basically, aside from a fix, is anyone else getting this, is this a confirmed issue?

8 Comments

[-]

memesss@reddit

Was the server 2022 upgraded in-place from 2019/2016? Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ for "rdrcef.exe" or "acrocef.exe" keys (process names mentioned here: https://helpx.adobe.com/acrobat/kb/acrocef-rdrcef-errors.html ), and try renaming those keys if they exist (to disable IFEO for the CEF processes). There is an issue with the January 2024 CU for server 2022 and chromium-based browsers (e.g. chrome, opera, edge, and brave) and webviews (e.g. CEF, electron, and edge webview2). Chromium bug entry: https://bugs.chromium.org/p/chromium/issues/detail?id=1519187 This looks like a patch Google/Chromium is working on which would fix this: https://chromium-review.googlesource.com/c/chromium/src/+/5214980 .

daveeeh2@reddit

Yes! Fixed our issues with Adobe on a brand new Windows Server 2022 RDS Farm. We were just getting a dark screen when adding signatures and having to crash Adobe. Not to mention the many popups about AcroCEF.exe. Thanks for posting this!

alexander0the0gray@reddit

Your comment fixed my issue after three hours of troubleshooting with Abode's useless advice. Thank you!

TheKingOfSpite@reddit (OP)

Nice one, will try this later on

boneclock@reddit

Man. This post just saved me another hour or two of troubleshooting! May the cybergods be in your favor!

BetterITSupport@reddit

At a customer of mine on Wednesday, the comment was made that Acrobat gave that particular error. This customer is working on a 2022 RDS server. All users were getting this error.  I went to check and apparently the recent update (in my case) is the problem. The update: January 9, 2024-KB5034129 (OS Build 20348.2227)  I have removed this update and my Acrobat error problem has also disappeared. The error seems to be related to this Windows update.  Greetings.

This fixed it, cheers

Nice one, will try this later on, thought it might be an update but uninstalling updates is a whole thing for us so wanted to be sure

Reply to Post

8 Comments