Update stale WSL + VS Code and install-on-server pages

wsl-vscode.md (last reviewed 2021):
- Recommend WSL extension directly; mention Remote Development pack as optional alternative
- Remove outdated VS Code 1.35 minimum version requirement callout
- Replace deprecated Shan.code-settings-sync community extension with VS Code built-in Settings Sync
- Remove 'new' from Windows Terminal (pre-installed on Windows 11); fix profile.json -> settings.json
- Remove deprecated RTVS (R Tools for Visual Studio) link

install-on-server.md (last reviewed 2022):
- Expand Server 2022/2025 section heading; add Server 2025 link and note Server Core 2025 support
- Add wsl --update as the modern kernel update method for Server 2022+; clarify MSI is for Server 2019

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: GrantMeStrength

WSL/install-on-server.md

@@ -1,23 +1,23 @@
 ---
 title: Install Linux Subsystem on Windows Server
 description: Learn how to install the Linux Subsystem on Windows Server. WSL is available for installation on Windows Server 2019 (version 1709) and later.
-ms.date: 06/14/2022
+ms.date: 04/15/2026
 ms.topic: install-set-up-deploy
 ---
 
 # Windows Server Installation Guide
 
 The Windows Subsystem for Linux (WSL) is available for installation on Windows Server 2019 (version 1709) and later. This guide will walk through the steps of enabling WSL on your machine.
 
-## Install WSL on Windows Server 2022 and 2025 Desktop Experience
+## Install WSL on Windows Server 2022 and 2025
 
-[Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022) now supports a simple WSL installation using the command:
+[Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022) and [Windows Server 2025](/windows-server/get-started/whats-new-in-windows-server-2025) support a simple WSL installation using the command:
 
 ```powershell
 wsl.exe --install
 ```
 
-You can now install everything you need to run WSL on Windows Server 2022 by entering this command in an **administrator** PowerShell and then restarting your machine.
+You can now install everything you need to run WSL on Windows Server 2022 or 2025 (including Server Core on 2025) by entering this command in an **administrator** PowerShell and then restarting your machine.
 
 This command will enable the required optional components, download the latest Linux kernel, set WSL 2 as your default, and install a Linux distribution for you *(Ubuntu by default)*.
 
@@ -46,7 +46,13 @@ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-L
 
 ### Install the WSL Kernel update for WSL 2
 
-This is not necessary for server core 2025.
+> [!NOTE]
+> This step is only needed for Windows Server 2019. On Server 2022 and later, use `wsl --update` instead:
+> ```powershell
+> wsl --update
+> ```
+
+For Windows Server 2019, you can install the WSL 2 kernel update using the MSI package:
 
 ```powershell
 Invoke-WebRequest -Uri "https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi" -OutFile ".\wsl_update_x64.msi"

WSL/tutorials/wsl-vscode.md

@@ -2,7 +2,7 @@
 title: Get started using VS Code with WSL
 description: Learn how to set up VS Code to author and debug code using the Windows Subsystem for Linux.
 keywords: wsl, windows, windowssubsystem, gnu, linux, bash, vs code, remote extension, debug, path, visual studio
-ms.date: 09/27/2021
+ms.date: 04/15/2026
 ms.topic: get-started
 ---
 
@@ -25,10 +25,7 @@ Visual Studio Code, along with the WSL extension, enables you to use WSL as your
 
 * When prompted to **Select Additional Tasks** during installation, be sure to check the **Add to PATH** option so you can easily open a folder in WSL using the code command.
 
-* Install the [Remote Development extension pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack). This extension pack includes the WSL extension, in addition to the Remote - SSH, and Dev Containers extensions, enabling you to open any folder in a container, on a remote machine, or in WSL.
-
-> [!IMPORTANT]
-> In order to install the WSL extension, you will need the [1.35 May release](https://code.visualstudio.com/updates/v1_35) version or later of VS Code. We do not recommend using WSL in VS Code without the WSL extension as you will lose support for auto-complete, debugging, linting, etc. Fun fact: this WSL extension is installed in $HOME/.vscode/extensions (enter the command `ls $HOME\.vscode\extensions\` in PowerShell).
+* Install the [WSL extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl). If you also plan to work with remote machines or Dev Containers, you can install the [Remote Development extension pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) instead, which includes the WSL extension along with Remote - SSH and Dev Containers.
 
 ## Update your Linux distribution
 
@@ -86,11 +83,11 @@ To install Git, see [set up Git to work with Windows Subsystem for Linux](./wsl-
 
 ## Install Windows Terminal (optional)
 
-The new Windows Terminal enables multiple tabs (quickly switch between Command Prompt, PowerShell, or multiple Linux distributions), custom key bindings (create your own shortcut keys for opening or closing tabs, copy+paste, etc.), emojis ☺, and custom themes (color schemes, font styles and sizes, background image/blur/transparency). Learn more in the [Windows Terminal docs](/windows/terminal).
+Windows Terminal enables multiple tabs (quickly switch between Command Prompt, PowerShell, or multiple Linux distributions), custom key bindings (create your own shortcut keys for opening or closing tabs, copy+paste, etc.), emojis ☺, and custom themes (color schemes, font styles and sizes, background image/blur/transparency). Windows Terminal comes pre-installed on Windows 11. Learn more in the [Windows Terminal docs](/windows/terminal).
 
 1. Get [Windows Terminal in the Microsoft Store](https://apps.microsoft.com/detail/9N0DX20HK701): By installing via the store, updates are handled automatically.
 
-2. Once installed, open Windows Terminal and select **Settings** to customize your terminal using the `profile.json` file.
+2. Once installed, open Windows Terminal and select **Settings** to customize your terminal using the `settings.json` file.
 
 ## Additional Resources
 
@@ -99,9 +96,8 @@ The new Windows Terminal enables multiple tabs (quickly switch between Command P
 * [Remote development tips and tricks](https://code.visualstudio.com/docs/remote/troubleshooting)
 * [Using Docker with WSL 2 and VS Code](https://code.visualstudio.com/blogs/2020/03/02/docker-in-wsl2)
 * [Using C++ and WSL in VS Code](https://code.visualstudio.com/docs/cpp/config-wsl)
-* [Remote R Service for Linux](/visualstudio/rtvs/setting-up-remote-r-service-on-linux)
 
 A few additional extensions you may want to consider include:
 
 * [Keymaps from other editors](https://marketplace.visualstudio.com/search?target=VSCode&category=Keymaps&sortBy=Downloads): These extensions can help your environment feel right at home if you're transitioning from another text editor (like Atom, Sublime, Vim, eMacs, Notepad++, etc).
-* [Settings Sync](https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync): Enables you to synchronize your VS Code settings across different installations using GitHub. If you work on different machines, this helps keep your environment consistent across them.
+* [Settings Sync](https://code.visualstudio.com/docs/configure/settings-sync): VS Code has built-in Settings Sync that lets you synchronize your settings, extensions, and keybindings across different machines using your GitHub or Microsoft account.