Error Join To Join 138 (0x8A): Use These 3 Solutions to Fix

ERROR_JOIN_TO_JOIN often comes with the following error code 138 (0x8A) and the following description: The system tried to join a drive to a directory on a joined drive. In this guide, we’re going to show you how to fix it.

How can I fix ERROR_JOIN_TO_JOIN?

1. Ensure that your VPN is using the correct settings

1. Right-click the Sophos VPN client in your system tray.
2. Choose Settings and select Use config file settings.
3. Save changes.

2. Change Eclipse settings

1. Open Debug Configurations in Eclipse.
2. Next, Expand GDB SEGGER J-Link Debugging and choose remote_Debug_Segger.
3. Check Start the J-Link GDB server locally.
   
4. Save changes.

Read more about this topic

• Error Not Joined: How to Fix it Permanently
• Python27.dll is Missing or Not Found: How to Get it Back

3. Other solutions to try

1. Open NAT for TCP 8443 to your Sophos.
2. Check your router before Sophos and make sure the Sophos port isn’t blocked. Your firewall can also block specific kind of traffic thus causing the problem, so check that as well.
3. Manually specific the path to bundled multiarch GDB. It should reside in X:\path\to\CLion\bin\gdb\bin\gdb.exe

Error ERROR_JOIN_TO_JOIN is somewhat rare, and it usually affects developers, but if you encounter it, be sure to try the solutions from this guide.

This isn’t the only error you can encounter, we wrote about ERROR_NOT_JOINED and ERROR_CALL_NOT_IMPLEMENTED in our older guides, so don’t miss them.