Tor on Windows reports bug in its logs

Description of the issue: Brave Tor Status stays disconnected on fresh installation
How can this issue be reproduced?

  1. Install Brave Browser
  2. Start Brave
  3. Open New Private Windows with TOR

Expected result: Brave reports the TOR-Status “Connected” after a few secconds

Brave Version( check About Brave): Version 1.26.77 Chromium: 91.0.4472.164 (Offizieller Build) (64-Bit)

Additional Information:
Brave retries to start tor process, Tor starts at different Ports, but it crashes. This is the User Data\tor\data\tor.log:

Jul 19 04:51:17.000 [notice] Tor 0.4.5.9 opening new log file.
Jul 19 04:51:17.957 [notice] We compiled with OpenSSL 101010bf: OpenSSL 1.1.1k  25 Mar 2021 and we are running with OpenSSL 101010bf: 1.1.1k. These two versions should be binary compatible.
Jul 19 04:51:17.962 [notice] Tor 0.4.5.9 running on Windows 8 [or later] with Libevent 2.1.11-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Jul 19 04:51:17.962 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jul 19 04:51:17.963 [notice] Configuration file "C:\nonexistent" not present, using reasonable defaults.
Jul 19 04:51:17.963 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Program Files\BraveSoftware\Brave-Browser\Application\91.1.26.77\<default>. Is this what you wanted?
Jul 19 04:51:17.963 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Program Files\BraveSoftware\Brave-Browser\Application\91.1.26.77\<default>. Is this what you wanted?
Jul 19 04:51:17.964 [notice] Opening Socks listener on 127.0.0.1:0
Jul 19 04:51:17.965 [notice] Socks listener listening on port 5671.
Jul 19 04:51:17.965 [notice] Opened Socks listener connection (ready) on 127.0.0.1:5671
Jul 19 04:51:17.965 [notice] Opening Control listener on 127.0.0.1:0
Jul 19 04:51:17.965 [notice] Control listener listening on port 5672.
Jul 19 04:51:17.965 [notice] Opened Control listener connection (ready) on 127.0.0.1:5672
Jul 19 04:51:17.000 [warn] Error replacing "C:\Users\Sonic\AppData\Local\BraveSoftware\Brave-Browser\User Data\tor\watch\controlport": Invalid argument
Jul 19 04:51:17.000 [warn] Writing C:\Users\Sonic\AppData\Local\BraveSoftware\Brave-Browser\User Data\tor\watch\controlport failed: Invalid argument
Jul 19 04:51:17.000 [warn] Error replacing "C:\Users\Sonic\AppData\Local\BraveSoftware\Brave-Browser\User Data\tor\data\state": Invalid argument
Jul 19 04:51:17.000 [warn] Unable to write state to file "C:\Users\Sonic\AppData\Local\BraveSoftware\Brave-Browser\User Data\tor\data\state"; will try again later
Jul 19 04:51:17.000 [warn] Error replacing "C:\Users\Sonic\AppData\Local\BraveSoftware\Brave-Browser\User Data\tor\watch\control_auth_cookie": Invalid argument
Jul 19 04:51:17.000 [warn] Error writing auth cookie to "C:\\Users\\Sonic\\AppData\\Local\\BraveSoftware\\Brave-Browser\\User Data\\tor\\watch\\control_auth_cookie".
Jul 19 04:51:17.000 [warn] Error creating control cookie authentication file.
Jul 19 04:51:17.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.5.9 )
Jul 19 04:51:17.000 [err] Reading config failed--see warnings above.

Take a look at

The more recent replies (June 8 and 9 - evanschmitt and minty) indicate a possible resolution for Mac OS and Linux users, but you might locate the mentioned Tor directory that exists in a similar fashion for Windows OS.