diff --git a/.github/workflows/auto_merge.yml b/.github/workflows/auto_merge.yml
index bf88f1c37..11b59a679 100644
--- a/.github/workflows/auto_merge.yml
+++ b/.github/workflows/auto_merge.yml
@@ -9,7 +9,7 @@ env:
   LABEL_NAME: auto_merge
 jobs:
   automerge:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
     - uses: actions/checkout@v4
       with:
diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml
index 0640c7b32..5aee6c7a0 100644
--- a/.github/workflows/checks.yml
+++ b/.github/workflows/checks.yml
@@ -34,7 +34,7 @@ on:
 jobs:
   get:
     name: Determine what files to check
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Checkout Repo
         uses: actions/checkout@v4
@@ -58,7 +58,7 @@ jobs:
   spellcheck:
     name: Check Spelling
     if: ${{ github.event_name != 'workflow_dispatch' || inputs.checkSpelling }}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     needs: get
     steps:
       - if: ${{! needs.get.outputs.filelist}}
@@ -80,7 +80,7 @@ jobs:
   proselint:
     name: Check Prose
     if: ${{github.event_name != 'workflow_dispatch'|| inputs.checkProse}}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     needs: get
     steps:
       - if: ${{! needs.get.outputs.filelist}}
@@ -100,7 +100,7 @@ jobs:
   mdlint:
     name: Check Markdown
     if: ${{github.event_name != 'workflow_dispatch' || inputs.checkMarkdown}}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     needs: get
     steps:
       - if: ${{! needs.get.outputs.filelist}}
@@ -120,7 +120,7 @@ jobs:
   metacheck:
     name: Check page meta
     if: ${{github.event_name != 'workflow_dispatch'|| inputs.checkMeta}}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     needs: get
     steps:
       - if: ${{ ! needs.get.outputs.filelist}}
@@ -137,7 +137,7 @@ jobs:
   testBuild:
     name: Test build
     if: ${{github.event_name != 'workflow_dispatch' || inputs.testBuild}}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     needs: get
     steps:
       - uses: actions/checkout@v4
diff --git a/.github/workflows/demo_deploy.yml b/.github/workflows/demo_deploy.yml
index b110d7723..523f7d12f 100644
--- a/.github/workflows/demo_deploy.yml
+++ b/.github/workflows/demo_deploy.yml
@@ -13,7 +13,7 @@ jobs:
   demo-deploy:
     continue-on-error: true
     name: Trigger test deployments
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Trigger Workflow in Another Repository
         run: |
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index d40c7e234..9759243a2 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -16,7 +16,7 @@ permissions:
 jobs:
   documentation:
     name: Build documentation
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
diff --git a/.github/workflows/fetch_includes.yml b/.github/workflows/fetch_includes.yml
index c94121b69..f0dc6e1de 100644
--- a/.github/workflows/fetch_includes.yml
+++ b/.github/workflows/fetch_includes.yml
@@ -11,7 +11,7 @@ env:
   BRANCH_NAME: "assets-update"
 jobs:
   fetch-includes:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: "Set Up Env"
         uses: actions/checkout@v4
diff --git a/docs/Scientific_Computing/Terminal_Setup/VSCode.md b/docs/Scientific_Computing/Terminal_Setup/VSCode.md
index 74ef57d5e..240a54163 100644
--- a/docs/Scientific_Computing/Terminal_Setup/VSCode.md
+++ b/docs/Scientific_Computing/Terminal_Setup/VSCode.md
@@ -1,7 +1,7 @@
 ---
 created_at: 2024-08-05
 description: How to set up Visual Studio Code to access the NeSI cluster
-tags: [ide, code]
+tags: [ide, code, visual studio code, vscode]
 ---
 
 'Visual Studio Code' (not to be confused with 'Visual Studio') or 'VSCode', is a popular editor/IDE with many useful extensions.
@@ -15,6 +15,19 @@ The 'Remote' extension allows you to connect to a remote computer (like NeSI).
     2. In VSCode, open the 'Extensions' Tab, search `remote` and make sure you have 'Remote - SSH' and 'Remote Explorer' by Microsoft, installed.
     ![vscode remote extension](../../assets/images/vscode-remote.png)
 === "Windows"
+    1. In VSCode, open the 'Extensions' Tab, search `remote` and make sure you have 'Remote - SSH' and 'Remote Explorer' by Microsoft installed.
+    ![vscode remote extension](../../assets/images/vscode-remote.png)
+    2. Open the 'Remote Explorer' Tab, then click on the 'Open SSH Config file' (gear symbol).
+    If you are prompted to create a file, the first option is fine.
+    ![vscode remote explorer](../../assets/images/vscode-remote-windows.png)
+    3. Set up your SSH Config file as described in Step 2 of [Terminal Setup](Standard_Terminal_Setup.md#first-time-setup).
+    4. Remove or comment out the `Control Path` line under `Host *`.
+    !!! warning
+        As Windows does not support SSH sockets, you will have to enter your password and second factor every time you open a new tab.
+        If this bothers you, you may want to consider the next option "Windows via WSL".
+=== "Windows via WSL"
+    !!! danger
+        This method may not work anymore. Only attempt if you have too much time on your hands.
     1. Set up WSL as described in
     [Windows Subsystem for Linux (WSL)](Windows_Subsystem_for_Linux_WSL.md).
     2. In VSCode, open the 'Extensions' Tab, search `remote` and make sure you have 'Remote - SSH' and 'Remote Explorer' by Microsoft installed.
diff --git a/docs/assets/images/vscode-remote-windows.png b/docs/assets/images/vscode-remote-windows.png
new file mode 100644
index 000000000..deb5d68d3
Binary files /dev/null and b/docs/assets/images/vscode-remote-windows.png differ