WhitewaterFoundry / Fedora-Remix-for-WSL

Fedora Remix for Windows Subsystem for Linux.
Other
734 stars 53 forks source link

Fedora Remix for WSL installation failed #52

Open tim-sebring opened 5 years ago

tim-sebring commented 5 years ago

Describe the bug When executing the most recent (1.30.1.0_x64) version of Distro Launcher, I get the following message almost immediately:

App installation failed with error message: Catastrophic failure (0x8000ffff)

To Reproduce Steps to reproduce the behavior:

  1. Double click on "DistroLauncher-Appx_1.30.1.0_x64.appx
  2. Click "Install"

Expected behavior Remix installs successfully and allows to use

Screenshots Image

Additional context This is a corporate/Enterprise computer, some policies are enabled that I have no control over, but the original Ubuntu install of WSL that is available at the MS store seemed to work fine. I preferred Fedora, so I followed instructions on how to remove the Ubuntu install (weeks ago) and now am attempting to install Fedora Remix.

Basic Troubleshooting Checklist

[x] I have searched Google for the error message. [x] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled. [x] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues. [x] I have searched the WLinux issues page: https://github.com/WhitewaterFoundry/WLinux/issues. [x] I have reset WLinux: Settings->Apps->Apps & features->WLinux->Advanced Options->Reset. [x] I have disabled and re-enabled WSL in Windows Features. [x] I have run Windows 10 updates and restarted.

What other troubleshooting have you attempted?

Insert here:

Trying to follow official instructions and not muck around with things to make anything worse.

WLinux Version

Find: Settings->Apps->Apps & features->WLinux->Advanced Options->Version.

Insert here:

Does not appear, though I know WSL is enabled.

Windows Build

Run 'systeminfo | findstr /C:"OS"' in Command Prompt and insert here:

PS C:\WINDOWS\system32> systeminfo |findstr /C:"OS" OS Name: Microsoft Windows 10 Enterprise OS Version: 10.0.17134 N/A Build 17134 OS Manufacturer: Microsoft Corporation OS Configuration: Member Workstation OS Build Type: Multiprocessor Free BIOS Version: Dell Inc. 1.15.4, 12/8/2017

For help on retrieving: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#check-your-build-number

crramirez commented 5 years ago

Hello @tim-sebring,

We will check and get back to you.

Thanks for reporting

Regards

tim-sebring commented 5 years ago

I also wanted to mention (just thought of this) that the Microsoft Store is blocked here at work. If the installer attempts to access the MS store, that could be a contributing factor. Internet access also goes through a corporate proxy, but we have access with credentials to get through.

crramirez commented 5 years ago

Ok, I installed in your Windows version and it works. Let's follow some steps:

  1. Could you install it using PorweShell so it can show you a better error? Add-AppxPackage -Path "DistroLauncher-Appx_1.30.1.0_x64.appx"

  2. Can you double-check if you enabled Side Loading? Check steps in this page: https://www.howtogeek.com/285410/how-to-install-.appx-or-.appxbundle-software-on-windows-10/

Regards

tim-sebring commented 5 years ago

So I checked #2 first -- Developer mode was already enabled, but I received this message: "Developer mode is turned on. However, remote deployment and Windows Device Portal couldn't be installed so they're not available. Error code 0x800f0954". Then I attempted to use the command you mentioned, and it failed saying that the package could not be opened. I looked in my Downloads directory where the appx file was, and saw a directory of the same name. I deleted that and tried again, and this time it installed completely successfully.

I can't really say if the directory existed before the GUI install attempt, but I don't recall it being there when I looked for the appx file directly.

crramirez commented 4 years ago

We updated the package in Releases to Fedora 31. It still says 29 in /etc/os-release but it correctly shows the version in /etc/fedora-release