Update content

Author: v-lianna

support/windows-server/toc.yml

@@ -2728,6 +2728,8 @@ items:
       href: ./virtualization/back-up-hyper-v-vm-from-parent-partition.md
   - name: Configuration of virtual machine settings
     items:
+    - name: Can't access Hyper-V virtual machines via VMConnect
+      href: ./virtualization/cannot-access-hyper-v-virtual-machine-connect.md
     - name: Copy and paste don't work when you connect to Hyper-V virtual machine
       href: ./virtualization/copy-paste-not-work-hyper-v-vm-vmconnect-enhanced-session-mode.md
     - name: Hyper-V limits the maximum number of processors

support/windows-server/virtualization/cannot-access-hyper-v-virtual-machine-connect.md

@@ -1,6 +1,6 @@
 ---
-title: Can't Access Hyper-V Virtual Machines Via VM Connect
-description: Describes a
+title: Can't Access Hyper-V Virtual Machines Via VMConnect
+description: Addresses an issue where you can't connect to Hyper-V virtual machines (VMs) through Virtual Machine Connection (VMConnect) after you repeatedly receive an authentication error.
 ms.date: 08/13/2025
 manager: dcscontentpm
 audience: itpro
@@ -10,72 +10,56 @@ ms.custom:
 - sap:virtualization and hyper-v\configuration of virtual machine settings
 - pcy:WinComm Storage High Avail
 ---
-# Unable to access Hyper-V virtual machines via VM Connect: "Local security authority cannot be contacted"
+# Can't access Hyper-V virtual machines via VMConnect
 
-This article addresses an issue where users are unable to connect to Hyper-V virtual machines (VMs) through VM Connect due to a persistent authentication error. The root cause and resolution steps are provided to help restore functionality.
+This article addresses an issue where you can't connect to Hyper-V virtual machines (VMs) through Virtual Machine Connection (VMConnect) after you repeatedly receive an authentication error.
 
-## Prerequisites
+> [!NOTE]
+> Before proceeding with the following procedures in this article, ensure you have administrative access to the affected server. In addition, you have a working server with the correct Transport Layer Security (TLS) cryptography registry keys to export.
 
-Before proceeding, ensure the following:
+You repeatedly receive an authentication error message:
 
-* Administrative access to the affected server.
-* A working server with the correct TLS cryptography registry keys to export.
-* Knowledge of registry editing and system reboot procedures.
+> Local security authority cannot be contacted.
 
-## Symptoms
+After about 20 days, you can't connect to any virtual machines, regardless of the operating system (Windows or Linux), via VMConnect.
 
-Users encountering this issue may experience the following:
+## Missing TLS cryptography registry keys
 
-* Persistent authentication error message: "Local security authority cannot be contacted."
-* Inability to connect to any virtual machines, regardless of the operating system (Windows or Linux), via VM Connect.
-* The issue began approximately 20 days before the case was logged.
+The issue is caused by missing TLS cryptography registry keys required for the TLS/Secure Sockets Layer (SSL) handshake. These keys are crucial for secure communication during the authentication process. Their absence leads to a failure in the secure channel initialization process, which prevents authentication attempts from succeeding.
 
-## Cause
+## Restore missing TLS cryptography registry keys
 
-The problem is caused by missing TLS cryptography registry keys required for the SSL/TLS handshake. These keys are crucial for secure communication during the authentication process. Their absence leads to a failure in the SchannelInit process, which prevents authentication attempts from succeeding.
-
-## Solution: Restore missing TLS cryptography registry keys
+[!INCLUDE [Registry alert](../../includes/registry-important-alert.md)]
 
 To resolve the issue, follow these steps:
 
-1. **Export TLS cryptography registry keys from a working server:**
-
-   * On a functioning server, open the Windows Registry Editor (regedit).
-   * Navigate to the following registry path:
-
-     HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols
-
-   * Right-click the Protocols key and select **Export**.
-   * Save the exported .reg file to a secure location.
-
-2. **Import the registry keys to the affected server:**
-
-   * Transfer the exported .reg file to the affected server.
-   * Open the Windows Registry Editor on the affected server.
-   * Double-click the .reg file to import the keys. Follow the prompts to confirm the import.
+1. Export TLS cryptography registry keys from a working server:
 
-3. **Reboot the server:**
+   1. Open Windows Registry Editor (**regedit.exe**) on a working server, and go to the following registry path:
 
-   * Restart the affected server to apply the changes.
+      `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols`
 
-4. **Test the connection:**
+   2. Right-click the `Protocols` key and select **Export**.
+   3. Save the exported `.reg` file to a secure location.
 
-   * Attempt to connect to the Hyper-V virtual machines using VM Connect to ensure the issue is resolved.
+2. Import the registry keys to the affected server:
 
-     By completing these steps, the missing TLS cryptography registry keys are restored, enabling the necessary SSL/TLS handshake and resolving the authentication error.
+   1. Transfer the exported `.reg` file to the affected server.
+   2. Open the Registry Editor on the affected server, and double-click the `.reg` file to import the keys. Follow the prompts to confirm the import.
 
-     ## Determine the cause of the problem
+3. Restart the affected server to apply the changes.
+4. Connect to the Hyper-V virtual machines using VMConnect to ensure the issue is resolved.
 
-     If the issue persists after performing the solution steps, further investigation may be required to confirm if additional configuration settings or system updates are impacting the VM connection process.
+After you complete these steps, the missing TLS cryptography registry keys are restored, enabling the necessary TLS/SSL handshake and resolving the authentication error.
 
-     ## Cause 2: Other potential issues
+## Other potential causes
 
-     If the TLS cryptography keys are present and correctly configured, other potential causes, such as network configuration issues or outdated system components, should be examined.
+If the issue persists, further investigation might be required to confirm whether additional configuration settings or system updates are impacting the VM connection process. For example, network configuration issues or outdated system components should be examined.
 
-### Solution 2: Verify network and system configurations
+You can verify the network and system configurations by using the following steps:
 
 1. Check the server's network connectivity to ensure there are no interruptions.
 2. Ensure all system updates and patches are applied to both the host and guest operating systems.
-3. Review event logs for additional error messages that may provide insights into the issue.
+3. Review event logs for additional error messages that might provide insights into the issue.
 
-     If further assistance is required, consider contacting Microsoft Support for advanced troubleshooting.
+If further assistance is required, consider contacting Microsoft Support for advanced troubleshooting.