Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kali error 0x80041002 (null) after System Restore #11153

Closed
1 of 2 tasks
LukeVilla opened this issue Feb 14, 2024 · 4 comments
Closed
1 of 2 tasks

Kali error 0x80041002 (null) after System Restore #11153

LukeVilla opened this issue Feb 14, 2024 · 4 comments

Comments

@LukeVilla
Copy link

Windows Version

Microsoft Windows [Version 10.0.22631.3085]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

Trying to use Kali Linux

Other Software

No response

Repro Steps

  1. Install Kali Linux
  2. Get your computer stuck in Safe Mode
  3. Boot into recovery mode by pressing Shift-Restart at the login screen
  4. Use bcdedit at the command prompt to manually change Safe Mode setting
  5. Realize that that just made the problem worse, go back into recovery and use a restore point from a .NET Framework install
  6. Try to run Kali Linux

Expected Behavior

C:\Windows\System32>kali
┏━(Message from Kali developers)

┃ This is a minimal installation of Kali Linux, you likely
┃ want to install supplementary tools. Learn how:
┃ ⇒ https://www.kali.org/docs/troubleshooting/common-minimum-setup/

┗━(Run: “touch ~/.hushlogin” to hide this message)
┌──(root㉿BYTE-SIZE-INFO)-[/home]
└─#

Actual Behavior

C:\Windows\System32>kali
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80041002
Error: 0x80041002 (null)
Press any key to continue...

Diagnostic Logs

No response

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Closed similar issues:

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

@OneBlue
Copy link
Collaborator

OneBlue commented Feb 14, 2024

/logs

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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 [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants