-
Notifications
You must be signed in to change notification settings - Fork 822
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
File missing after command "wsl --update" showing "WSL is finishing an ugrade... Update failed (exit code:1603) Error code:Wsl/CallMsi/E_ABORT" #10651
Comments
Thank you for reporting this @ChenLiangYin. Which version of WSL are you running ? What's the output of wsl --version ? |
Thank you for your reply! I think I am in wsl2. "wsl --version" shows "invalid command line option --version". |
It looks like you reverted to inbox wsl. Can you try to run wsl --update and see if that solves the issue ? |
If you install WSL > 2.0 again, can you collect logs during the installation so we can see where the issue is ? /logs |
#Requires -RunAsAdministrator [CmdletBinding()] Set-StrictMode -Version Latest $folder = "WslLogs-" + (Get-Date -Format "yyyy-MM-dd_HH-mm-ss") if ($LogProfile -eq $null) reg.exe export HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss $folder/HKCU.txt $wslconfig = "$env:USERPROFILE/.wslconfig" get-appxpackage MicrosoftCorporationII.WindowsSubsystemforLinux > $folder/appxpackage.txt $wprOutputLog = "$folder/wpr.txt" wpr.exe -start $LogProfile -filemode 2>&1 >> $wprOutputLog
} try
} if ($Dump)
} Collect networking state relevant for WSLUsing a try/catch for commands below, as some of them do not exist on all OS versionsWrite-Host "`nCollecting additional network state..." $networkingFolder = "$folder/networking" Host networking infotry try try try try try try try try try
Write-Host -ForegroundColor Green "Logs saved in: $logArchive. Please attach that file to the GitHub issue." |
Actually I have found the the ubuntu folder in %localappdata% where the ext4 still exists. It seems like those files are still intact. However, I don't know why after uninstalling the apps I still couldn't connect wsl. |
No, the problem still exists even if I push the repair button. If there anyway to repair and restore my original wsl? or I have to shutdown the original one and create a new one with the original ext4. I just copied it to other disk. |
Does manually installing the latest release solve the issue ? |
I am installing it manually. But it shows "WSL service could not be installed. Verify you have sufficient privileges to install system services". But I am administer... |
Can you collect logs during the install ? /logs |
#Requires -RunAsAdministrator [CmdletBinding()] Set-StrictMode -Version Latest $folder = "WslLogs-" + (Get-Date -Format "yyyy-MM-dd_HH-mm-ss") if ($LogProfile -eq $null) reg.exe export HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss $folder/HKCU.txt $wslconfig = "$env:USERPROFILE/.wslconfig" get-appxpackage MicrosoftCorporationII.WindowsSubsystemforLinux > $folder/appxpackage.txt $wprOutputLog = "$folder/wpr.txt" wpr.exe -start $LogProfile -filemode 2>&1 >> $wprOutputLog
} try
} if ($Dump)
} Collect networking state relevant for WSLUsing a try/catch for commands below, as some of them do not exist on all OS versionsWrite-Host "`nCollecting additional network state..." $networkingFolder = "$folder/networking" Host networking infotry try try try try try try try try try
Write-Host -ForegroundColor Green "Logs saved in: $logArchive. Please attach that file to the GitHub issue." |
You need to run the script and upload the file it produces, this is just the content of the script. /logs |
Sorry I see. |
I found out the solution now. I install a new distribution Ubuntu-22.04 now and replace its ext4 file with my previous one (on ubuntu20.04) and it works! All the files and data got restored. And I can open it on vscode. However, I am not sure if there is any problem when doing this way. Now I feel like I should store the files on my mnt/ not on the virtual machine. |
Today I want to check the volume of my virtual machine. Therefore, I just want to update my wsl. However, it shows the message "WSL is finishing an ugrade... Update failed (exit code:1603) Error code:Wsl/CallMsi/E_ABORT" which seems unable to update. However, after that, my virtual machine and all of my files on it were gone. I am using the Ubuntu 20.04
The text was updated successfully, but these errors were encountered: