-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Installer using incorrect service name #47
Comments
So we assume no KProcessHacker2 service is running anymore? |
Yes, although someone might be upgrading from an older version with KPH2 which needs to be stopped/deleted (??) but all newer versions (and the last two releases) are using KPH3 |
Changes for installer, just diff:
|
@VictorVG: thanks, I already have made a patch for this locally. |
Ok!, big thanks! |
Patch correction:
|
Sorry, more fix - I accidentally mixed up files - my version Process_Hacker_installer_full.iss has more lines, because they would not match. Remade and tested team
Diff attached |
Thanks but don't beat yourself up; let me find some time to merge my local
|
Ok!, I wait Your. No problem. Big thanks! |
Also I found value
do you needed correct this string? |
Sorry, but my patch it causes an error in the new versions of Process Hacker due to the recording of incorrect values of the driver KProcessHacker3 Parameters\SecurityLevel=2. Because for the assembly of Process Hacker v3.0.0.144 and later it does not apply. |
I patched this some time ago but forgot to update the ticket 😄 |
Ok! :) |
The Process Hacker setup is not correctly installing/uninstalling KPH due to using the service name KProcessHacker2 after it was renamed KProcessHacker3 about two releases ago :P
The text was updated successfully, but these errors were encountered: