Odd clock stretching when WSL is installed

[Matteo-Di-Rienzo]

So kind of an odd issue, is similar to the windows defender bug.

So I have my 9900K at 4.7ghz, I've known windows to be a bit finicky with windows defender specifically real time protection which messes up effective clocks. When I have real time protection enabled, my effective clocks drop 50-100mhz lower than my core clocks (4700mhz) when under load. If I turn off real time protection the effective clocks stay pegged at 4700mhz, matching the core clock. So I've edited the registry to disable real time protection permanently.

Now I have Wsl2 installed, and noticed the exact same phenomenon, I removed wsl and turned off the virtual machine check boxes inside off turn off apps and features settings, so not sure if it's wsl or the windows virtual machine setting that does it.

So, any fix for this? I'd like to still have wsl on my system, but as I'm an avid overclocker and like tinkering, I'd like my effective clocks to be matched when under load.

[github-actions[bot]]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[Matteo-Di-Rienzo]

/questionOn Jul 31, 2024, at 9:36 PM, github-actions[bot] @.***> wrote: Logs are required for review from WSL team If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt: Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1

The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to @.*** with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]

Diagnostic information

``` Found '/question', adding tag 'question' Found '/feature', adding tag 'feature' Found '/emailed-logs', adding tag 'emailed-logs' ```