msrdc.exe spams .etl files in RdClientAutoTrace directory

[nevmerzhitsky]

Version

Microsoft Windows [Version 10.0.19045.2546]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.83.1-microsoft-standard-WSL2

Distro Version

Ubuntu 20.04

Other Software

Docker Desktop (Windows), version 4.16.3
JetBrains Toolbox 1.27.2.13801, Windows 10.0

Repro Steps

Start Docker Desktop and work with some containers

Expected Behavior

No new .etl files in C:\Users\username\AppData\Local\Temp\DiagOutputDir\RdClientAutoTrace

Actual Behavior

I see the msrdc.exe process in my Windows which creates spam of .etl files in the C:\Users\username\AppData\Local\Temp\DiagOutputDir\RdClientAutoTrace directory from time to time. Full path of the msrdc process: C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.1.2.0_x64__8wekyb3d8bbwe\msrdc.exe /v:1DA2E607-905F-45FE-8912-D4B1F8019ABF /hvsocketserviceid:8C4086BF-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\1DA2E607-905F-45FE-8912-D4B1F8019ABF\wslg "C:\Program Files\WindowsApps\MicrosoftCorporati...

Diagnostic Logs

No response

[ligq]

I also have this issue. My linux distribution is Ubuntu 22.04

[hideyukn88]

@nevmerzhitsky, thanks for reporting the issue, do you observe same issue when WSL is launched without docker? such as start WSL by wsl.exe command from Windows's command prompt or terminal?

@ligq, do you also use Doccker desktop?

And if you can share us a few of those *.etl, it would help us to diagnostic the issue, thanks!

[ligq]

@nevmerzhitsky, thanks for reporting the issue, do you observe same issue when WSL is launched without docker? such as start WSL by wsl.exe command from Windows's command prompt or terminal?

@ligq, do you also use Doccker desktop?

And if you can share us a few of those *.etl, it would help us to diagnostic the issue, thanks!

No, I am not using Docker.
I had this issue since I updated wsl to the latest version last week. (I updated wsl from MS store).
The versions are:
WSL version: 1.1.2.0
Kernel version: 5.15.83.1
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1194

Every 30 seconds a .etl file was created.
The attached is a .etl file.
RdClientAutoTrace-WppAutoTrace-20230211-164020-138.zip

[nevmerzhitsky]

@nevmerzhitsky, thanks for reporting the issue, do you observe same issue when WSL is launched without docker? such as start WSL by wsl.exe command from Windows's command prompt or terminal?

Yes, files are create even when Docker Desktop stopped.

But today I was noticed that JetBrains Toolbox (1.27.2.13801, Windows 10.0) related to the issue: I see a new .etl file is created after just I started the Toolbox (without starting PhpStorm/PyCharm even). I think the Toolbox triggers the start of my WSL's Ubuntu to scan my PHP/Python projects whose all located on WSL's filesystem. The created .etl file: RdClientAutoTrace-WppAutoTrace-20230211-171635-606.zip

[ligq]

I have not installed anything about JetBrains.

[ligq]

Today I updated the wsl to the latest version, still got this issue.
And I found if I keep a wsl terminal open, no new .etl file is created.

[hideyukn88]

@ligq, would you please clarify what do you mean by "wsl terminal" ? If you close "wsl terminal" (and keep new files being created), what do you see when you type wsl --list -v in Windows command prompt? thanks!

[ligq]

"wsl terminal" means I run wsl in the windows terminal.
After I close windows terminal, then the new .etl files are being created every 30 seconds.

PS C:\Users\ligq> wsl --list -v
NAME STATE VERSION
Ubuntu-22.04 Running 2

[nasbench]

Hi,

Any updates regarding this issue?

[dzilin]

I am waiting for a solution to this issue...

[space-shell]

May relate to microsoft/WSL#8486

[bszonye]

I just discovered that my system is generating these log files every time File Explorer scans the system for drives. This happens whenever I open Explorer to the Home location and again every time it refreshes the tab. The log retention is exactly one week, and currently I have a few hundred of the logs totaling 3 GB. More information in the related discussion linked above. Hope this helps you with troubleshooting or corrective action.

