WSABuilds/Fixes/Post-Install Issues/TargetMachineActivelyRefusedConnection.md
MCDeltaT e9c76a53df Changes to Fixes and Guides
- Move Fixes and Guides into separate folder
- Update guides and fix mistakes
- Adding Post-Installation Pages
2023-08-29 15:56:46 +01:00

2.0 KiB

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.

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 enabled) using the command dism.exe /Online /Disable-Feature:Microsoft-Hyper-V and reboot your PC

  3. 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

  4. 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

Your issue should be fixed now!



Hope this works for you!



Have futher question or need help?

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