Using Windows Terminal as default WSL launcher? - windows-subsystem-for-linux

When I click 'Open linux shell here' inside a directory, it opens the default Microsoft Windows Subsystem for Linux Launcher.
Is it possible to make Windows Terminal the default WSL launcher?
So when I click 'Open linux shell here' it opens the Windows Terminal (Ubuntu).

This is an easy quick answer. No you can't. However the latest Insider build of Windows ships with Windows Terminal and is in process of becoming the default terminal used. So once that's done, then the answer will be "yes, it will be done automatically". We just need some patience. I would instead recommend taking advantage of the "Open Windows Terminal here" instead and set Ubuntu as your default profile to launch. Similarly, you could run a wt argument to launch Ubuntu that wouldn't rely on switching the default profile. This can be done both inside WT itself on the CLI and in the Command Palette or from a normal CMD/PS window.

Related

How to type in the Windows Ubuntu terminal while a windows exe is processing?

Typically in most terminals I've worked with (for instance, powershell or OSX's built-in "terminal") if you start typing your next command while the previous is still running, the terminal will receive your keyboard inputs and insert them anyway.
With the windows ubuntu terminal, all my keystrokes while the current command is running are lost.
This seems to only happen when I run a windows exe through the ubuntu terminal.
For example, this suppresses all my keyboard input: "ping.exe windows.com", while using ubuntu's ping does not: "ping windows.com"
Is there a fix to make it so that my keyboard input is not suppressed when running windows tools in the ubuntu terminal? I find this valuable since I often being typing the next command while the previous is still running.

Need to restart wsl everytime after Windows start before using vscode-remote

I'm running Windows 10 with WSL2. I'm using VSCode with the Remote - WSL extension to open the files from my wsl file system.
When I boot my Windows laptop, and open VSCode I get the following error:
When I perform a wsl.exe --shutdown in PowerShell, and restart Docker Desktop, Everything works fine. But I have to do this after every laptop restart.
Remote WSL extension version: v0.51.4
Visual Studio Code version: v1.51.1
Windows version: 10.0.19041 Build 19041
Someone any idea?
I have had this problem several times, and I have found that on Windows 10 20H2 one of the two options described below solves the problem.
Network reset
This option can make you lose your network configuration, so use it with discretion and read every warning. You can perform this task by going to Settings > Network & Internet > Status. There you need to click on the option "Network reset" after that, you can start the network reset by clicking on "Reset now" Picture of Windows 10 20H2 status section. Then you will need to wait some minutes until your PC is restarted automatically and try to execute Visual Studio Code under WSL2 again.
Reset Windows
This option is dangerous as it will remove either all your files and programs or all your installed programs. You select what you want to remove before starting the reset process. This option can be performed by going to Settings > Update & Security > Recovery. Then you have to click on the button "Get started" on the section "Reset this PC" and follow the instructions provided by the reset tool Picture of Windows 10 20H2 recovery section. After your Windows is reset, you will have to configure your WSL again because all your WSL files will be lost when executing this operation.

Installing drivers in Windows 8 silently without OS prompts(pop ups)

We have a device with Windows 8 embedded OS. We need to install cypress USB drivers while updating our application and do it silently without any OS pop ups, as users won't have input device to accept the prompt dialog.
I have used PNPUtil.exe and DpInst.exe with /S /Q option combinations. Either installation does not happen or it happens with OS prompt.
I tried signing our drivers with code sign certificate still there OS prompt pops up.
I have also tried disabling EnableLUA option in the registry, but still issue exists.
I have used following to tools with all relevant flags, still we could not suppress the OS prompt.
pnputil.exe /S -i -a Drivers/win8/x86/
dpinst-x86.exe /S /PATH Drivers/win8/x86/
I would like to know :
Whether this is possible?
Does any installer framework support such installation?
Can creating a sub process and making it install the drivers in a programmatic way serve the purpose?
Can we modify the registry to suppress these prompts?
NOTE: if I could I would have left this as a comment.
For this scenario I've always used DISM. You can mount your image and install software, drivers or anything you like and then silently blast the image onto a machine. If reinstalling isn't an option please disregard.
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism---deployment-image-servicing-and-management-technical-reference-for-windows

An after-build copy command compatible with Windows and Linux at the same time

I'm developing C# using Mono and MonoDevelop in Windows and Ubuntu. I might code the same project in Windows today and tomorrow in Ubuntu (which is why I chose Mono and MonoDevelop).
In project properties I need to add some After Build commands to copy some projects compiled files into some alternate folders. And I've done this like so:
cp ${TargetFile} ${SolutionDir}/SomePorject/bin/${ProjectConfigName}/Plugins
While this command works perfectly in my Ubuntu machine, each time I'm using Windows my Build requests get canceled since this command can not be executed in Windows (there's no cp in Windows). It makes this a pain to switch between Ubuntu and Windows since each time I need to change these commands.
Now my question is, is there a copy command which works in Windows and Ubuntu alike? Or maybe MonoDevelop has come up with a copy command of its own which works according to the OS it is running under!
I think "configurations" is your way to go.
Create separate configurations for each platform (Right click on solution -> options -> configurations). After that, in "Custom commands" create two "After Build" commands, one for Windows, and other for Ubuntu.
When you build solution just choose your platform from your configurations.
You could install cygwin on your Windows box.

Using Enthought Canopy over SSH+Putty Fails to Start

I have Enthought Canopy installed on a machine running RedHat Enterprise Linux 5. I installed it successfully and can verify it runs.
I would like to be able to use it remotely from a windows computer, I have installed putty + xming for X11 forwarding. I can use regular applications like gedit and firefox fine. However when I try using canopy by launching ~/Canopy/canopy an empty gray box for the welcome screen appears, disappears after a few moments, and canopy exits with no return error without having started.
When I ssh with X forwarding from another linux computer, I can use canopy just fine.
There is no error code, I don't see any debug flags and I can't find any log files. I really have no idea why I cant access canopy with putty and xming.
I am trying this as a solution for interns so they can use a machine with access to our datafiles from their windows computers.
I highly appreciate any and all help.
Canopy needs some features not provided by XMing and a few other X server implementation on windows. See the following article for more details:
https://support.enthought.com/entries/21873380-Running-Canopy-Linux-via-remote-display-VNC-remote-X-display-
In short, use MobaXterm ( http://mobaxterm.mobatek.net/ ) or VcXSrv ( http://sourceforge.net/projects/vcxsrv/ )
EDIT: newer versions of Canopy have fixed this bug and should work fine with XMing