I have successfully repackaged the files/.INI/shortcuts and even added a Custom Action to execute winvnc.exe -install after the files/.INI/shortcuts are copied to the installation folder to install and start the uvnc_service service. This works without any problems.

Where I am having problems is with the unattended install of the mirror driver as an additional Custom Action. After downloading the drivers.zip file, I can see two options to install the mirror driver in an unattended way:

The first problem is that ..\driver\xp\install_silent.bat file (i.e., setupdrv.exe installs) does not work, as the driver is not installed after executing this (e.g., the mv2.dll file (and other driver related files) are not dropped into C:\Windows\System32 and the mv video hook driver2 is not present in the Device Manager > Display adapters). Is this what everyone else has experienced?

Regardless, this isn't so much of a problem as ..\driver\xp\install.bat (i.e., setupdrv.exe install) does appear to work (more or less silently) -- but only if you execute it manually! Which leads me to the second (i.e., the real) problem:

If I add a Custom Action into my MSI installation script to execute "C:\Program Files\UltraVNC\Mirror\setupdrv.exe" install, it fails with a Driver installation failed error and the mirror driver is not installed.

If I add a Custom Action into my MSI installation script to execute a VB script to copy the driver files into %Temp% and execute "%Temp%\setupdrv.exe" install, it also fails with a Driver installation failed error and the mirror driver is not installed.

If I add a Custom Action into my MSI installation script to execute a VB script to copy the driver files into C:\Temp (i.e., short path with no spaces) and execute "C:\Temp\setupdrv.exe" install, it again fails with a Driver installation failed error and the mirror driver is not installed.

Note: I copy the XP version (from drivers.zip) of setupdrv.exe, driver\mv2.cat, driver\mv2.dll, driver\mv2.inf, driver\mv2.sys into the target destinations above from my MSI as a Custom Action so the files are present on the target system during and after install time. I can run setupdrv.exe install from any of the above locations manually (i.e., from the Start > Run dialog) once my MSI copies the file across and it will execute and install the mirror driver fine which is strange.

Can anyone shed any light on these Driver installation failed errors? Are there any log files (or is it possible to turn logging on) for setupdrv.exe?

I found some older posts (several years old) on this forum that referenced the exact same Driver installation failed error message, but the proposed solutions were not helpful unfortunately.

I was able to install trusted certificate on Windows Seven and install silently mirror driver with Devcon.

But I can't do the same on Windows XP x86, this is what I'm doing :
- Install uvnc 1.0.9.6 x86
- In setup I check mirror drivers download to get the latest mirror drivers x86.
- I go in properties of mv2.dll and I install manually the certificate (let it export later, before I want to check if that works)
- I can see the certificate into certificate manager, trusted publisher section, in Internet Explorer (like in Windows Seven)
- I use devcon (x86) to install the mirror driver, but I got the warning concerning unsigned driver

I don't understand why because I've installed the mv2.dll certificate it should work like on Windows Seven but it does not : I have the unsigned driver warning.

Have you downloaded the mirror driver recently? Although the mirror
driver files did not change with the release of 1.0.9.6, Rudi updated the
certificate to sometime in 2014. Prior to that change the mirror driver
cert was set to expire around April 10, 2011.

The only driver signing recognized by Windows XP is a WHQL signature.
Drivers need to be signed by MS.... this is to expensive and a paper hell.

For the installer we did a little trick to avoid the popup.

The setupdrv.exe we use detect the popup and press the ok button This trick only works when you have a desktop, setupdrv need to be able
to detect the popup window. (Running setupdrv from some service without a logon is likely to fail to press the ok button.)

Wrote a powershell script which seems to work on Win7 and WinXP boxes. The setupdrv.exe line would cause the HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce key to run whatever was in it, so I disabled it for the line. This is only a section of a bigger script which reboots and runs while starting. I renamed the folders to xp32, xp64, vista32, and vista64 (no W2K folder). Needed to rename them to keep the code short. I exported the certificate from mv2.dll (Properties > Digital Signatures > Details> View Certificate > Details > Copy to File...). Here is the section of script:

Atticus wrote:Wrote a powershell script which seems to work on Win7 and WinXP boxes. The setupdrv.exe line would cause the HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce key to run whatever was in it, so I disabled it for the line. This is only a section of a bigger script which reboots and runs while starting. I renamed the folders to xp32, xp64, vista32, and vista64 (no W2K folder). Needed to rename them to keep the code short. I exported the certificate from mv2.dll (Properties > Digital Signatures > Details> View Certificate > Details > Copy to File...).

Can you explain more how to run this on every computer in a domain? Is it possible to deploy this in GPO? Where to put this script and how to run it?