-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No control over Installation Files #607
Comments
Hi there! While I wouldn't say open-source software (that doesn't cost patients or clinicians anything!) is typical healthcare software, we can definitely look into making it easier for IT workers to install our software remotely. The reason why the USB driver installation isn't silent at the moment is to make it easier to debug when things go wrong, like certificates to working on all supported versions of Windows. Users can't send screenshots when drivers fail to install silently. Given that our USB driver installation on Windows has been working well for quite some time now, we should probably just make the USB driver installation silent for everyone, as it's one less thing to click through during installation. I've logged your request and hope to have this fixed soon. |
Note that a silent USB driver install is not possible on Windows 7 without a hotfix (which was never made available on Windows Update): https://support.microsoft.com/en-us/help/2921916/the-untrusted-publisher-dialog-box-appears-when-you-install-a-driver-i Given that the hotfix requires a restart for it to work and that we probably can't distribute it with the installer, having a silent install on Windows 7 is not viable. I'm going to attempt to allow a silent install for Windows 8, 8.1 and 10, and provide an error message if a silent install is attempted on Windows 7. |
A silent install option ( |
Very typical of Healthcare software - no ability to control the apps installation, no silent installation option for the USB drivers. You make it difficult for IT workers within Healthcare to use your product without tearing it open and re-writing it for our own environment. It's very frustrating. It might be easier for you to use the NSIS script compiler, but that doesn't work for us.
The text was updated successfully, but these errors were encountered: