Hacker News Reader

Comment by xaduha | Hacker News Reader

If you're really tired of this shit, then get LTSB.

I'm not sure how LTSB could have prevented this at all. Ironically, 1809 was a LTSB release, so if you were upgrading from 1607 LTSB (to get WSL working, for example), you would also be exposed to this bug.

I just installed WSL on LTSC and it worked great. The MS docs explained it easily enough and provided the proper power shell commands.

Well at the moment LTSB isn't affected is it? So there you go, proof enough. In any case it's not just that, there are lots of other annoying stuff that I don't need in my life.

>Well at the moment LTSB isn't affected is it?

And you know that based on what? The lack of bug reports? The LTSB population is obviously going to be smaller than the general population, so the lack of reports of it happening on LTSB doesn’t really indicate anything. Besides, the task manager bugs introduced in 1809 is in ltsb 1809 AND server 2019, which makes me inclined to believe that all the windows editions come from the same branch anyways.

I don't expect it to have 0 bugs. But generally speaking less features means less bugs. And as I said it's not just about bugs.

From your friendly neighborhood enterprise B2B volume sales team? Or from an illegally shared copy of questionable integrity?

> questionable integrity?

What's what integrity checks are for.

Microsoft aren't the ones supplying the tools to fake a licence, though.

They are welcome to make it easier to obtain LTSB license. They are not interested in that obviously.

Technically there's not much that is stopping me from using it in trial mode with a rearm up to 90 days, because I use it in a VFIO VM anyway. But you probably wouldn't like that either, would you?

We downloaded the 2019 LTSC (1809) and a day later it was pulled. I suppose it has the same problems.

What's LTSB?

https://www.howtogeek.com/273824/windows-10-without-the-cruf...

Reply on news.ycombinator.com