Is you tor.exe connected with the network? Does it show something like this? The Socks listener is open quite early, but this does not consequently mean tor is ready already connected to the network. (just tested in a setup hopefully close to yours i 32-bit)
Dec 13 05:03:35.602 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 13 05:03:35.602 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Dec 13 05:03:35.000 [notice] Bootstrapped 0% (starting): Starting
Dec 13 05:03:46.000 [notice] Starting with guard context "default"
Dec 13 05:03:48.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Dec 13 05:03:48.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Dec 13 05:03:48.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Dec 13 05:03:48.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Dec 13 05:03:48.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Dec 13 05:03:48.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Dec 13 05:03:48.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Dec 13 05:03:48.000 [notice] Bootstrapped 100% (done): Done
Dec 13 05:09:27.886 [notice] Tor 0.4.8.13 (git-e153e72c01315f86) running on Windows Server 2012 [or later] with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
\7z.exe l tor.exe|more
7-Zip 24.09 (x64) : Copyright (c) 1999-2024 Igor Pavlov : 2024-11-29
Scanning the drive for archives:
1 file, 8562176 bytes (8362 KiB)
Listing archive: tor.exe
--
Path = tor.exe
Type = PE
Physical Size = 8562176
CPU = x86
Characteristics = Executable 32-bit
Maybe you did some tweaks on your torrc which do not work? Or an antivirus or firewall interfering?