**[WARNING]** WSL unusable in build 18272 (No such interface supported)

[benhillis]

There is an issue in this build that makes WSL inoperable. When trying to launch your distribution you will see a “No such interface supported” error. The issue has been fixed and will be in next week's Insider Fast build. If you've installed this build you can roll back to the previous Windows build using “Go back to the previous version of Windows 10” in Settings->Update & Security->Recovery.

[therealkenc]

Thanks so much for the heads up Ben. My radiator fan is whirring as we speak while 18272 installs in the background. Work-around: hold together a week of uptime somehow.

[benhillis]

@therealkenc - No problem. I feel bad about this but luckily the rollback mechanism works well and is actually surprisingly fast.

[Biswa96]

Lxss User session <--> Lxss Instance connection gone... poof....
Workaround: Is there any black magic to use old LxssManager.DLL file in newer builds?

[benhillis]

@Biswa96 - Unfortunately not, I suggest rolling back.

[Biswa96]

The whole WSL subsystem isn't affected. Install, uninstall, get-, set-properties, get-id, get-, set-default work as usual. Also there is a new feature in ConHost.exe. I am using build 18272 in VirtualBox.

Out of curiosity, why do you introduced the 15 seconds delay in Lx instance termination? The release notes didn't say something about that.

[benhillis]

@Biswa96 - "My car isn't broken, I can open the door, turn on the lights, adjust the seats, I just can't start it!"

[Loongphy]

my god！！I have been struggling with this problem for 3 hours !!

[dinfyru]

So what we can do for work now?

[Biswa96]

@dinfyru

If you've installed this build you can roll back to the previous Windows build using “Go back to the previous version of Windows 10” in Settings->Update & Security->Recovery.

[refack]

Unfortunately not, I suggest rolling back.

Ahhh 😨 I have this bad situation with a faulty piece of hardware, in order to easily rollback I need this key in my registry (Including in the PE environment):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_SanDisk&Prod_SSD_i100_24GB\4&5120a8e&0&010000]
"ConfigFlags"=dword:00000041

Can anyone give me a simple recipe for that?

(I'm nimble with DISM, I know how to mount R:\Recovery\WindowsRE\Winre.wim, and I have a licence to ntlite and I've used Win10PE before. I just can't seem to grok how to slipstream a simple reg change into the update pipeline. ETOOMANYGUIDES)

[benhillis]

If you can not tolerate the occasional bug, the insider fast ring is likely not a good fit for you.

[refack]

If you can not tolerate the occasional bug, the insider fast ring is likely not a good fit for you.

@benhillis I can and I'm aware, and in general I'm a very happy insider (fast ring, and jump ahead). Above all as a fellow developer I appreciate the great work y'all are doing. And the agility you manage to achieve (within a huge corp nonetheless) with insider builds 💚

If anyone could help me it will make the the difference between a 1 hour rollback, and an all nighter.
The fault is with a 20GB onboard SSD, it's broken just so that the BIOS/UEFI recognizes it and tries to query it until it times out. That's about 30 minutes each time. This turns an update/rollback cycle from 1h (when I convert the UUP to WIM, mount it and add that key to the PE registry) to ~12 hours.

I obviously could just wait till tonight, but if anyone can help that would be much much appreciated 🙏

[refack]

Took the rollback over the night, now I'm back on 18267 and WSL is working great.
Again, thank you all for making WSL such a valuable part of my toolkit 🎩

[fenchu]

There was a new version of hyper-v aswell. having spend 2hours upgrading all my vms, I rather use cygwin.

[benhillis]

Fixed in 18277.

[ramyd-a5]

this is fixed in the latest update: 18277

[Biswa96]

Ya, it works in new build 18277. Happy WSL-ing!

@benhillis It looks like there was a Swiss Army knife beside driver seat in our old car ;)

[refack]

Confirm fixed:

Thank you all again!

[mqudsi]

@therealkenc - No problem. I feel bad about this but luckily the rollback mechanism works well and is actually surprisingly fast.

The only problem I have with the rollback mechanism is that afterwards Windows Update always tries to reinstall the same build I rolled back.

[therealkenc]

afterwards Windows Update always tries to reinstall the same build I rolled back

'Relax' said the night man,
We are programmed to receive.
You can roll back any time you like,
But you can never leave. 🎵

[benhillis]

@therealkenc - I hate the f'ng eagles, man!

[djensen47]

@mqudsi The only problem I have with the rollback mechanism is that afterwards Windows Update always tries to reinstall the same build I rolled back.

What I do is "Pause Updates" and then you don't need to worry about it. 😃

[Biswa96]

Apology for hijacking this issue 🙇‍♂️ Sometimes while I'm (ab)using with LxBus internals in build 18277 I got 50% CPU usage with /init process. Should I post that in a separate issue?

[benhillis]

@Biswa96 - sure, create a new issue with some proof of concept code and I can take a look.