Mirrors/WSABuilds
2
0
Fork 0
mirror of https://github.com/MustardChef/WSABuilds.git synced 2024-11-25 20:56:53 +01:00
Code Issues Packages Projects Releases Wiki Activity
master
WSABuilds/Documentation/Fix Guides/Post-Install Issues/TargetMachineActivelyRefusedConnection.md
MCDeltaT af9fdf32f6 Update Pages.
2023-12-15 15:03:18 +00:00

2.1 KiB
Raw Permalink Blame History

WSABuilds      

Issue:
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 or WSAPacman, or when you try to connect to a device using adb.exe via Android SDK 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.

image

cannot connect to ||127.0.0.1:58526:|| No connection could be made because the target machine actively refused it. (10061)

Solution

This is a bug with the subsystem itself, restarting the PC will usually fix it. But, if you still get this error, try these steps:


  • 1. Make sure WSA is turned off and disable WSA autostart in Task Manager ---> Startup Apps before proceeding

  • 2. Disable Hyper-V (if it is enabled) using the command
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

  • 3. Reboot your PC

  • 4. Reserve port 58526 so Hyper-V doesn't reserve it back using the command
netsh int ipv4 add excludedportrange protocol=tcp startport=58526 numberofports=1

  • 5. Re-enable Hyper-V (if it was previously enabled) using the command dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All and reboot your PC



Hope this works for you!


Have futher question or need help?

Join the Discord if you have any other questions or need help!