Open ItsumoKnight opened 1 year ago
- The "windhawk_setup.exe" for v1.2 I used disappeared like a ghost
This part makes me think that maybe an antivirus on your computer (incorrectly) detected Windhawk v1.2 as malicious, removed the setup file, and caused crashes to some processes that Windhawk injected into. Are you using an antivirus, or any other security program?
AVG AntiVirus. That does check out, I see the .exe's in quarantine. Don't see how that makes my desktop spaz out with its removal or why it's tripping the detection when the older ones don't.
Well thanks for troubleshooting, m417z. Hope it helps as data.
Can you check whether the issue happens with AVG turned off? You also might want to add Windhawk to the exclusions list.
Incompatibilities with Antivirus programs and false positive detections are brought up from time to time. Here's one of my replies to a similar report about Bitdefender from the Discord channel:
Unfortunately, false positive detections are a never ending problem. False detections like these were reported many times by users. Here's one of the most recent discussions about it, one of dozens: https://ramensoftware.com/7-taskbar-tweaker/comment-page-51#comment-13213
There's not much I can do about it. Adding a digital signature to my software helped a bit, but the issue still comes up.
[...] Note that both the tweaker and Windhawk inject code into other processes, which antiviruses usually find suspicious. You can try adding them to the antivirus exclusion list and see if that helps.
I did recently update my Windows 10 Pro to Version 22H2, and bothered checking today for an update to Windhawk. I use v0.9.2 which is still perfectly functional but I figured why not. So I try it and upon reaching the completed install window with the "Run Windhawk" on it; File Explorer crashes, desktop has a painful-to-look-at seizure for 1-2 minutes, and when it comes back all of my desktop icon text is invisible. Check File Explorer, all text is invisible too.
Restart computer, tried it a few more times and in-addition to repeats of above:
The v0.9.2 exe I kept from before works perfectly for uninstalling v1.2 & actual use except for one string erroring (the only error message in entire situation). Just ignoring it finishes the install fine, and the mods seem to work. So the old version I have does work consistently; I'm confused why the new version breaks things on my computer.