shadowsocks / shadowsocks-windows

A C# port of shadowsocks

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Shadowsocks-Windows is not even opening on my computer

seniorweasel opened this issue · comments

Describe the bug

I can't open the shadowsocks executable

Environment

  • Shadowsocks client version: 4.4.1.0
  • OS version: Windows 10 22H2 19045.2965
  • .NET version: 4.8/5.0.17 both I have

Steps you have tried

Tried to open it with command prompt (no message, error, etc. nothing appeared)
Tried to run it as an admin
Tried to run it in specific folders like program files (x86) or the x64 one, nothing happened.
Tried to run it with compatibility mode.
Tried to turn off the antivirus software
Tried to update and repair netfx, nothing corrupted
Tried netsh winsock reset, etc.
Tried sfc /scannow
nothing happened.

What did you expect to see?

I expected from shadowsocks GUI application to run

What did you see instead?

Nothing, it did not even run.

Config and error log in detail (with all sensitive info masked)

I could not get any log, etc. anything about it. Its simply just not running without any error, etc.

PASTE LOG HERE

Is there a process name Shadowsocks.exe in the task manager?

In some cases, certain apps may be blocked from running if your computer is protected by a network administrator (also known as a domain or Active Directory).

Unfortunately, I am not able to see any process on the taskmgr too. It's weird actually. I tried everything but no result.

Is there a process name Shadowsocks.exe in the task manager?

In some cases, certain apps may be blocked from running if your computer is protected by a network administrator (also known as a domain or Active Directory).

Came back to home. It actually shows itself a little bit on taskmgr and goes away, but before it goes away it says "Suspended".
I'd like to share a memory dump file, if you need.

Noting helped. I also tried to rebuild it by myself but... no hope. Probably because of ASR rules on my computer. Because debugger also gives no info. I'm using V2rayN+Xray Core for shadowsocks now. Sorry, I don't have enough time for solving that issue by myself. Solved by using different client.