Bug "Failed to bind the game because of an AgentinitializationException"

I had this issue, Its indeed onedrive. Problem is I had to reinstall my OS and not sign into my outlook account and I ran a script bot to remove onedrive all together. Microsoft has done something with one drive where it redirects the home folders that runemate is looking for.

Thescript I used was v1.2 here TERRAOperative/OneDrive-Uninstaller

 

Same problem

--- Double Post Merged, May 16, 2018, Original Post Date: May 16, 2018 ---

Follow up to my last post, here are two of my logs:

Log 1:
[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.1
[Debug] Operating System: Windows 10 x64
Checking for a new game client every second for two minutes or until one is found.
Found a new game instance after 3 seconds.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:68)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
[Clouse] Downloaded 988 human mouse movements selected for you by Clouse.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:68)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)



Bigass log 2:
[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.1
[Debug] Operating System: Windows 10 x64
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more
[Clouse] Downloaded 1000 human mouse movements selected for you by Clouse.
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more




On another occasion, I ran both clients as admin. When I attempted to start an instance, it acted like it was going to load for a second and then it just goes right back to the "Start instance" screen like nothing happened at all. Which was kind of weird because it was doing the opposite earlier when I DID NOT run as admin BEFORE I uninstalled then reinstalled Java/Runemate. Needless to say, there were no errors or log files that popped up for those times.

 

XD

 

Glad someone in here is happy! >(

 

Still not fixed.

 

Same, still not fixed

 

Did you guys try using the solutions that have been posted numerous times?

 

If we didn't, I wouldn't have posted. I tried literally everything besides wiping my entire computer.
Edit: Posted it somewhere else but the issue is basically the same.
Edit - 2: Actually fixed it by following the details Bug - instrument library is missing in target VM probably not a bad idea to add that information somewhere easily accesible.

 

have you tried using the standalone instead of installing ?

 

That didn't work but I fixed it by the link I posted above. Had to do with the fact that my user folders where on my second SSD instead of the first because the first is fairly small. It's a windows 10 feature, and it breaks the bot if you don't add a symlink.

 

No worries, I HAVE tried reformatting the PC and it still didn't solve the issue

--- Double Post Merged, May 30, 2018, Original Post Date: May 28, 2018 ---

Same

 

Yeah this seems to be a common issue for people with the agent initialisation exception. I'm not quite sure how the RMI protocol works that runemate uses but I can imagine that it doesn't like bridging cross-storagedevice when binding to a client that is installed on a different location than the runemate client.

 

Welp, uninstall time. We have waited more than long enough for help or fixes.

 

Yeahc Issue is still occurring for me... Any fixes? The stuff above does not work.

 

How can this issue not be resolved yet? Support seems to be lacking severely.