Ubuntu 20.04 on a Win10 Home with WSL2 installed. No sudo!
by Snugbug from LinuxQuestions.org on (#5MKZQ)
Please note, even when I'm going to talk about Win10 in this thread, this issue is actually about Ubuntu in the end.
Well, most likely, you will understand as you go on reading...
On a Win10 Home 21H1, I managed to install Hyper-V, which is not supported by the Home version by default, by using this script. Sorry, for using a deep link here, but since that zip is from a german page and many of you probably won't understand that language, I think, I show you the relevant part of that page only, by pointing you directly to the mentioned script.
Then I installed the WSL2 Kernel Update (see section "Step 4") and Ubuntu 20.0 from the MS-Shop, followed this guide to change the RDP port, as well as the resolution, followed by enabling the dbus and starting the xrdp server.
I've also set WSL2 to default with this command:
Code:wsl --set-default-version 2With...
Code:ip addr...I found the IP to be used for RDP and with...
Code:mstsc...I opened the Remote Desktop Connection tool of Win10 and finally, I got into the GUI of Ubuntu 20.04, similar to what it's like in a VNC connection.
So, from the Windows point of view, everything seems to be working, but now, the problem is, that I cannot open Synaptic as sudo, but without sudo Synaptic doesn't make sense, because I cannot install anything from there. Besides, I cannot use sudo anyway, there, no matter what I'm trying that for.
Does anybody have an idea how to fix this, please?
My goal is to use Ubuntu just as if it was installed on its own partition.
I would rather have done it using the ordinary way with partitioning, anyway, but since this is all about a "Surface Book 3", which (by Microsoft themself, I guess) is very heavily blocked against an installation of a 2nd OS, using WSL2 seemed to me the only chance left, to have a Linux on that device.
By "heavily" I mean, there is TPM2.0 (I don't want to destroy it), Bitlocker and Secure-Boot, which cannot be disabled without getting un ugly red banner with a padlock on the boot screen.
Well, most likely, you will understand as you go on reading...
On a Win10 Home 21H1, I managed to install Hyper-V, which is not supported by the Home version by default, by using this script. Sorry, for using a deep link here, but since that zip is from a german page and many of you probably won't understand that language, I think, I show you the relevant part of that page only, by pointing you directly to the mentioned script.
Then I installed the WSL2 Kernel Update (see section "Step 4") and Ubuntu 20.0 from the MS-Shop, followed this guide to change the RDP port, as well as the resolution, followed by enabling the dbus and starting the xrdp server.
I've also set WSL2 to default with this command:
Code:wsl --set-default-version 2With...
Code:ip addr...I found the IP to be used for RDP and with...
Code:mstsc...I opened the Remote Desktop Connection tool of Win10 and finally, I got into the GUI of Ubuntu 20.04, similar to what it's like in a VNC connection.
So, from the Windows point of view, everything seems to be working, but now, the problem is, that I cannot open Synaptic as sudo, but without sudo Synaptic doesn't make sense, because I cannot install anything from there. Besides, I cannot use sudo anyway, there, no matter what I'm trying that for.
Does anybody have an idea how to fix this, please?
My goal is to use Ubuntu just as if it was installed on its own partition.
I would rather have done it using the ordinary way with partitioning, anyway, but since this is all about a "Surface Book 3", which (by Microsoft themself, I guess) is very heavily blocked against an installation of a 2nd OS, using WSL2 seemed to me the only chance left, to have a Linux on that device.
By "heavily" I mean, there is TPM2.0 (I don't want to destroy it), Bitlocker and Secure-Boot, which cannot be disabled without getting un ugly red banner with a padlock on the boot screen.