Citrix - Installation Error DVCRenderingAdapter.dll Failed to Register
I recently was troubleshooting the following error on roughly 400 systems that we were deploying the Citrix Receiver v14 to:
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 Helgeklein.com 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
2
3REM Christopher Kibble. March 1 2016.
4REM Always test in a development or test environment before using in production.
5
6REM Script requires SETACL from https://helgeklein.com/setacl/
7
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
10
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
13
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
16
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
19
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
22
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
25
26exit 0