You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing to C:\Program Files doesn't allow the driver to load after installation (might be permissions related?)
Steps to reproduce
When installing, you can choose a directory for install (ex: C:\Program Files\VirtualDisplayDriver).
Doing so will permit the installation, but after installation, nothing will happen with the computer. The companion app will run, but say "No driver configured", and things don't work.
After searching and watching some videos (thanks for the installation guide), I observed that if I installed to a different location, then a signing dialog pops up and I had to approve that, and then the driver works as expected.
Expected behavior
I suspect that the issue is that I specified a directory that required Administrator permission, so it didn't permit the driver to start as a result. At minimum it would be good for the installer to check if permissions are available before installing, or maybe there's a way to make it work if you do install to C:\Program Files.
Log File (Beta Only)
No response
Contact Details
No response
The text was updated successfully, but these errors were encountered:
Which OS?
Win11 Home
Which release?
23H2
Describe the bug
Installing to C:\Program Files doesn't allow the driver to load after installation (might be permissions related?)
Steps to reproduce
When installing, you can choose a directory for install (ex: C:\Program Files\VirtualDisplayDriver).
Doing so will permit the installation, but after installation, nothing will happen with the computer. The companion app will run, but say "No driver configured", and things don't work.
After searching and watching some videos (thanks for the installation guide), I observed that if I installed to a different location, then a signing dialog pops up and I had to approve that, and then the driver works as expected.
Expected behavior
I suspect that the issue is that I specified a directory that required Administrator permission, so it didn't permit the driver to start as a result. At minimum it would be good for the installer to check if permissions are available before installing, or maybe there's a way to make it work if you do install to C:\Program Files.
Log File (Beta Only)
No response
Contact Details
No response
The text was updated successfully, but these errors were encountered: