05-29-2018, 03:37 PM
(This post was last modified: 05-29-2018, 03:43 PM by InterestedNewbie.)
I would appreciate some help with the following:
I have compiled a complete setup file of my utilities program. It installs fine and works fine.
However, after install the user has to Take Ownership of the Program Folder because Windows is blocking access to some of the files and then some elements of my program won't work properly.
Instead of a right clicking on the program folder, choosing properties, clicking the security tab etc. etc. or using third-party reg files or utilities, I would prefer a faster and easier way (because some users don't understand all these extra steps and I preferably don't want to include any third party files in my setup).
I've been trying to create a second executable that takes care of this by means of performing these steps one after another by means of sending keystrokes/activating the controls. About halfway, in the "Permissions for App2" window, QM manages to activate the window but apparently cannot get access to its controls.
Apart from that I think this approach is too risky anyway, too many steps are involved with the chance of misfiring/accidental selection of the wrong folder, user may touch the mouse or keyboard etc.
It's about this program folder:
C:\Program Files (x86)\App2
I understand that the Take Ownership procedure mainly consists of (CMD) commands Takeown.exe and Icacls.exe
But that would be way too complicated for a user to do. Is there an easier way with QM?
Any suggestions are welcome.
I have compiled a complete setup file of my utilities program. It installs fine and works fine.
However, after install the user has to Take Ownership of the Program Folder because Windows is blocking access to some of the files and then some elements of my program won't work properly.
Instead of a right clicking on the program folder, choosing properties, clicking the security tab etc. etc. or using third-party reg files or utilities, I would prefer a faster and easier way (because some users don't understand all these extra steps and I preferably don't want to include any third party files in my setup).
I've been trying to create a second executable that takes care of this by means of performing these steps one after another by means of sending keystrokes/activating the controls. About halfway, in the "Permissions for App2" window, QM manages to activate the window but apparently cannot get access to its controls.
Apart from that I think this approach is too risky anyway, too many steps are involved with the chance of misfiring/accidental selection of the wrong folder, user may touch the mouse or keyboard etc.
It's about this program folder:
C:\Program Files (x86)\App2
I understand that the Take Ownership procedure mainly consists of (CMD) commands Takeown.exe and Icacls.exe
But that would be way too complicated for a user to do. Is there an easier way with QM?
Any suggestions are welcome.