WSL2 installing any distro causes crash of Windows

[Evgeniy-Spasskikh]

Windows Version

10.0.19045.5131

WSL Version

2.4.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

No response

Other Software

No response

Repro Steps

Windows 10 Enterprise 22H2 x64, Intel(R) Core(TM) Ultra 5 135U
When I try to install any distro, it downloads and then immediately causes Windows to crash. WSL1 works fine, but switching downloaded distro from WSL1 to WSL2 also causes crash. I tried installing different versions of WSL (2.4.5.0 and 2.3.26) and removed some Windows updates.
Virtualization enabled
PC is new, no other application was installed

Expected Behavior

WSL2 any distro works

Actual Behavior

Windows crash

Diagnostic Logs

Win events logs.zip
Windows events logs
Wsl logs are not saved

[github-actions]

Failed to parse logs. Unexpected file: Win events logs.evtx
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL crashes shortly after starting up (#12308), similarity score: 0.76
• WSL2 gives HYPERVISOR_ERROR BSOD but WSL1 works okay (#11508), similarity score: 0.75

Closed similar issues:

• Windows crashes when starting up WSL2 (#10293), similarity score: 0.83
• WSL 2 shows a KMODE_EXCEPTION_NOT_HANDLED BSOD upon installing a distro. (#7514), similarity score: 0.77
• WSL crashes when building application (#12238), similarity score: 0.74

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information

Found no WSL traces in the logs

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!