From 30baf3ec6a11af515e9543487ce6b7afa873a7cd Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:06:08 -0800 Subject: [PATCH 01/12] Add ubuntu/snapcraft endpoints --- windows/deployment/do/delivery-optimization-endpoints.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/do/delivery-optimization-endpoints.md b/windows/deployment/do/delivery-optimization-endpoints.md index 79e8211757..2dfd4d8e9e 100644 --- a/windows/deployment/do/delivery-optimization-endpoints.md +++ b/windows/deployment/do/delivery-optimization-endpoints.md @@ -36,4 +36,5 @@ Use the table below to reference any particular content types or services endpoi | *.assets1.xboxlive.com, *.assets2.xboxlive.com, *.dlassets.xboxlive.com, *.dlassets2.xboxlive.com, *.d1.xboxlive.com, *.d2.xboxlive.com, *.assets.xbox.com, *.xbl-dlassets-origin.xboxlive.com, *.assets-origin.xboxlive.com, *.xvcb1.xboxlive.com, *.xvcb2.xboxlive.com, *.xvcf1.xboxlive.com, *.xvcf2.xboxlive.com | HTTP / 80 | Xbox | | Both | | *.tlu.dl.adu.microsoft.com, *.nlu.dl.adu.microsoft.com, *.dcsfe.prod.adu.microsoft.com | HTTP / 80 | Device Update | [Complete list](/azure/iot-hub-device-update/) of endpoints for Device Update updates. | Both | | *.do.dsp.mp.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft Connected Cache -> Delivery Optimization Services communication | [Complete list](../do/waas-delivery-optimization-faq.yml) of endpoints for Delivery Optimization only. | Connected Cache Managed in Azure | -| *.azure-devices.net, *.global.azure-devices-provisioning.net, *.azurecr.io, *.blob.core.windows.net, *.mcr.microsoft.com, github.com | AMQP / 5671
MQTT / 8883
HTTPs / 443 | IoT Edge / IoT Hub communication| [Complete list](/azure/iot-hub/iot-hub-devguide-protocols) of Azure IoT Hub communication protocols and ports. [Azure IoT Guide](/azure/iot-hub/iot-hub-devguide-endpoints) to understanding Azure IoT Hub endpoints. | Connected Cache Managed in Azure | +| *.azure-devices.net, *.global.azure-devices-provisioning.net, *.azurecr.io, *.blob.core.windows.net, *.mcr.microsoft.com, github.com | HTTPs / 443 | IoT Edge / IoT Hub communication| [Complete list](/azure/iot-hub/iot-hub-devguide-protocols) of Azure IoT Hub communication protocols and ports. [Azure IoT Guide](/azure/iot-hub/iot-hub-devguide-endpoints) to understanding Azure IoT Hub endpoints. | Connected Cache Managed in Azure | +| *.ubuntu.com, api.snapcraft.io | HTTP / 80
HTTPs / 443 | Ubuntu package updates | Used to deploy Connected Cache to Windows host machines. | Connected Cache Managed in Azure | From 287ff269718ba555310d8a1b02277d7305e44cf5 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:07:12 -0800 Subject: [PATCH 02/12] Update known issues page --- windows/deployment/do/mcc-ent-troubleshooting.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index 9e896b0acf..a602264680 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -23,8 +23,6 @@ This article contains instructions on how to troubleshoot different issues you m This section describes known issues with the latest release of Microsoft Connected Cache for Enterprise and Education. See the [Release Notes page](mcc-ent-release-notes.md) for more details on the fixes included in the latest release. -### Cache node monitoring chart in the Azure portal user interface displays incorrect information - ### Script provisionmcconwsl.ps1 fails when executed on a Windows 11 host machine configured to use Japanese language In the Connected Cache installation script (provisionmcconwsl.ps1), the check processing is executed until the value of the last execution code (Last Result) of the installation task becomes 0 in the following processing. However, in Japanese OS, the return value is null because "Last Result" is displayed, and an exception occurs. From ebf63cf1df4fe46e1b0e8a302ce784de04055efb Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:09:39 -0800 Subject: [PATCH 03/12] Added packages.microsoft.com to endpoints --- windows/deployment/do/delivery-optimization-endpoints.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/do/delivery-optimization-endpoints.md b/windows/deployment/do/delivery-optimization-endpoints.md index 2dfd4d8e9e..3bc2a48d9b 100644 --- a/windows/deployment/do/delivery-optimization-endpoints.md +++ b/windows/deployment/do/delivery-optimization-endpoints.md @@ -38,3 +38,4 @@ Use the table below to reference any particular content types or services endpoi | *.do.dsp.mp.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft Connected Cache -> Delivery Optimization Services communication | [Complete list](../do/waas-delivery-optimization-faq.yml) of endpoints for Delivery Optimization only. | Connected Cache Managed in Azure | | *.azure-devices.net, *.global.azure-devices-provisioning.net, *.azurecr.io, *.blob.core.windows.net, *.mcr.microsoft.com, github.com | HTTPs / 443 | IoT Edge / IoT Hub communication| [Complete list](/azure/iot-hub/iot-hub-devguide-protocols) of Azure IoT Hub communication protocols and ports. [Azure IoT Guide](/azure/iot-hub/iot-hub-devguide-endpoints) to understanding Azure IoT Hub endpoints. | Connected Cache Managed in Azure | | *.ubuntu.com, api.snapcraft.io | HTTP / 80
HTTPs / 443 | Ubuntu package updates | Used to deploy Connected Cache to Windows host machines. | Connected Cache Managed in Azure | +| packages.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft package updates | Used to deploy Connected Cache to Windows and Linux host machines. | Connected Cache Managed in Azure | From 2dae80083b8cb477138cb63c923ab70a64868bb2 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:21:07 -0800 Subject: [PATCH 04/12] Install script v2.0.0.2 release notes --- windows/deployment/do/mcc-ent-release-notes.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 28471a7fb7..4f9a0b4e30 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -18,6 +18,18 @@ ms.date: 10/30/2024 This article contains details about the latest releases of Connected Cache. Since Connected Cache is a preview service, some releases may contain breaking changes. +## Install script v2.0.0.2 + +Released on **2/5/2025** + +These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you will need to re-deploy your existing cache nodes using the updated installation script. + +### Feature updates + +- **Removes dependency on AMQP/MQTT ports**: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group. +- **Improves cleanup during uninstall**: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the `uninstallmcconwsl.ps1` script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache. +- **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability. + ## Release v1.2.1.2076_E (public preview launch) The public preview released on **10/30/2024** From 85227fc618327c3432aba237d7a000a8e1948e38 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Tue, 4 Feb 2025 15:35:06 -0800 Subject: [PATCH 05/12] Retitle feature updates to improvements in release notes --- windows/deployment/do/mcc-ent-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 4f9a0b4e30..fb5b1e5eb5 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -24,7 +24,7 @@ Released on **2/5/2025** These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you will need to re-deploy your existing cache nodes using the updated installation script. -### Feature updates +### Improvements - **Removes dependency on AMQP/MQTT ports**: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group. - **Improves cleanup during uninstall**: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the `uninstallmcconwsl.ps1` script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache. From 2f3ae7ec767dfa988aa59ff411c3c196822aaca3 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Wed, 5 Feb 2025 09:40:54 -0800 Subject: [PATCH 06/12] Add proxy install to release notes --- windows/deployment/do/mcc-ent-release-notes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index fb5b1e5eb5..b866870600 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -29,6 +29,7 @@ These changes only affect the installation scripts for Connected Cache. To take - **Removes dependency on AMQP/MQTT ports**: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group. - **Improves cleanup during uninstall**: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the `uninstallmcconwsl.ps1` script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache. - **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability. +- **Uses proxy to perform install if configured**: If proxy is enabled in its configuration, the Windows-hosted cache node will use the configured proxy host name during installation. ## Release v1.2.1.2076_E (public preview launch) From ace00ab40695563af94a34f3df091235362f4014 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:28:27 -0800 Subject: [PATCH 07/12] revise proxy wording on release notes --- windows/deployment/do/mcc-ent-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index b866870600..8596a20961 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -29,7 +29,7 @@ These changes only affect the installation scripts for Connected Cache. To take - **Removes dependency on AMQP/MQTT ports**: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group. - **Improves cleanup during uninstall**: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the `uninstallmcconwsl.ps1` script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache. - **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability. -- **Uses proxy to perform install if configured**: If proxy is enabled in its configuration, the Windows-hosted cache node will use the configured proxy host name during installation. +- **Uses configured proxy to perform install**: If a proxy was configured for the Windows-hosted cache node in Azure Portal, the cache node will use the specified proxy during installation. ## Release v1.2.1.2076_E (public preview launch) From 837625d0c9c123687bda525191b04c5bfa34ca46 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:34:15 -0800 Subject: [PATCH 08/12] Added note to prereqs about connection limit --- windows/deployment/do/mcc-ent-prerequisites.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index f30f503e31..f8ddaef129 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -30,6 +30,8 @@ This article details the requirements and recommended specifications for using M - [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916) - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans) + Note that there is no limit to the number of licensed machines that may concurrently download from a Connected Cache node. + ## Cache node host machine requirements ### General requirements From cf039a5a2ecd3379bc3f407a295b00d2d2a8caba Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:50:29 -0800 Subject: [PATCH 09/12] Adding GPO guidance to troubleshooting --- windows/deployment/do/mcc-ent-troubleshooting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index a602264680..ac07cde399 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -80,6 +80,10 @@ You can expect to see the following types of log files: 1. **WSL_Mcc_UserUninstall_Transcript**: This log file records the output of the "uninstallmcconwsl.ps1" script that the user can run to uninstall MCC software from the host machine. 1. **WSL_Mcc_Uninstall_FromRegisteredTask_Transcript**: This log file records the output of the "MCC_Uninstall_Task" scheduled task that is responsible for uninstalling the MCC software from the host machine when called by the "uninstallmcconwsl.ps1" script. +### Group Policy Object conflicts with Scheduled Task registration + +Enabling the Group Policy Object: ["Network access: Do not allow storage of passwords and credentials for network authentication"](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-access-do-not-allow-storage-of-passwords-and-credentials-for-network-authentication) will prevent the Connected Cache software from registering the scheduled tasks necessary for successful cache node registration and operation. + ### WSL2 fails to install with message "A specified logon session doesn't exist" If you're encountering this failure message when attempting to run the PowerShell command `wsl.exe --install --no-distribution` on your Windows host machine, verify that you're logged on as a local administrator and running the command from an elevated PowerShell window. From de7a95e0c6aca58f5e465b0008b2b1dccbcfd18b Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:55:17 -0800 Subject: [PATCH 10/12] Revise language for ubuntu endpoint --- windows/deployment/do/delivery-optimization-endpoints.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/delivery-optimization-endpoints.md b/windows/deployment/do/delivery-optimization-endpoints.md index 3bc2a48d9b..1f8366e62b 100644 --- a/windows/deployment/do/delivery-optimization-endpoints.md +++ b/windows/deployment/do/delivery-optimization-endpoints.md @@ -37,5 +37,5 @@ Use the table below to reference any particular content types or services endpoi | *.tlu.dl.adu.microsoft.com, *.nlu.dl.adu.microsoft.com, *.dcsfe.prod.adu.microsoft.com | HTTP / 80 | Device Update | [Complete list](/azure/iot-hub-device-update/) of endpoints for Device Update updates. | Both | | *.do.dsp.mp.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft Connected Cache -> Delivery Optimization Services communication | [Complete list](../do/waas-delivery-optimization-faq.yml) of endpoints for Delivery Optimization only. | Connected Cache Managed in Azure | | *.azure-devices.net, *.global.azure-devices-provisioning.net, *.azurecr.io, *.blob.core.windows.net, *.mcr.microsoft.com, github.com | HTTPs / 443 | IoT Edge / IoT Hub communication| [Complete list](/azure/iot-hub/iot-hub-devguide-protocols) of Azure IoT Hub communication protocols and ports. [Azure IoT Guide](/azure/iot-hub/iot-hub-devguide-endpoints) to understanding Azure IoT Hub endpoints. | Connected Cache Managed in Azure | -| *.ubuntu.com, api.snapcraft.io | HTTP / 80
HTTPs / 443 | Ubuntu package updates | Used to deploy Connected Cache to Windows host machines. | Connected Cache Managed in Azure | -| packages.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft package updates | Used to deploy Connected Cache to Windows and Linux host machines. | Connected Cache Managed in Azure | +| *.ubuntu.com, api.snapcraft.io | HTTP / 80
HTTPs / 443 | Ubuntu package updates | Used by Linux distribution image in WSL on Windows host machine to deploy Connected Cache. | Connected Cache Managed in Azure | +| packages.microsoft.com | HTTP / 80
HTTPs / 443 | Microsoft package updates | Used to deploy required Connected Cache packages to Windows and Linux host machines. | Connected Cache Managed in Azure | From e5ed38e6621f15383c35d7269d02f3c2702b8f26 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 6 Feb 2025 11:57:09 -0800 Subject: [PATCH 11/12] Acrolinx fixes to release notes --- windows/deployment/do/mcc-ent-release-notes.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 8596a20961..7a69747aff 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -20,27 +20,27 @@ This article contains details about the latest releases of Connected Cache. Sinc ## Install script v2.0.0.2 -Released on **2/5/2025** +Released on **2/7/2025** -These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you will need to re-deploy your existing cache nodes using the updated installation script. +These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you'll need to redeploy your existing cache nodes using the updated installation script. ### Improvements - **Removes dependency on AMQP/MQTT ports**: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group. - **Improves cleanup during uninstall**: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the `uninstallmcconwsl.ps1` script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache. - **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability. -- **Uses configured proxy to perform install**: If a proxy was configured for the Windows-hosted cache node in Azure Portal, the cache node will use the specified proxy during installation. +- **Uses configured proxy to perform install**: If a proxy was configured for the Windows-hosted cache node in Azure portal, the cache node uses the specified proxy during installation. ## Release v1.2.1.2076_E (public preview launch) The public preview released on **10/30/2024** -For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux and Windows host machines. Please see the [early preview documentation page](mcc-ent-early-preview.md) for more details. +For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux and Windows host machines. See the [early preview documentation page](mcc-ent-early-preview.md) for more details. ### Feature updates - **Metrics and charts in Azure portal**: You can now visualize *Outbound egress* and *Volume by Content type* charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal. -- **Cache nodes for Windows or Linux host machines**: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by simply choosing the OS when creating cache nodes. +- **Cache nodes for Windows or Linux host machines**: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by choosing the OS when creating cache nodes. - **Ubuntu 22.04 LTS**: Cache nodes can now be deployed on Ubuntu 22.04 LTS. - **Azure CLI support**: Cache nodes can now be created and managed via Azure CLI. - **Proxy**: We added support for unauthenticated proxy and cloud proxy integration. From dc623da946946d931abc79fa25f554f3186f7c38 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 6 Feb 2025 12:05:12 -0800 Subject: [PATCH 12/12] Update windows/deployment/do/mcc-ent-troubleshooting.md fix link --- windows/deployment/do/mcc-ent-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index ac07cde399..fd4a693300 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -82,7 +82,7 @@ You can expect to see the following types of log files: ### Group Policy Object conflicts with Scheduled Task registration -Enabling the Group Policy Object: ["Network access: Do not allow storage of passwords and credentials for network authentication"](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-access-do-not-allow-storage-of-passwords-and-credentials-for-network-authentication) will prevent the Connected Cache software from registering the scheduled tasks necessary for successful cache node registration and operation. +Enabling the Group Policy Object: [Network access: Do not allow storage of passwords and credentials for network authentication](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-access-do-not-allow-storage-of-passwords-and-credentials-for-network-authentication) will prevent the Connected Cache software from registering the scheduled tasks necessary for successful cache node registration and operation. ### WSL2 fails to install with message "A specified logon session doesn't exist"