From 55e3e7836dc4f0409cbc92b490f68faba225a78e Mon Sep 17 00:00:00 2001
From: MCDeltaT <68516357+MustardChef@users.noreply.github.com>
Date: Sun, 9 Apr 2023 21:04:21 +0100
Subject: [PATCH] Update TargetMachineActivelyRefusedConnection.md

---
 Fixes/TargetMachineActivelyRefusedConnection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Fixes/TargetMachineActivelyRefusedConnection.md b/Fixes/TargetMachineActivelyRefusedConnection.md
index 63a608d..2925b8b 100644
--- a/Fixes/TargetMachineActivelyRefusedConnection.md
+++ b/Fixes/TargetMachineActivelyRefusedConnection.md
@@ -1,7 +1,7 @@
 # WSABuilds &nbsp; &nbsp; <img src="https://img.shields.io/github/downloads/MustardChef/WSABuilds/total?label=Total%20Downloads&style=for-the-badge"/> &nbsp; 
 
 ---
-## Issue: </br> Error: No connection could be made because the target machine actively refused it
+## Issue: </br> Error: No connection could be made because the target machine actively refused it (10061)
 ### Preface:
 ##### This issue occurs when you are either using a sideloading application such as [WSA-Sideloader](https://github.com/infinitepower18/WSA-Sideloader) or [WSAPacman](https://github.com/alesimula/wsa_pacman), or when you try to connect to a device using ``adb.exe`` via [Android SDK Platform Tools](https://developer.android.com/tools/releases/platform-tools). This issue arises due to an issue with the inability of Hyper V to reserve port 58526 causing the issue, as seen below.