\n\nThis page has been machine-translated from the original page.
\n
I built a PC with parts I picked up during Prime Day, so while setting up a fresh environment, I put together these notes on setting up a Windows 10 environment.
\nThis article includes the following:
\nWith that out of the way, let’s start setting things up right after a clean install.
\n\nThis time, I clean-installed Windows 10 on a PC built with an ASUS motherboard, the TUF GAMING Z490-PLUS, so I first needed to install drivers in order to get things like internet connectivity working.
\nI installed the drivers from the CD-R that came with the motherboard.
\nRun Windows Update from [Settings] in Windows.\nA restart is required after it completes.
\nFrom [Control Panel] > [Network and Internet], change the network adapter settings.\nThis time I was not assigning a static IP address, so I left that setting alone.
\nNext, enable network discovery only on [Private network] so that remote connections can be made by host name.
\nEnable Remote Desktop connections from [Control Panel].
\nI think it is fine to disable Remote Assistance.
\nAlso, although I am not changing it this time, if you want to change the RDP listening port, edit the following registry entry.
\nI uninstalled every preinstalled application I do not use.
\nI removed games, Skype, OneNote, and so on.
\nCustomize the Windows keyboard layout to better match your preferences.
\nFirst, create a file named [changekey.reg] in Notepad and enter the following.
\nWindows Registry Editor Version 5.00\n\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Keyboard Layout]\n\"Scancode Map\"=hex:00,00,00,00,00,00,00,00,06,00,00,00,1d,00,3a,00,4b,e0,70,00,\\\n 4d,e0,38,e0,0e,00,7b,00,7b,00,36,00,00,00,00,00I summarized the key remapping used here in the following article, so feel free to customize it as you like.
\n\nDouble-clicking the registry file you created will write the keyboard layout changes into the registry.
\nThe changed registry settings take effect after a restart.
\nEven without changing registry keys, you can customize some key input behavior from [IME settings].
\nThe [IME settings] available from [Settings] do not yet cover every setting, so first turn on compatibility mode.
\nThen, from [Advanced IME Settings], I changed the following.
\nIf it concerns you, I think it is also a good idea to disable the setting that sends input history to Microsoft.
\nChange the host name from [Settings] and restart.
\nFirst, sign in with your Microsoft account.
\nOnce you do that, the login method is forcibly switched to sign-in with the Microsoft account, so change it back to [Sign in with a local account instead] from [Account settings].
\nThis is to reduce the hassle of remote connections within my home network.
\nFrom [Personalization], change the taskbar position, apply a theme, and change the background and colors.
\nWhatever you prefer.
\nFrom [Turn Windows features on or off], enable the following features.
\nFor now, install them with apt. Next, install Docker on the Ubuntu environment where WSL2 has been enabled. The procedure in the official documentation is fine. Next, make it possible to run Docker without sudo privileges. See here for details. Normally you just register the public key created with ssh-keygen in GitHub, but I run into the same trap every time, so I am writing it down here. Connecting to GitHub with SSH - GitHub Docs That is because when you try to connect to GitHub over SSH, you may see an error like this. To resolve this problem, create .ssh/config and run ssh-add. In my environment, I name the private key for GitHub [github], so I create .ssh/config as follows. Also, for some reason ssh-agent is sometimes not running, so start it as well. (At worst, write it into .bashrc or something similar…) With this, I was able to connect to GitHub from WSL over SSH. Here is the command to check. I installed VSCode extensions like this. Next, enable Hyper-V and configure the virtual switches. First, run the following command in PowerShell started with administrator privileges, then restart the OS. This lets you connect to the local host service from Hyper-V Manager, so create the following three networks from the [Virtual Switch] settings. I will omit the details here, but after this I will set up the virtual machines. I also divided a partition for storing virtual machine disks just in case.\nIdeally, a separate disk would be better, but since I still have plenty of space left on the M.2 SSD, I am using partitions for now.Install Various Packages in WSL
\nsudo apt update && sudo apt upgrade -y\nsudo apt install vim \\\n make \\\n python3.8 \\\n python3-pip \\\n unzip \\\n zip \\\n build-essential \\\n ufw \\\n python3.8-dev \\\n gdb \\\n yara \\\n radare2 \\\n ltrace \\\n strace \\\n -ysudo gpasswd -a $USER docker\nsudo chown \"$USER\":\"$USER\" /home/\"$USER\"/.docker -R\nsudo chmod g+rwx \"/home/$USER/.docker\" -RConnect to GitHub from WSL over SSH
\nWarning: Permanently added the RSA host key for IP address '13.114.40.48' to the list of known hosts.\ngit@github.com: Permission denied (publickey).\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.$ cat .ssh/config\nHost github\nUser git\nHostname github.com\nPort 22\nIdentityFile ~/.ssh/githubeval `ssh-agent`\nssh-add ~/.ssh/githubssh-add -lInstall VSCode Extensions
\nHyper-V Settings
\nEnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All\n
\n