Bug Runemate wont start bot

Hello I am new here, I have read the tut video, I click start interface, it says failed to bind to virtual machine

I am using Windows 8 64bit.
i have installed java 32bit even though I am on 64bit
I have uninstalled runemate & all javas on my system. I have restarted my pc and reinstalled Runemate still having the same problem.
I have downloaded the legacy runescape client as asked todo by video tut.
I have turned of my windows firewall with no success.

I dont really need a refund at all it doesnt cost that much. I would like it if I could get it working.

If needs be I will be up for the admin to have access on my pc and ill let him try to get it to work.

 

[Debug] RuneMate Version: 2.1.8
[Debug] Java Version: 8u92 x86 (Oracle Corporation)
[Debug] Operating System: Windows 8.1 x64
May 28, 2016 1:07:38 AM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Found a new game instance after 7 seconds.
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Found a new game instance after 11 seconds.
Found a new game instance after 8 seconds.
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Found a new game instance after 4 seconds.
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Found a new game instance after 9 seconds.
Attempting to start official client. If it does not open shortly please do so manually.
Checking for a new game instance every second for two minutes or until one is found.
Found a new game instance after 3 seconds.
Failed to bind to virtual machine because of a AgentInitializationException
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(te:216)
at nul.iiIiIIiiiIii.try(jec:41)
at nul.iIiiIIiIIIiI.run(vgc:9)

--- Double Post Merged, May 28, 2016, Original Post Date: May 27, 2016 ---

I have now upgraded to windows 10 to see if that will work and it doesnt make any difference.

 

Update it works for me. I installed windows 10 instead of the laptops manufactures software that splits the c drive and d drive seperatly that causes the issue.

Sky leave do what I have done. It will work I fact I'll pm u the link to the one you should download