Citrix - Installation Error DVCRenderingAdapter.dll Failed to Register

Share on:

I recently was troubleshooting the following error on roughly 400 systems that we were deploying the Citrix Receiver v14 to:

Citrix Receiver DVCRenderingAdapter failed to register, Image Credit Christopher Cable from Citrix Discussion Forum

CustomAction +DVCRenderingAdapter.dll.827545C6_7013_4DE1_8E6C_DAEE4C57F54A returned actual error code -2147319780 (note this may not be 100% accurate if translation happened inside sandbox)MSI (s) (5C:9C) [10:08:57:789]: Product: Online Plug-in -- Error 1904. Module C:\Program Files\Citrix\ICA Client\DVCRenderingAdapter.dll failed to register.  HRESULT -2147319780.  Contact your support personnel. Error 1904. Module C:\Program Files\Citrix\ICA Client\DVCRenderingAdapter.dll failed to register.  HRESULT -2147319780.  Contact your support personnel.

There are a few discussion board posts online that discuss this issue and provide some helpful tips for manually fixing the issue.  Ones that helped me the most was this response by Mike Moskal on the Citrix Discussion Board.

Update (2018-05-15): One of our awesome commenters pointed out that Citrix published a support article on this in March of 2018. You can find that here.  I would absolutely recommend you test Citix's solution before mine going forward.  Thanks zarkers!

In researching, I came to the same conclusion as Mike - that we need to update the permission on a number of keys in HKCR in order to resolve the issue.  I also used Process Monitor and watched for Access Denied errors.

In that same post, user "Testus Test" (I'm going to go ahead and guess that's a fictitious name...) said there must be a better way than to have to manually adjust the permission to resolve this problem.  As I had had quite a few to fix myself, I created the batch file below to include in the rollout to resolve the problem.

This batch file requires SetACL.exe from to be located in the same folder in order to work.  If you find this does not resolve the issue for you, I suggest you use Process Monitor from SysInternals to see what additional registry keys you may have to change the permission on and then add them to the batch file.

 1@echo off
 3REM Christopher Kibble.  March 1 2016. 
 4REM Always test in a development or test environment before using in production.
 6REM Script requires SETACL from
 8"%~dp0setacl.exe" -on "HKCR\Interface\{A1230201-1439-4E62-A414-190D0AC3D40E}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
 9"%~dp0setacl.exe" -on "HKCR\Interface\{A1230201-1439-4E62-A414-190D0AC3D40E}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
11"%~dp0setacl.exe" -on "HKCR\Interface\{A1230203-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
12"%~dp0setacl.exe" -on "HKCR\Interface\{A1230203-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
14"%~dp0setacl.exe" -on "HKCR\Interface\{A1230205-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
15"%~dp0setacl.exe" -on "HKCR\Interface\{A1230205-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
17"%~dp0setacl.exe" -on "HKCR\Interface\{A1230204-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
18"%~dp0setacl.exe" -on "HKCR\Interface\{A1230204-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
20"%~dp0setacl.exe" -on "HKCR\Interface\{A1230206-9A39-4D58-8674-CDB4DFF4E73B}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
21"%~dp0setacl.exe" -on "HKCR\Interface\{A1230206-9A39-4D58-8674-CDB4DFF4E73B}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
23"%~dp0setacl.exe" -on "HKCR\Interface\{A1230207-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn setowner -ownr "n:%computername%\Administrators" -rec yes
24"%~dp0setacl.exe" -on "HKCR\Interface\{A1230207-D6A7-11D8-B9FD-000BDBD1F198}" -ot reg -actn ace -ace "n:SYSTEM;p:full" -rec yes
26exit 0



Hi christopher, Thank you for sharing ! I tried your method to install Citrix Receiver but I don't manage to make it... I downloaded SetACL.exe and managed to run it with the script you gave but it didn't solve the problem. Then I downloaded Procmon in order to identify the remaining blocking registry keys but I don't really manage to locate the good lines. After applying many filters to exclude many of the non wanted lines, I see a few lines related to Citrix I guess (TrolleyExpress.exe) but don't really understand waht to do next... (most of these lines are related to a reg keyt named HighContrastMode : not sure that will help...)

Could you please help me ?

I managed to install citrix receiver on one of my VMs but It is not handy at all...


I got the same error (with the only difference that the HRESULT was -2147024770) while installing Citrix Receiver 4.11 onto Windows 7. I had to install 4.10 instead.

Nicolai Erchadi

During Installation of Revceiver 4.11 I got the Failure-message: "Failure during Registration of Modul: c:\programmFiles(x86)\Citrix\ICAClient\DVCRenderingAdapterdll.HRESULT-2147024770


Hi there, I couldn't install the Citrix Client either and had the exact same error (copied below).. The script didn't fix the error for me unfortunately.

~~ What worked ~~ Installing "Microsoft Visual C++ Redistributable 2015" fixed the error for me. After that the installer worked fine :)

~~ Error Message ~~ This was the error I got when trying to install Citrix Receiver:

"Module C:\Program Files\Citrix\ICA Client\DVCRenderingAdapter.dll failed to register. HRESULT -2147024770. Contact your support personnel."

Chris Kibble

Thanks Zarkers! I've added that link to the post. Appreciate you letting us know!

Chris Kibble

Hey Quentin, sorry I see it's been some time since you posted this comment. If you're still running into issues please try the later versions of the receiver as well as some of the other fixes that our commenters have included.

paul l

Thanks for sharing this information. I was hitting this exact symptom when trying to upgrade from LTSR CU3 to CU4. The receiver portion of the upgrade failed. I tried your setacl script and that didn't work, but procmon showed that the same keys you identified were also present in HKCR\WOW6432Node\Interface... After adding these to the script the upgrade worked!