Console used as a WSL terminal has garbled screen on paging

[nicferrier]

The console as a WSL terminal looks broken in the latest builds; I'm on Windows Insider and have build:

17692.red_prerelease.180609.1317

ver output shows:

Microsoft Windows [Version 10.0.17692.1000]

Steps to recreate:

• open a bash terminal, say, ubuntu 16 or 18

• view a file, eg:

  view .bashrc
  

• cursor down a page of lines, so the terminal has to scroll

• see the screen garble and all the lines get compressed to the bottom line

  TERM reports xterm-256color
  

View is just one way to validate, I haven't been able to narrow it down but many things that do sophisticated screen are failing.

• ls -l works
• htop works
• less -r works
• emacs -nw works
• view doesn't work
• vi doesn't work
• vi doesn't work in a remote ssh from the terminal
• tmux doesn't work

Steps to test tmux:

• apt-get install tmux
• tmux new-session
• ls -la
• see the results are garbled at the bottom line

I'm not sure when this broke as I haven't used it that much in the past week.

Any help?

[JoBrad]

This is also happening for me, on Windows 10 build 17692. . I've posted a video of the behavior I'm seeing here: https://imgur.com/a/24bMNoc.

[mkarpoff]

It is still an issue in Windows 10 build 17704

[nicferrier]

Actually I'm pretty sure this is not limited to a WSL shell. It's happening with a standard CMD console as well.

[nicferrier]

No response though. :-(

[alecacco]

Byt hey they fixed Ctrl+s shortcut in notepad! :D Il giorno dom 1 lug 2018 alle ore 13:00 Nic Ferrier < notifications@github.com> ha scritto:

…

No response though. :-( — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#210 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AT-d8NlGjyrxIKYBIfnZd2dJ_-iNaCPGks5uCKvCgaJpZM4UzR5y> .

[miniksa]

This is MSFT:17807270. It just hit the main branch in 17709 and should be fixed in Insiders shortly.

Sorry, we have several people on vacation the last few weeks and scrubbing GitHub has been a lower priority while we're low on people.

[JoBrad]

@miniksa Thanks for the follow-up! Appreciate it!

[nicferrier]

Yeah. I was trying not to be snarky. I didn't feel snarky. Y'all doing an impressive job of moving this stuff that hasn't moved for years.

[nicferrier]

Yep. That fixed it. Thanks!

[toloveru]

Any update on this issue and its resolution? In Fast ring it still seems to be present, and makes the WSL terminal pretty much useless.
I'm still on build 17704 by the way and have disabled Telemetry in the Registry because seeing in the Diagnostic Data Viewer how much my device phones home got me very worried. I would find this very shady if that's why I can't update to 17713 but it seems like this is the case.

[twisty]

@toloveru #210 (comment) states this is fixed in 17709. I can confirm that things got back-to-normal for me in 17711. Once you manage to upgrade to a post-17709 version you should be happy.

If you suspect that you can't update because you "disabled Telemetry in the Registry" you should open a new issue for that.

[miniksa]

I see this fix in the Windows Insiders builds 17711 and higher like @twisty says.

@toloveru, it should be fixed if you update.
If you have concerns about privacy and the data being collected, I recommend you view https://privacy.microsoft.com/en-US/windows-10-feedback-diagnostics-and-privacy or check out the data we have connected to you personally at https://account.microsoft.com/privacy/ and delete it if you like.

I highly doubt someone is intentionally blocking you from updating if you have tinkered with the assorted telemetry registry keys. It just might be that one of the registry keys you disabled also stopped our ability to send back what OS version you are on or the configuration hardware of your machine so we know which build of Windows to send you. I'm not on that team, however, I just know a lot of our "telemetry pipelines" are shared utilities by a bunch of OS components which probably include the updater services.

[toloveru]

@miniksa I realize that this strongly deviates from OP's issue but I don't think that telemetry should be as tightly integrated with the OS as seems to be the case right now. I don't want to send out data about my OS usage at all other than the critical stuff such as e.g. build number and other non-personal stuff upon explicit request by clicking "Update" or periodically as in every day instead of multiple JSON requests to Microsoft per second. If not intentional, it'd be a really bad design. Adding a key (HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection - AllowTelemetry 0) and disabling the Connected User Experiences and Telemetry service shouldn't somehow stop updates from being applied.

As for me, I ended up having to reinstall the OS. Back to stable and contemplated my choice of becoming a telemetry subject in Insiders, just for the dark theme in Windows Explorer. Great and long-awaited feature, but not worth discarding basic privacy rights for. Turns out though that even with Basic telemetry the system still ends up making multiple requests per second for every driver update, app launch or whatever. If only I could make this bloody OS shut up and stop abusing my privacy. Then again, super tight integration, and thanks to Nvidia no option to run Linux like I do everywhere else. Thanks Microsoft!