search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.46k stars 822 forks source link

wsl update failed: update failed: updating wsl: exit code: 4294967295 #11554

Open JulianHopkins opened 6 months ago

JulianHopkins commented 6 months ago

Windows Version

22H2 19045.2130

WSL Version

5.10.102.1

Are you using WSL 1 or WSL 2?

Kernel Version

5.10.102.1

Distro Version

Ubuntu-22.04

Other Software

Docker 4.29.0

Repro Steps

After installing Docker Desktop for Windows version 4.29.0, during the first launch it tries to update WSL and an error occurs

Expected Behavior

Launching Docker Desktop for Windows version 4.29.0 without error

Actual Behavior

After installing Docker Desktop for Windows version 4.29.0, during the first launch it tries to update WSL and an error occurs: wsl update failed: update failed: updating wsl: exit code: 4294967295: running WSL command wsl.exe C:\windows\System32\wsl.exe --update --web-download: (c) >@?>@0F8O 09:@>A>DB (Microsoft Corporation). A5 ?@020 70I8I5=K.

A?>;L7>20=85: wsl.exe [Argument] [Options...] [CommandLine] ...

Diagnostic Logs

github-actions[bot] commented 6 months ago

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 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](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'.

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:

Closed similar issues:

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

github-actions[bot] commented 6 months ago

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 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](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'.

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:

Closed similar issues:

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

JulianHopkins commented 6 months ago

WslLogs-2024-05-04_14-39-40.zip

github-actions[bot] commented 6 months ago

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information ``` Appx package is not installed Found no WSL traces in the logs ```
JulianHopkins commented 6 months ago

/emailed-logs

github-actions[bot] commented 6 months ago
Diagnostic information ``` Found '/emailed-logs', adding tag 'emailed-logs' ```
JulianHopkins commented 6 months ago

What does "Appx package is not installed" mean?

JulianHopkins commented 6 months ago

WslLogs-2024-05-04_14-55-07.zip

JulianHopkins commented 6 months ago

/emailed-logs

github-actions[bot] commented 6 months ago
Diagnostic information ``` Found '/emailed-logs', adding tag 'emailed-logs' ```
github-actions[bot] commented 6 months ago
Diagnostic information ``` Appx package is not installed ```
JulianHopkins commented 6 months ago

WslLogs-2024-05-04_15-16-08.zip

JulianHopkins commented 6 months ago

/emailed-logs

github-actions[bot] commented 6 months ago
Diagnostic information ``` Found '/emailed-logs', adding tag 'emailed-logs' ```
github-actions[bot] commented 6 months ago
Diagnostic information ``` Appx package is not installed ```
JulianHopkins commented 6 months ago

No, it didn't work. Even complete removal and disabling of the WSL subsystem with the subsequent command "wsl --install" did not help. I can’t move beyond version 5.10.102.1. Although new, as far as I know: 5.15.146.1-2

пн, 6 мая 2024 г. в 14:41, Grouane @.***>:

Did you manage to solve the issue ? I have the same issue and can't find anything to solve it

— Reply to this email directly, view it on GitHub https://github.com/microsoft/WSL/issues/11554#issuecomment-2095816607, or unsubscribe https://github.com/notifications/unsubscribe-auth/AODVWYDMBZRSLNPZPSJ6AR3ZA5T7FAVCNFSM6AAAAABHGXKJRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVHAYTMNRQG4 . You are receiving this because you authored the thread.Message ID: @.***>

OneBlue commented 6 months ago

Thank you @JulianHopkins. Does manually installing the MSI package solve the issue ?

JulianHopkins commented 6 months ago

No

oeon commented 6 months ago

Applying this Windows update allowed me to update to 4.30 https://github.com/docker/for-win/issues/14022#issuecomment-2065838496 maybe it will help you too ¯_(ツ)_/¯

vinalian commented 3 months ago

Thank you @JulianHopkins. Does manually installing the MSI package solve the issue ?

Thank you, it helped me.

karema9 commented 2 months ago

wsl update failed: update failed: updating wsl: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --update --web-download: Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe [Argument] [Options...] [CommandLine]

Arguments for running Linux binaries:

If no command line is provided, wsl.exe launches the default shell.

--exec, -e <CommandLine>

    Execute the specified command without using the default Linux shell.

--

    Pass the remaining command line as is.

Options:

--cd <Directory>

    Sets the specified directory as the current working directory.

    If ~ is used the Linux user's home path will be used. If the path begins

    with a / character, it will be interpreted as an absolute Linux path.

    Otherwise, the value must be an absolute Windows path.

--distribution, -d <Distro>

    Run the specified distribution.

--user, -u <UserName>

    Run as the specified user.

--system

    Launches a shell for the system distribution.

Arguments for managing Windows Subsystem for Linux:

--help

    Display usage information.

--install [Options]

    Install additional Windows Subsystem for Linux distributions.

    For a list of valid distributions, use 'wsl --list --online'.

    Options:

        --distribution, -d [Argument]

            Downloads and installs a distribution by name.

            Arguments:

                A valid distribution name (not case sensitive).

            Examples:

                wsl --install -d Ubuntu

                wsl --install --distribution Debian

--set-default-version <Version>

    Changes the default install version for new distributions.

--shutdown

    Immediately terminates all running distributions and the WSL 2

    lightweight utility virtual machine.

--status

    Show the status of Windows Subsystem for Linux.

--update [Options]

    If no options are specified, the WSL 2 kernel will be updated

    to the latest version.

    Options:

        --rollback

            Revert to the previous version of the WSL 2 kernel.

Arguments for managing distributions in Windows Subsystem for Linux:

--export <Distro> <FileName>

    Exports the distribution to a tar file.

    The filename can be - for standard output.

--import <Distro> <InstallLocation> <FileName> [Options]

    Imports the specified tar file as a new distribution.

    The filename can be - for standard input.

    Options:

        --version <Version>

            Specifies the version to use for the new distribution.

--list, -l [Options]

    Lists distributions.

    Options:

        --all

            List all distributions, including distributions that are

            currently being installed or uninstalled.

        --running

            List only distributions that are currently running.

        --quiet, -q

            Only show distribution names.

        --verbose, -v

            Show detailed information about all distributions.

        --online, -o

            Displays a list of available distributions for install with 'wsl --install'.

--set-default, -s <Distro>

    Sets the distribution as the default.

--set-version <Distro> <Version>

    Changes the version of the specified distribution.

--terminate, -t <Distro>

    Terminates the specified distribution.

--unregister <Distro>

    Unregisters the distribution and deletes the root filesystem.

--mount <Disk>

    Attaches and mounts a physical disk in all WSL2 distributions.

    Options:

        --bare

            Attach the disk to WSL2, but don't mount it.

        --type <Type>

            Filesystem to use when mounting a disk, if not specified defaults to ext4.

        --options <Options>

            Additional mount options.

        --partition <Index>

            Index of the partition to mount, if not specified defaults to the whole disk.

--unmount [Disk]

    Unmounts and detaches a disk from all WSL2 distributions.

    Unmounts and detaches all disks if called without argument.

I am getting the same erro while starting Docker Desktop on Windows. I have tried the recommended solutions with no success, what could be the issue.

Traineratwot commented 1 month ago

GPT: The error you're encountering is related to updating the Windows Subsystem for Linux (WSL). Error code 1603 typically indicates a general installation failure, while exit code 4294967295 (or 0xffffffff) may signify that an error occurred during the execution of the command.

Here are several steps that may help you resolve this issue:

  1. Check the Installation Log: Open the log file mentioned in the error message (<HOME>\AppData\Local\Temp\wsl-install-logs.txt) to get more detailed information about what went wrong.

  2. Update Windows: Ensure that you have all the latest Windows updates installed. Sometimes, WSL issues can be related to outdated Windows components.

  3. Restart Your Computer: Sometimes a simple reboot can help resolve temporary issues.

  4. Reinstall WSL:

    • Open PowerShell as an administrator and run the following command to unregister WSL: 
      wsl --unregister <DistroName>

      Replace <DistroName> with the name of your distribution (e.g., Ubuntu).

    • Then reinstall WSL using: 
      wsl --install

  5. Check for Conflicting Programs: Some antivirus programs or system utilities may block the installation of updates. Try temporarily disabling them and attempt the update again.

  6. Run the Installation Manually: If you know which version of WSL you need, you can try downloading and installing it manually from the official Microsoft website.

  7. Use the wsl --update Command: Try executing the update command manually in PowerShell as an administrator:

    wsl --update

If none of these steps work, you may want to seek help on the official Microsoft forums or the Windows community for more specific guidance.

It helped me