[bszonye]

File explorer definitely isn't the only thing creating these log entries, because a couple dozen have shown up in my logs tonight while I was watching videos in Chrome.

[hideyukn88]

First, please allow me to clarify a few things.

1: One log file is always created every time when WSL/WSLg is launched. Thus, if WSL is terminated (aka wsl --shutdown) and restarted "repeatedly", it can end up large number of files being created.

2: Log files older than one week will be deleted, but there is no limit by number of files or total size of all files in the folder.

3: When Linux GUI applications are used, the size of one currently active log file can grow over time, but it shouldn't be significant, it should be less then 2~300mb even active WSL session is running more than 1 month.

Above 3 are currently expected behavior, but we are looking into to add limit by number of files.

Second, if WSL/WSLg is not terminated and relaunched repeatedly (like 1), but new log files are being created, or log files keep growing more than 500mb, this is not what's expected, thus, if you are experiencing such issues, please share a few log files with us, we would like to see as many as possible cases, and please make sure you are on the latest version of WSL, thanks!

[hideyukn88]

@nevmerzhitsky, thanks for sharing log file

file: RdClientAutoTrace-WppAutoTrace-20230211-171635-606.zip

From provided log file, it's very likely your case is fixed by microsoft/weston-mirror#138, which will be included in next WSL update, thanks!

[bszonye]

If I have an active WSL terminal open, I only see one log entry for the session, and opening File Explorer is instantaneous. However, if I close the WSL terminal, then any refresh of the File Explorer "Home" view will start a fresh WSL process. There's a noticeable delay (with progress bar) while File Explorer starts WSL, which I can see in Task Manager. If I leave the File Explorer window open, it'll start WSL again every few minutes when the view auto-refreshes.

That still doesn't explain what happened yesterday, though, as I wasn't actively using WSL or File Explorer. I presume that some other background process must have scanned the WSL drive. I'm attaching some of the logfiles from last night, including at least one log caused by File Explorer and a few more from unknown sources.

RdClientAutoTrace-WppAutoTrace-20230321.zip

Altogether there were about 2 dozen logfiles accumulated last night. Right in the middle of them, I can see this entry in Event Viewer:

Faulting application name: DllHost.exe, version: 10.0.22621.1, time stamp: 0x05e70ed3
Faulting module name: KERNELBASE.dll, version: 10.0.22621.1413, time stamp: 0x5129184b
Exception code: 0x80000003
Fault offset: 0x0000000000107d22
Faulting process id: 0x0x3684
Faulting application start time: 0x0x1D95BC690A6C0DD
Faulting application path: C:\WINDOWS\system32\DllHost.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 29adb7c7-1fcc-4765-af4b-5ec5fae754d5
Faulting package full name: MicrosoftCorporationII.WindowsSubsystemForLinux_1.1.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: wsl

This is the first time I've noticed an error like that, no idea whether it's related.

What's the recommended way to check WSL for updates?

[hideyukn88]

@bszonye,

What's the recommended way to check WSL for updates?

Please try wsl --update, this will install update if available. I think there is no way to just check if update is available without installing it, @benhillis? thanks!

[bszonye]

Thanks! The update command says that I'm already running the latest version.

[MattJeanes]

I'm now seeing this as well, started randomly possibly after an update to Windows (on Beta channel insider builds)

It's creating about one file every second all of which are around 8MB and it's filling up my drive extremely quickly and with tons of unnecessary writes.

I've attached a random one here if that helps at all, couldn't see anything noteworthy using tracerpt but I have also no idea what I'm looking at.

It happens whenever WSL is running at all, have to use wsl --shutdown to stop. Up to date, installed from MS Store. Tried uninstalling and reinstalling WSL entirely and did not fix it.

RdClientAutoTrace-WppAutoTrace-20230626-023310-410.zip

[hideyukn88]

@MattJeanes, thank you very much for sharing the log, the log indicates the socket is disconnected and it seems triggered from Linux VM side, do you see any dumps at /mnt/wslg/dumps? if not, please share /mnt/wslg/*.log with us, (note, this folder is cleaned up at every WSL start up, thus, dumps/logs need to be collected while active WSL instance is experiencing the issue) thanks!

[for internal reference]
::AP=c9281653::0 bytes read -- WSock has gracefully terminated, socket 3336 : 0.226455500
[c9281653]Read operation failed: freeing the read buffer. : 0.226456200

[MattJeanes]

@hideyukn88 thank you for looking into this. I was not able to find any dumps in the /mnt/wslg/dumps folder, but I have attached the log files. I can see a couple of interesting things like unable to checkDescriptor for 0x55b601632160 and this in the wlog.log file:

[01:35:58:789] [9:9] [INFO][com.freerdp.core.gcc] - Active rdp encryption level: NONE
[01:35:58:789] [9:9] [INFO][com.freerdp.core.gcc] - Selected rdp encryption method: NONE
[01:35:58:792] [9:9] [ERROR][com.freerdp.core.info] - failed to convert Domain string
[01:35:58:792] [9:9] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_SECURE_SETTINGS_EXCHANGE - rdp_recv_client_info() fail
[01:35:58:792] [9:9] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[01:35:59:126] [9:9] [INFO][com.freerdp.core.connection] - Client Security: NLA:0 TLS:0 RDP:1
[01:35:59:126] [9:9] [INFO][com.freerdp.core.connection] - Server Security: NLA:0 TLS:0 RDP:1
[01:35:59:126] [9:9] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:0 TLS:0 RDP:1
[01:35:59:126] [9:9] [INFO][com.freerdp.core.nego] - Turning off encryption for local peer with standard rdp security
[01:35:59:129] [9:9] [ERROR][com.freerdp.core.gcc] - Unknown GCC client data block: 0xC00C
[01:35:59:129] [9:9] [ERROR][com.freerdp.core.gcc] - Unknown GCC client data block: 0xC00D

I'm sure there is other useful stuff in the logs too! Please let me know if you need anything else or wish to reach out directly to me to investigate, I really appreciate it.

[MattJeanes]

Oops, didn't actually attach the file - here it is!

logs.zip

[hideyukn88]

@MattJeanes, thank you very much for log, as you pointed, below error is the fatal and this causes the disconnection of remote desktop protocol.

[01:35:58:792] [9:9] [ERROR][com.freerdp.core.info] - failed to convert Domain string

While error message indicates it's failing to convert "Domain" string, but based on FreeRDP source code, it can be either "Domain name", "User name", "Password", "AlternateShell" or "WorkingDirectory".

What it does here is, Windows sends these strings in Unicode, and FreeRDP is converting to UTF-8, and one of these conversions was failed.

But based on the RdClientAutoTrace you provided which logs what Windows is sending to Linux side; these are simply NULL (below screen capture). There is no logging for "Password" for security purpose, but this should be as well. At my environment, these are all NULL. Thus, I can't tell why conversion has been failed at your end.

So, just in case, I believe you have multple RdClientAutoTrace files can be found on your local disk, would you please share a few more of them? And is it possible you can run privately build version of WSLg with extended logging? if yes, I can send something to you. thank you very much for your help!

[MattJeanes]

@hideyukn88 yes I am happy to run debug versions of WSLg if you can share how to do that.

If you would like to reach out over email you can find it on my GitHub profile, although it is also useful to be talking in this public thread as well in case anyone else is seeing similar issues.

Here is a zip with 73 of those logs from when I booted WSL up earlier to grab those logs for you 🙂

They compress very well, 600MB down to 3MB!

RdClientAutoTrace.zip

[hideyukn88]

@MattJeanes, would you please try attached private system distro VHD (at below link, unzip it first). You can install it by following steps at https://github.com/microsoft/wslg/blob/main/CONTRIBUTING.md#installing-a-private-version-of-the-wslg-system-distro. Once the issue occurs again, please share /mnt/wslg/wlog.log with us, the log contains some additional information including the "Password" field mentioned above, it should be nil, but just in case, please double check, if it's exposing your real password or other than nil, please simply remove it and let us know, thanks for helping!

https://1drv.ms/u/s!AqQ2qEh_9iIOhqkPVs2_V0Z9dWoOrg?e=16q5df

[MattJeanes]

@hideyukn88 I have done that and the much more verbose log is attached below! Password is indeed showing nil as you said it should.

The issue happens immediately after booting WSL and I have also noticed the mouse cursor often showing the 'working in background' symbol (pic below) and flickering back to the normal mouse seemingly every time it writes one of these files. Not sure if that's relevant but thought worth noting!

wlog.zip

[MattJeanes]

Oh also, some extra system information in case it is useful:

Windows build: 22H2 (OS Build 22631.1900)
Insider settings: Beta channel
Distro: Ubuntu from MS Store
uname -a: Linux Matt-PC 5.15.90.2-microsoft-standard-WSL2 #1 SMP Fri Jun 2 00:45:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I have docker desktop installed but the issue was also happening without it installed, and happens with only the primary Ubuntu WSL runnning:

C:\_git> wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu                 Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

As I mentioned I also tried completely uninstalling WSL as much as I could and re-installing it to no avail.

[hideyukn88]

@MattJeanes, for diagnostics purpose, I rebuilt system distro private VHD without ICU library (which in charge of Unicode conversion) and switch to WinPR's inhouse conversion, would you please try this?

https://1drv.ms/u/s!AqQ2qEh_9iIOhqkRO2bCFSyGqmt23Q?e=biDVq4

[MattJeanes]

@hideyukn88 I have tried Arch WSL from the Microsoft Store and with only that one running it still shows the same issue:

C:\_git> wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu                 Stopped         2
  docker-desktop-data    Stopped         2
  Arch                   Running         2
  docker-desktop         Stopped         2

I have also tried your new system VHD (back on Ubuntu now) and it unfortunately has not helped the issue. Attached below is a zip containing one of the RdClientAutoTrace files and the wlog.log file.

logs.zip

I really appreciate your help with this by the way, hope we can get to the bottom of this!

[hideyukn88]

@MattJeanes, would you please try below VHD again and please share /mnt/wslg/wlog.log with us, thanks!

https://1drv.ms/u/s!AqQ2qEh_9iIOhqkSqc3VtKrVHPCbmA?e=QM0jge

[MattJeanes]

@hideyukn88 sure, have attached logs below.

wlog.zip

[hideyukn88]

@MattJeanes, I've updated to address possible buffer handling, please try again.

https://1drv.ms/u/s!AqQ2qEh_9iIOhqkWmWhadTTAxMby2g?e=tyHbzv

[MattJeanes]

@hideyukn88 I think you're onto something - it looks to be working 😄 I can now open graphical apps successfully!

There is one file it has created in the DiagOutputDir but it is no longer spamming. I have attached it and the wlog.log again, very promising results! Still some errors in the wlog.log but not sure if they are normal.

logs.zip

[hideyukn88]

@MattJeanes, thanks for checking, it's good to hear it's working!

Still some errors in the wlog.log but not sure if they are normal.

These are not really error but I logged them in that way (easy to tell), so all looks good, thank you very much for helping us to solve this! thanks!

[MattJeanes]

@hideyukn88 Ah okay, great! No problem at all, I am super happy that you've been able to fix this and so quickly as well 🙂

I was a little worried that I would be shouting into the wind by commenting here originally so I am very glad to be proven wrong.

I'll keep running the custom system.vhd for now but if you could let me know when the fix is out on the MS Store that would be super useful.

Again really appreciate you looking into this for me, hope you have a great rest of the week!

[camerondubas]

(edit: had some incorrect config. Made some progress and updated this comment to reflect that)

I'm having the exact same issue as MattJeanes (down to the flickering cursor), I tried using the latest custom system.vhd provided by @hideyukn88, but that causes wsl to crash on start with this error:

The network name cannot be found.
Error code: Wsl/0x80070043

[process exited with code 4294967295 (0xffffffff)]

I tried running netsh winsock reset (suggested here), but that didn't help.

Some details:
Windows 11 Home 22H2 (22631.1972 ni_release)

> wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2

> wsl -v
WSL version: 1.3.11.0
Kernel version: 5.15.90.2-3
WSLg version: 1.0.54
MSRDC version: 1.2.4240
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22631.1972

> cat .\.wslgconfig
[system-distro-env]
WESTON_RDP_HI_DPI_SCALING=true
WESTON_RDP_FRACTIONAL_HI_DPI_SCALING=true
WESTON_RDP_DEBUG_DESKTOP_SCALING_FACTOR=1OO

> cat ./.wslconfig
[wsl2]
systemDistro=C:\\Users\\<Path_To_File>\\system.vhd

Setting guiApplications=false in .wslconfig does stop the logging. Using this as a workaround for now.

Here's a zip containing a dump of some .etl files from a minute ago, as well as my wslg.log.
RdClientAutoTrace-and-wlog.zip

Let me know if I can provide any more info,
Thanks!

[hideyukn88]

@camerondubas, using my private VHD shouldn't cause such network issue, just in case, would you please re-download the VHD and try again? If persist, would you please take WSL log following https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method, thanks!

[Amit-A2Z]

(edit: had some incorrect config. Made some progress and updated this comment to reflect that)

I'm having the exact same issue as MattJeanes (down to the flickering cursor), I tried using the latest custom system.vhd provided by @hideyukn88, but that causes wsl to crash on start with this error:

The network name cannot be found.
Error code: Wsl/0x80070043

[process exited with code 4294967295 (0xffffffff)]

I tried running netsh winsock reset (suggested here), but that didn't help.

Some details: Windows 11 Home 22H2 (22631.1972 ni_release)

> wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2

> wsl -v
WSL version: 1.3.11.0
Kernel version: 5.15.90.2-3
WSLg version: 1.0.54
MSRDC version: 1.2.4240
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22631.1972

> cat .\.wslgconfig
[system-distro-env]
WESTON_RDP_HI_DPI_SCALING=true
WESTON_RDP_FRACTIONAL_HI_DPI_SCALING=true
WESTON_RDP_DEBUG_DESKTOP_SCALING_FACTOR=1OO

> cat ./.wslconfig
[wsl2]
systemDistro=C:\\Users\\<Path_To_File>\\system.vhd

Setting guiApplications=false in .wslconfig does stop the logging. Using this as a workaround for now.

Here's a zip containing a dump of some .etl files from a minute ago, as well as my wslg.log. RdClientAutoTrace-and-wlog.zip

Let me know if I can provide any more info, Thanks!

Having the same configuration in my system. Uploading the trace etl file. I have tried doing the registry tweak, re-install etc. Did not help.

RdClientAutoTrace-WppAutoTrace-20230710-034045-804.zip
PS C:\Users\Dell> wsl -v
WSL version: 1.3.11.0
Kernel version: 5.15.90.2-3
WSLg version: 1.0.54
MSRDC version: 1.2.4240
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22631.1972

PS C:\Users\Dell> wsl -l -v
NAME STATE VERSION

• Ubuntu Stopped 2
  osuse Stopped 2

[nevmerzhitsky]

I dont know what i do, wsl or other, but when i searching in google i found this page, can i just delete this folder C:\Users\cpanel\AppData\Local\Temp\DiagOutputDir because using my space 22.7 GB (24,448,598,016 bytes) Thanks

Yes, you can.

[sverkera]

I am getting about 140 new such files per minute.

[hideyukn88]

@lexavey, thanks for sharing your experience, it is unfortunate that this issue is still not addressed. While the log is deleted automatically time to time, but it was not enough in this case. I have added some mitigation for this by #1082, so that it will not take out large amount of space on user's disk. If you can share a few of those files, it will help us to understand more about this issue or your specific situation, thanks!

[sarim]

@hideyukn88 So RdClientAutoTrace etl files are error/crash logs? Due to their frequency I previously assumed they were debug logs. It seems to be if they are error/crash logs, we need to find out the root causes of error/crash right? Otherwise limiting process restart etc.. is just a band aid. If these are crash logs, can you please share how to open/read them? That way users can maybe help with diagnosis?

[tig]

Dupe of microsoft/WSL#10216 ?

[hideyukn88]

@sarim, no, they are not error/crash log, those logs are being created even everything is perfectly working, and unfortunately user can not read these logs in meaningful way. The log can be opened by wpa.exe (Windows Performance Analyzer) which tool is available publicly, but in order to access important logging information, it requires full private debug symbols of msrdc which is not available publicly, thanks!

[hideyukn88]

@lexavey, the behavior you observed is expected, the new log file is created every fresh WSL startup, and the log you provided does not show any errors, everything is working as expected, then WSL is terminated after roughly 50 secs of idle time. In this case, #1082 will not prevent from new log file being created, thus we are also working on to limit the number of files being created (or any other possible limitation), thanks!

[ecraig12345]

I just deleted 200GB+ of these files under %localappdata%\RdClientAutoTrace which had filled up my main hard drive... This is unacceptable, and if the files come back, I'd be happy to share some for debugging.

[amzon-ex]

Hello! I just had 23.3 GB worth of disk space consumed by these etl logs until I stopped WSL manually. It is after I stopped it that I realised I had lost so much space. This hasn't happened to me before - at least at this scale.
I just had my primary (and only) WSL distro sitting open, while I was working on something else. After reading this thread, I realise that msrdc.exe probably kept restarting - because I had my mouse flickering to the "working in background" state every other second.

I have attached one of these files below.

RdClientAutoTrace-WppAutoTrace-20230727-103211-730.zip

[hideyukn88]

To whoever experiencing this issue, would you please try the system.vhd from below link? @MattJeanes, thanks for helping us with previous drop, but if you don't mind, would you please try this new one again and let us know if this still works? thanks!

https://1drv.ms/u/s!AqQ2qEh_9iIOhqk8zLxXTvCerpopWg?e=pHYU7d

Here is how you can configure WSL to side-load private system-distro VHD.

https://github.com/microsoft/wslg/blob/main/CONTRIBUTING.md#installing-a-private-version-of-the-wslg-system-distro

And if it didn't work, please share RdClientAutoTrace files and /mnt/wslg/wlog.log, thanks!

[MattJeanes]

@hideyukn88 I have tried the new VHD and it looks good to me! It's created one file and appears to be holding it open which I believe is intended behaviour

[adiantek]

I had 32 874 files, total size 205 GiB

[smitharc]

Exactly the same issue here 240GB of log files deleted. I am running WSL2 Ubuntu 20.04 LTS and Docker desktop.

[dennisroche]

@hideyukn88 I have tried the new VHD and it looks good to me! It's created one file and appears to be holding it open which I believe is intended behaviour

I can also confirm this fix works 🙌. I was unable to use the PC as constant low diskspace.

[kyesil]

Exactly the same issue here77GB of log files deleted. I am running WSL2 Ubuntu 20.04 LTS and Docker desktop.

[nevmerzhitsky]

Not reproduced for me anymore, thanks!

$ wsl -v
Версия WSL: 2.0.7.0
Версия ядра: 5.15.133.1-1
Версия WSLg: 1.0.59
Версия MSRDC: 1.2.4677
Версия Direct3D: 1.611.1-81528511
Версия DXCore: 10.0.25880.1000-230602-1350.main
Версия Windows: 10.0.19045.3636

Docker Desktop (Windows), version 4.25.0 (126437)
JetBrains Toolbox 2.1.0.18144, Windows 10, x64

[ewebgh33]

I just deleted 50gb of logs.
I tried the trick of renaming the folder to RdClientAutoTrace.xxx so it looks like a file, reports said this would stop logs writing to it. But a few seconds later some process (I have shut down WSL already????) recreates the RdClientAutoTrace folder and logs start dumping in.

This thread was last commented over a year ago. I am pretty sure my WSL install isn't even that old, maybe 8 months? So as of 8 months back, there was no update to the default install that prevented this behaviour, I assume.

Is there now?
Or Is the best method still "download this random file from @hideyukn88 ?

I only have a 1Tb SSD, I can't be losing 100gb to logs every week or so.
It's literally writing 12mb every minute. It's insane.