Skip to content

Commit 43134f7

Browse files
authored
Update cannot-access-hyper-v-virtual-machine-connect.md
1 parent 8d9a485 commit 43134f7

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Can't Access Hyper-V Virtual Machines Via VMConnect
3-
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.
4-
ms.date: 08/13/2025
3+
description: Addresses an issue where you can't connect to Hyper-V virtual machines (VMs) through VMConnect after you repeatedly receive an authentication error.
4+
ms.date: 08/18/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -54,12 +54,12 @@ After you complete these steps, the missing TLS cryptography registry keys are r
5454

5555
## Other potential causes
5656

57-
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.
57+
If the issue persists, further investigation might be required to confirm whether other configuration settings or system updates are impacting the VM connection process. For example, network configuration issues or outdated system components should be examined.
5858

5959
You can verify the network and system configurations by using the following steps:
6060

6161
1. Check the server's network connectivity to ensure there are no interruptions.
6262
2. Ensure all system updates and patches are applied to both the host and guest operating systems.
63-
3. Review event logs for additional error messages that might provide insights into the issue.
63+
3. Review event logs for other error messages that might provide insights into the issue.
6464

6565
If further assistance is required, consider contacting Microsoft Support for advanced troubleshooting.

0 commit comments

Comments
 (0)