What's wrong with SOCKS 5 in Win 10?

Question

Windows

I don't even know where to dig...

There is a NodeJS package npm i socks-proxy( https://www.npmjs.com/package/socks-proxy )

I'm testing it in Ubuntu, setting up a SOCKS 5 proxy.

• I configure FireFox to work through it - it works fine.
  
• I set up a system-wide proxy in Ubuntu, I check in Google Chrome - it works fine.
  

I'm testing in Windows 10, I'm raising SOCKS 5 proxies.

• I configure FireFox to work through it - it works fine.
  
• I set up a system-wide proxy in Windows (I fill in only the socks field, as it should be), I check it in Google Chrome - it doesn't work! (connection timed out)
  
• Internet Explorer also using the system wide proxy too - doesn't work! (writes something like DNS_ERROR).
  
• I put in Google Chrome an extension for manually setting a proxy, I fill in the fields for socks - it works fine.
  

Those. It turns out that the socks proxy itself works, but when I specify it in the system-wide proxy settings in Win 10, neither Chrome nor Explorer wants to work through it.

Where to dig? What exactly doesn't work? Is there something wrong in Win 10 with socks 5 implementation?

Answer 1

The question why it does not work in Win, but it works in Ubuntu, will remain a mystery.
But on the other hand, I found what needs to be done to make it work in Win.
To do this, I used another socks implementation for NodeJS: https://github.com/sequoiar/socks5
Under Win with system-wide proxy settings, it worked in all browsers.