Why can't openvpn connect on windos 7?

Question

openvpn

I do everything according to this manual,
click
On one computer (where Windows 7 is also) - it works. On the other - no.
If we disable the blocking of the domain and private profile, then everything works. As soon as we turn it on, it stops. I checked the path to the program, running as administrator. The vpka itself is fully functional. Configs are the same on both computers. that is, the problem is clearly from the computer.
(the outgoing rule is active, Windows is clean without antiviruses , etc.)

Thu Nov 29 18:46:20 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Thu Nov 29 18:46:20 2018 Windows version 6.1 (Windows 7) 64bit
Thu Nov 29 18:46:20 2018 library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Enter Management Password:
Thu Nov 29 18:46:20 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Thu Nov 29 18:46:20 2018 Need hold release from management interface, waiting...
Thu Nov 29 18:46:21 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'state on'
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'log all on'
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'echo all on'
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'bytecount 5'
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'hold off'
Thu Nov 29 18:46:21 2018 MANAGEMENT: CMD 'hold release'
Thu Nov 29 18:46:22 2018 MANAGEMENT: CMD 'username "Auth" "[email protected]"'
Thu Nov 29 18:46:22 2018 MANAGEMENT: CMD 'password [...]'
Thu Nov 29 18:46:22 2018 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Nov 29 18:46:22 2018 NOTE: --fast-io is disabled since we are running on Windows
Thu Nov 29 18:46:22 2018 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Nov 29 18:46:22 2018 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Nov 29 18:46:22 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]91.210.105.204:443
Thu Nov 29 18:46:22 2018 Socket Buffers: R=[8192->8192] S=[8192->8192]
Thu Nov 29 18:46:22 2018 Attempting to establish TCP connection with [AF_INET]91.210.105.204:443 [nonblock]
Thu Nov 29 18:46:22 2018 MANAGEMENT: >STATE:1543506382,TCP_CONNECT,,,,,,

ps Wi-Fi to which it is connected stands as a "home network". In theory, everything should work.

Answer 1

So the matter is in the firewall, see the allowing rule on the VPN server.
On clients, usually, everything works by default.