Since only one user managed to report it to support let’s say that it’s not a wide-used feature.
And he started even without fully diagnosing the issue, claimed to be some routing problem at first: http://forum.mikrotik.com/t/routeros7-socks-packet-to-another-gateway-not-working/152856/5
Only a week ago he managed to describe the problem properly.
And no I don’t have something against socks in particular, I have something against spammers.
Two dedicated topics (that I know of) and spamming every release topic with his broken socks is annoying.
@Znevna if I were up to you and me, SOCKS would have been on the cutting room floor long ago. But I could say the same thing about MPLS, or IP>Packing…
I too imagine SOCKS version=5 isn’t a high priority… And, whatever reason why SOCKS doesn’t work may actually go beyond socks to some larger bug in the packet flow or auth system. Or perhaps they may be forced by distributors to drop it for the same reasons why @soheilsh want to use it, outside any technical reason. Clearly SOCKS is on Mikrotik’s radar since you can lock a device from using it…(and we know, many times, that there is a ticket for it open).
But my grip is with Mikrotik and their communications, not @soheilsh or you. They had a routing status for V7 page – certainly they can say what channel broken features are targeted for, include (but least among) them SOCKS, now that V7 isn’t in “testing” but shipping. Not sure that entirely solve @soheilsh issues, but at least it be a “see here: help.mikrotik.com/…” post.
It was not broken on purpose, I’m sure of it, and they can’t possibly tell what every tiny bit is broken vs v6.
That’s why you file bug reports, to report bugs found so they can put a number and a priority to it and consider fixing it in the future.
They’re putting a lot of work on other “router-like” features v7 Routing Protocol Status
You know, features that ISPs are waiting for to get stabilized in order to be put in production.
Socks, openvpn and other useless stuff don’t have that high of a priority.
socks5 now ok in 7.2rc1 is, but 7.1.1 still problem
And in 7.1 still a problem, and… You may continue 
Anyway it’s fixed in 7.2rc
There are no need to post the same in 3 threads!!!
We can all read the change logs.
Sounds like happy end to me, you should celebrate, now you can have both WG and SOCKS5. Even if it’s only RC version, but if you were willing to use older ones, this one shouldn’t be worse.
Oh and some of us can lock this discussion away:
/system/device-mode/update mode=enterprise socks=no pptp=no l2tp=no proxy=no romon=no smb=no
# physically hit the reset or mode button
# note: instruction say unplugging, but that didn't work on RB5009, Audience - hit [i]some[/i] button..
# after coming back...
/system/device-mode/print
# mode: enterprise
# socks: no
# pptp: no
# l2tp: no
# romon: no
# proxy: no
# smb: no
/ip/socks/set enabled=yes
/ip/socks/print
# ;;; inactivated, not allowed by device-mode
# enabled: yes
A good tip, block it once and for all.