openSUSE Leap 15-1 fails to install in WSL1/WSL2

[seritools]

• Your Windows build number: 18932

• What you're doing and what's happening:

WSL1:

• Trying to install openSUSE Leap 15-1 via Windows Store
• Clicking "Launch"
• "Installing, this may take a few minutes..."
• Asks for UNIX user name, enter it
• Get spammed with "The system cannot find the file specified"

WSL2:

• Installation fails with 0x80071772 (seems encryption related)

• What's wrong / what should be happening instead:

The app files seem to be created encrypted in the Program Files/WindowsApps folder:

After pressing "Launch", the folders in my LocalState folder are marked as encrypted as well:

Compare that to Ubuntu, for example:

WindowsApps:

LocalState after (successful) install:

It seems this may be related to #4103, however the files don't seem to be compressed, but encrypted instead?

[NotTheDr01ds]

I was seeing the same issue on Windows Build 18362 with WSL1. I ran an "openSUSE-Leap-15-1.exe clean", followed by "openSUSE-Leap-15-1.exe", and saw the same problem again after reinstalling.

In checking the installation (Settings -> Apps & Features), I noticed that the install had defaulted to the D: drive.

From Apps & Features->OpenSUSE...->Advanced, I did a Terminate, followed by a Reset. I then ran another "clean", and then used the "Move" option (again, from Apps & Features/Advanced) to put it on the system drive (C:, of course).

I then re-launched from the Store, and the installation completed successfully this time, allowing the user creation.

The files are not showing as encrypted, but I didn't check their state when the install was failing.

[lemmy04]

still happening with wsl2 on build 18363.535. Any chance to get that fixed?

[benhillis]

@lemmy04 WSL2 was first available in 18917, you're still running WSL1.

[lemmy04]

@lemmy04 WSL2 was first available in 18917, you're still running WSL1.

I'm on the latest windows 10 build 1909, which according to the microsoft docs should be running WSL2. At least I have a wsl command which i thought means it's wsl2 and not wsl1...

[therealkenc]

Confirmed here. This is on 19023, --set-default-version set to 2. Also tried 19555 before rolling back. I am not 100% convinced this is limited to OpenSUSE, but not willing to clobber my Ubuntu installs to find out.

[nevgeniev]

still doesn't work with 2004 release

[crramirez]

Hello,

This happens because the package won't force to be installed in C:. This happened a while with Ubuntu 20.04.

Remove the app and then change your settings:

Make your that new applications install in C:

After it is installed you can change it back to your preferred drive.

Regards,
Carlos

[bpulliam]

@crramirez has a good workaround until the solution is available: make sure your distros install on the system drive to ensure that they are not encrypted. Closing this issue and marking as workaround-available and fixinbound.

[zhuziyi1989]

我的20.04版本也存在这个问题，于是我下载了18.04进行安装，最后18.04成功安装，这个时候我打开之前的20.04，居然没有提示找不到路径的错误了。

This problem also exists in my version 20.04, so I downloaded 18.04 for installation. Finally, 18.04 was successfully installed. At this time, I opened the previous version 20.04 without prompting the error that the path could not be found.