
- #BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS HOW TO#
- #BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS MAC OS X#
- #BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS INSTALL#
- #BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS DRIVER#
- #BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS FULL#
#BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS MAC OS X#
#BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS DRIVER#
#BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS INSTALL#
'Please install the Blackmagic Desktop Video drivers to use the features of this application' If I capture the output of the child process it says : I also tried some other combinations like 'Local system account'.

I tried to use another 'real admin' account, but this has the same effect. I selected this account at the 'logon' tab of the service properties. But I am surprised that when I login with our domainUser account (according to our network administrator, this account is admin level) and I run the service via commandline, it works as expected. I agree that is really looks like that the service is not having admin rights. This is of course a very easy to handle issue. I found that our logging was written in C:\Windows\SysWOW64 and we handled this by writing our log files to C:\logging\myService\xxxxx.log. I can see the result when the icon of the application shows the admin logo inside the icon (that little shield).

I compiled the windows service (project type : Debuggable service) with a manifest to require admin rights. Thank you for your reply, I recognize all your comments. I'm not sure if that will help this specific case, but it is an alternative for if you need to save something to Program Files.
#BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS HOW TO#
Heres a link from Microsoft which shows how to change ownership of the directory, but it is not advised to write anything to the Program Files directory:Īlternatively, you could save your logs to an alternate location, such as the desktop or My Documents and then move is using a script to the Program Files directory. its owned by the user, or by the SYSTEM). If still isn't working then this may be because you aren't the owner of the folder (ie. It sounds like you might be running the service not as an administrator, despite being logged in as an administrator.Ĭan you confirm that you running the Windows Service with elevated admin rights? (Right-click -> Run as Administrator) However, running your Windows Service as an administrator should allow you to read and execute from the Program Files directory.

If you're trying to access these using a Windows Service they will be unreachable due to security permissions of the directory. It appears that the Blackmagic API files are in fact installed in the Program Files folder.
#BLACKMAGIC DESKTOP VIDEO DRIVERS FOR WINDOWS FULL#
What can I change, so the ImageCapture can capture images using the Blackmagic video drivers and the windows service will be started as real windows service.Ĭould it be that de “Blackmagic desktop video drivers” are installed in the ‘program files’ folder and therefore unreachable for our ImageCapture program? (I already tried to give the domainAdminUser full control to the Blackmagic folder)
