It is usually not a good idea to rename system files (or change their NTFS permissions, after the next OS-Update this may be reversed back). Ideally contact your Software vendor (for ImageMagick) to request that they don't name their files with the same name as Windows system files.
A workaround hack, is to tell Windows to execute a different program when you are running convert.exe
Run something like this:
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\convert.exe" /v Debugger /t REG_SZ /d "C:\Program Files\ImageMagic\convert.exe" /f
I haven't tested this and I am not sure whether it works if the target has the same name as the source, but it is worth a try.
And you better remember you've done this if you even want to use to convert.exe to convert your file systems.
Another option is to put the ImageMagic folder into the path before %systemroot%.
I would really try to fix the application rather than changing system files.
Take owner of the file, right click on the executable, and rename it. Why don't you just put the ImageMagick path before Windows/System32 in the path variable – Ramhound – 2017-05-11T01:50:51.820
That doesn't work. Now it says "You need permission from xps\Chloe...". The package is installed with chocolatey and is in
– Chloe – 2017-05-11T01:55:56.233chocolatey\bin
.Now I can't change the owner back to
TrustedInstaller
. That user/name/account doesn't exist. – Chloe – 2017-05-11T02:03:25.917I assumed you understood the risks of changing the owner, and your desire, to accomplish what you wanted was defiant? You will have to reset the ACL on the file – Ramhound – 2017-05-11T02:26:31.567
How do you reset ACL? – Chloe – 2017-05-11T06:45:54.707