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
[Bug] Second SimpleWall.exe instance/process in 3.8.1 #1769
Comments
Windows detects the second SimpleWall.exe process instance as a none-responding task and it can be closed with "Kill Not Responding Tasks" command. Is this intended behavior or a bug? |
simplewall cannot create second process, check second process by virustotal, if it is the same process then i do not know why, sw did not needed it, and even not elevated |
I checked many times and it happened even on a fresh installation of Windows 11 22631.3527 and nothing else installed. Unelevated process (only present in SimpleWall 3.8.1) Elevated process (present in all SimpleWall versions) |
I have the same problem. It occurs when I run SW with unchecked "Skip UAC prompt" or from a limited user account. |
Yes. Thank you for narrowing it down. "Skip UAC Prompt" is not needed for who disable UAC account-wide. I think this will be an easy for developer. |
Same issue persists in 3.8.2. |
Just tested Windows 11 and it had the same exact bug with 3.8.1 and 3.8.2. |
Checklist
App version
3.8.1
Windows version
Win10 19045
Steps to reproduce
Launch SimpleWall 3.8.1 (64bit) and check Task Manager. There will be 2 SimpleWall.exe processes. One is elevated and has High priority. Second one is not elevated and has Normal priority.
Expected behavior
There should be only one SimpleWall.exe process.
Actual behavior
Version 3.8.1 creates 2 SimpleWall.exe processes instead of one.
Logs
None
The text was updated successfully, but these errors were encountered: