leapdroid-team / leapdroid

Leapdroid Android emulator
Apache License 2.0
58 stars 29 forks source link

"Unknown internal error" when starting LeapDroid #39

Open pidgeon777 opened 8 years ago

pidgeon777 commented 8 years ago

I've been using LeapDroid without any problem during the past days. Now, everytime I try to start VM1 or VM2, I receive the following error, and LeapDroid closes itself:

image

My OS is Windows 7 Professional x64 SP1.

pidgeon777 commented 8 years ago

I think the problem was due the fact that when starting the VM, there was already more than one "LeapdroidVM.exe" process active (I counted five of them). I terminated the processes through Task Manager, and finally I've been able to run LeapDroid.

So, the problem could be that when closing the main window through the "x" button, the process still occupied RAM.

LeapdroidDev99 commented 8 years ago

Thanks for your detailed description, which helped us a lot. You know, it is not an easy job to hunt for the reason based on something like "this does not work". Let me confirm: after killing all the LeapdroidVM processes, you are able to launch. Do you still remember what you did in your last launching and then close? Such as: the leapdroidvm took a long time to disappear? You were running something at the same time while closing leapdroidvm?

pidgeon777 commented 8 years ago

If I recall correctly, on that day I opened and closed LeapDroid about 4 or 5 times, but it closed itself quickly every time. Moreover, I think explorer.exe crashed (it sometimes happens on my case), and I was even using VMWare Player and Oracle VM Virtualbox with two virtual machines. I confirm that after killing each process, I was finally able to start LeapDroid again. In summary, the situation was this: 5 x LeapDroidVM.exe 1 x LeapDroidVMSVC.exe

I terminated the five LeapDroidVM.exe processes, leaving only LeapDroidVMSVC.exe active (thinking it was a service), then I started LeapDroid again through the desktop shortcut, and it ran.

LeapdroidDev99 commented 8 years ago

Thanks for the details. OK, we will need to test our product in a more complex os env. BTW: it is definitely OK to kill the service. That is started on demand. In this case, we also kill them "LeapdroidVM*" all.

pidgeon777 commented 8 years ago

Thank you for the support. If the problem will occur again, I will let you know as soon as possible. I want to congratulate you, anyway, because I think LeapDroid is the fastest (and I could add even stablest) Android emulator I've ever tried.

LeapdroidDev99 commented 8 years ago

Thanks, I will let our team know your kind feedback. :)

Zeroxcore commented 8 years ago

I love it man. & thanks for your hard work, I am also getting this error can you help me. Again Thanks for the best emulator.

pidgeon777 commented 8 years ago

Uhm, unfortunately it seems that the error is appearing again. No LeapDroid processes already active in RAM this time, but still not being able to run it (same error message). I noticed that after having clicked on the "OK" button, a LeapDroid process is left active in RAM:

image

Zeroxcore commented 8 years ago

I have to uninstall & re-install it every time when i use this, so kindly fix this issue. I upload every essential log file, kindly look into this matter screenshot 319 screenshot 320 screenshot 321 Log Files.zip

LeapdroidDev99 commented 8 years ago

Hi, Guys, First of all, thanks for trusting us and the invaluable log files. Can I ask a few more questions?

  1. Let me double check, the issue happened actually after you are able to use Leapdroid on your box for some time. And in the middle, you actually did nothing (like installing/uninstalling Leapdroid) with leapdroid.
  2. Did you happen to install/uninstall any other VBox related product in the middle, such as other emulators or vbox itself?

@Zeroxcore From the log, in your case, the kernel driver did not start at all. You can actually check the driver status by running Windows command console and using "sc query LeapdroidVMDrv". It should be in a running state. @pidgeon777 Could you please share the log with us? I hope the reason is the same as Zeroxcore.

We do have a command utility to install (again) the driver for you. You can open a Windows command console and this time the console needs to be launched using administrator. Go to our program folder and use command "DoCustomActions.exe InstallRPrepare".

Please let us know whether this works for you. But god, even this works, we still need to figure out why the driver suddenly got disabled or deleted.

Zeroxcore commented 8 years ago

I just install your LeapdroidVMSetup64.msi 342mb setup & its work perfectly. Thanks for your reply i will reply you if next time I will getting this issue, by the way service i think driver is running. Thanks

C:\Windows\system32>sc query LeapdroidVMDrv

SERVICE_NAME: LeapdroidVMDrv TYPE : 1 KERNEL_DRIVER STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0

Onihikage commented 8 years ago

I want to chime in with a contribution of my own. I got this error today on Windows 8.1, some time after rebooting for an unrelated issue and attempting to start Leapdroid. I attempted the above commands and suggestions made by LeapdroidDev99, with no change in the error message and the same result as Zeroxcore. However, I believe I may have found where the problem lies, at least in some cases.

First, I was running version 1.7 of Leapdroid, installed via exe. It was working perfectly earlier today, but after rebooting, the Unknown internal error message appeared. I uninstalled it and replaced it with 1.8, also through the exe installer. Leapdroid started just fine. I closed Leapdroid and made sure all Leapdroid processes had ended, then copied the data.vmdk which I'd backed up from the previous installation, just as I had done back when I went from 1.6 to 1.7. After that, Leapdroid threw the error message again and wouldn't start.

In my case, it seems like something got corrupted within the data.vmdk, and this corruption prevented Leapdroid from starting. (Related note: the reason I rebooted was to resolve an issue with my mouse cursor appearing corrupted on one monitor but not the other, an AMD driver issue that crops up very rarely) Slight side note, the current data.vmdk, after installing/uninstalling everything the old one had, is about 500MB smaller, 2.209GB vs 2.790GB. Version 1.8 is working fine for now, but I'll keep you posted if the problem recurs.

pidgeon777 commented 8 years ago

Hi LeapdroidDev99,

  1. Let me double check, the issue happened actually after you are able to use Leapdroid on your box for some time.

Exactly.

And in the middle, you actually did nothing (like installing/uninstalling Leapdroid) with leapdroid.

Yes.

  1. Did you happen to install/uninstall any other VBox related product in the middle, such as other emulators or vbox itself?

I removed one of my virtual machines from VirtualBox.

LeapdroidVMInstallerFull.log:

[logger] module: C:\Users\Pidgeon\Downloads\LeapdroidVMInstallerFull.exe, pid: 9288, version: 1.6.1.0 2016-09-13 23:30:09, 9288, 8328, LeapdroidVMInstallerFull, **** 2016-09-13 23:30:09, 9288, 8328, LeapdroidVMInstallerFull, loader start... 2016-09-13 23:30:09, 9288, 8328, LeapdroidVMInstallerFull, **** 2016-09-13 23:30:09, 9288, 8328, LeapdroidVMInstallerFull, cmdline: "C:\Users\Pidgeon\Downloads\LeapdroidVMInstallerFull.exe" [logger] module: C:\Users\Pidgeon\Downloads\LeapdroidVMInstallerFull.exe, pid: 13012, version: 1.6.1.0 2016-09-13 23:30:13, 13012, 14304, LeapdroidVMInstallerFull, **** 2016-09-13 23:30:13, 13012, 14304, LeapdroidVMInstallerFull, loader start... 2016-09-13 23:30:13, 13012, 14304, LeapdroidVMInstallerFull, **** 2016-09-13 23:30:13, 13012, 14304, LeapdroidVMInstallerFull, cmdline: "C:\Users\Pidgeon\Downloads\LeapdroidVMInstallerFull.exe" /restart 2016-09-13 23:30:14, 13012, 14304, LeapdroidVMInstallerFull, Leapdroid Installer Full start... 2016-09-13 23:30:14, 13012, 14304, LeapdroidVMInstallerFull, query_no_safe: 200 2016-09-13 23:30:15, 13012, 14304, LeapdroidVMInstallerFull, query_no_safe: 200 2016-09-13 23:30:15, 13012, 14304, LeapdroidVMInstallerFull, query exception 2016-09-13 23:30:16, 13012, 11356, LeapdroidVMInstallerFull, start ... 2016-09-13 23:31:10, 13012, 13672, LeapdroidVMInstallerFull, start install... 2016-09-13 23:31:10, 13012, 13672, LeapdroidVMInstallerFull, do install... 2016-09-13 23:31:11, 13012, 13672, LeapdroidVMInstallerFull, start checking... 2016-09-13 23:31:11, 13012, 13672, LeapdroidVMInstallerFull, Checking free space available: [3434201088 Bytes]/[3434201088 Bytes] 2016-09-13 23:31:11, 13012, 13672, LeapdroidVMInstallerFull, Precheck ok! 2016-09-13 23:31:11, 13012, 13672, LeapdroidVMInstallerFull, start download... 2016-09-13 23:31:12, 13012, 13672, LeapdroidVMInstallerFull, devinfo: http://stats.leapdroid.com/stats/sysinfo.php?id=10BF481DF9DC&mac=10BF481DF9DC&product_id=2002&version=1.6.1.0&osinfo=os:(Microsoft Windows 7 Professional , Service Pack 1, 7601, 64 bit), cpu:(Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz), gpu:(NVIDIA GeForce GT 650M , 20150408000000.000000-000, 9.18.13.5012, -2147483648), bios:(BIOS Date: 05/11/12 16:43:21 Ver: 04.06.05, American Megatrends Inc., ASUS - 1072009)&vtenabled=1 2016-09-13 23:31:12, 13012, 13672, LeapdroidVMInstallerFull, stop service and app... 2016-09-13 23:31:12, 13012, 13672, LeapdroidVMInstallerFull, run setup... 2016-09-13 23:31:45, 13012, 13672, LeapdroidVMInstallerFull, Optimizing VMDK Images... 2016-09-13 23:32:15, 13012, 13672, LeapdroidVMInstallerFull, vbox rom install ok 2016-09-13 23:32:15, 13012, 13672, LeapdroidVMInstallerFull, °²×°Ö÷³ÌÐòºÍ¿ì½Ý·½Ê½... 2016-09-13 23:32:15, 13012, 13672, LeapdroidVMInstallerFull, create_shortcut ... 2016-09-13 23:32:20, 13012, 13672, LeapdroidVMInstallerFull, Create Uninstall Items 2016-09-13 23:32:20, 13012, 13672, LeapdroidVMInstallerFull, create all ok.

VBoxSVC.log

VirtualBox COM Server 5.0.8_OSE r103449 win.amd64 (Aug 4 2016 19:39:49) release log 00:00:00.008001 main Log opened 2016-09-27T11:53:27.762445800Z 00:00:00.008001 main Build Type: release 00:00:00.008001 main OS Product: Windows 7 00:00:00.008001 main OS Release: 6.1.7601 00:00:00.008001 main OS Service Pack: 1 00:00:00.031003 main DMI Product Name: N56VZ 00:00:00.038004 main DMI Product Version: 1.0
00:00:00.038004 main Host RAM: 8077MB total, 1278MB available 00:00:00.038004 main Executable: C:\Program Files\Leapdroid\VM\LeapdroidVMSVC.exe 00:00:00.038004 main Process ID: 12088 00:00:00.038004 main Package type: WINDOWS_64BITS_GENERIC (OSE) 00:00:00.040005 Home directory: 'C:\Users\Pidgeon\Documents\Leapdroid' 00:00:00.040005 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VirtualBox.xml" with version "1.12-windows" 00:00:00.041005 USBLibInit: USB Service not found 00:00:00.046505 Skipped non-Ethernet 'Loopback Pseudo-Interface 1' 00:00:00.046505 Skipped non-Ethernet 'isatap.{DE343537-DCFC-4C60-9FEA-AD8DD34BCCC8}' 00:00:00.046505 Skipped non-Ethernet 'isatap.{7D721AA4-2269-48B4-916D-CF03E383E90C}' 00:00:00.046505 Skipped non-Ethernet 'isatap.{6F7BEC30-7455-4BCF-A9BA-1BF01FE7D6E7}' 00:00:00.046505 Skipped non-Ethernet 'Teredo Tunneling Pseudo-Interface' 00:00:00.046505 Skipped non-Ethernet 'isatap.{9830AE4E-C2A4-4ED1-8B20-AD26831AEF7A}' 00:00:00.046505 Skipped non-Ethernet 'isatap.{008B40B0-5C02-4880-BC8A-765CC56599E0}' 00:00:00.046505 Skipped non-Ethernet 'isatap.{00F38D98-4B9A-43AE-9D16-127C60320A79}' 00:00:00.053006 HostDnsMonitor: old information 00:00:00.053006 no server entries 00:00:00.053506 no search string entries 00:00:00.053506 no domain set 00:00:00.053506 HostDnsMonitor: new information 00:00:00.053506 server 1: 192.168.0.1 00:00:00.053506 no search string entries 00:00:00.053506 no domain set 00:00:00.053506 HostDnsMonitorProxy::notify 00:00:00.053506 VD: VDInit finished 00:00:00.054506 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={37797299-3c74-4fad-9b04-afff8c65bc5a} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0 00:00:00.055507 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\vm1.vbox" with version "1.15-windows" 00:00:00.056507 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\vm2.vbox" with version "1.15-windows" 00:00:00.878611 WARNING [COM]: aRC=E_FAIL (0x80004005) aIID={40b9684d-894b-4f96-bf6a-52f56f4a0eec} aComponent={HostWrap} aText={Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer}, preserve=true aResultDetail=0 00:00:01.376674 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7afeec2d-0ae6-4f52-86de-0eedb4e4a662} aComponent={SessionMachine} aText={The object is not ready}, preserve=false aResultDetail=0

The service appears to be running:

C:\Users\Pidgeon>sc query LeapdroidVMDrv

NOME_SERVIZIO: LeapdroidVMDrv TIPO : 1 KERNEL_DRIVER STATO : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) CODICE_USCITA_WIN32 : 0 (0x0) CODICE_USCITA_SERVIZIO : 0 (0x0) PUNTO_CONTROLLO : 0x0 INDICAZIONE_ATTESA : 0x0

Anyway, I tried the command you suggested me:

DoCustomActions.exe InstallRPrepare

Result:

image

But if I run CMD as administrator, no error:

C:\Program Files\Leapdroid\VM>DoCustomActions.exe InstallRPrepare Service stopped successfully Successfully started service: LeapdroidVMDrv

it didn't solve my problem, though. It appears to be related to VB Guest Additions, by judging from the log file.

LeapdroidDev99 commented 8 years ago

Thanks for all the feedback. Actually, in a summary, more than 1 reason would result in this "Unknown Internal Error", which we have been suffering for a long time.

  1. VM Data Files are installed to a folder where the file permission of user is not the usual case. For example, C:\ProgramData C:\Users\OneDrive\Documents . This could be avoided by choosing a different folder.
  2. VMDK are copied back to overwrite existing one. Actually, in this case, typically the file is not corrupted. The issue roots in Virtualbox's VMDK management. Each VMDK is given an unique UUID. Simple copying and overwriting the existing one makes Virtualbox confused. In this case, you should open Virtualbox, choose "File->Virtual Media Manager"; Release and remove the ones with "question mark"; Open vm settings panel; Go to Storage settings and bind the VMDK to this storage installer again. In this case, Virtualbox will know "OK, user actually changed VMDK and do not bother with old settings".
  3. The driver issue as first identified in this thread. While we know how to install driver again, it is still unknown why driver suddenly gets disabled or deleted. I hope this description can help advanced users a bit.
Zeroxcore commented 8 years ago

kindly install this leapdroid setup & tell here if you are getting this issue again, my problem has been resolved when i install this version. Thanks

For x64 bit windows http://www.leapdroid.com/installer/current/LeapdroidVMSetup64.msi
For x32 bit windows http://www.leapdroid.com/installer/current/LeapdroidVMSetup32.msi

Zeroxcore commented 8 years ago

hey @LeapdroidDev99 how can i update leapdroid within software? is there any option in leapdroid for update?

i am getting another issue, every time my leapdroidshared folder is empty, & i have re-configure it again.

pidgeon777 commented 8 years ago

I solved my problem. I went to this folder:

C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1

and opened the vm1.vbox file. By doing so, the main window of VirtualBox appeared, and the new LeapDroid VM got added to the main panel:

image

Finally I closed VirtualBox, and when I tried to open LeapDroidVM, this time it succesfully started. Here is the new VBoxSVC.log file:

VirtualBox COM Server 5.0.8_OSE r103449 win.amd64 (Aug 4 2016 19:39:49) release log 00:00:00.006500 main Log opened 2016-09-27T19:39:15.169672300Z 00:00:00.006500 main Build Type: release 00:00:00.007000 main OS Product: Windows 7 00:00:00.007000 main OS Release: 6.1.7601 00:00:00.007000 main OS Service Pack: 1 00:00:00.071009 main DMI Product Name: N56VZ 00:00:00.078510 main DMI Product Version: 1.0
00:00:00.078510 main Host RAM: 8077MB total, 2822MB available 00:00:00.078510 main Executable: C:\Program Files\Leapdroid\VM\LeapdroidVMSVC.exe 00:00:00.078510 main Process ID: 11240 00:00:00.078510 main Package type: WINDOWS_64BITS_GENERIC (OSE) 00:00:00.080510 Home directory: 'C:\Users\Pidgeon\Documents\Leapdroid' 00:00:00.081010 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VirtualBox.xml" with version "1.12-windows" 00:00:00.082010 USBLibInit: USB Service not found 00:00:00.088511 Skipped non-Ethernet 'Loopback Pseudo-Interface 1' 00:00:00.088511 Skipped non-Ethernet 'isatap.{DE343537-DCFC-4C60-9FEA-AD8DD34BCCC8}' 00:00:00.088511 Skipped non-Ethernet 'isatap.{7D721AA4-2269-48B4-916D-CF03E383E90C}' 00:00:00.088511 Skipped non-Ethernet 'isatap.{6F7BEC30-7455-4BCF-A9BA-1BF01FE7D6E7}' 00:00:00.088511 Skipped non-Ethernet 'Teredo Tunneling Pseudo-Interface' 00:00:00.088511 Skipped non-Ethernet 'isatap.{9830AE4E-C2A4-4ED1-8B20-AD26831AEF7A}' 00:00:00.088511 Skipped non-Ethernet 'isatap.{008B40B0-5C02-4880-BC8A-765CC56599E0}' 00:00:00.088511 Skipped non-Ethernet 'isatap.{00F38D98-4B9A-43AE-9D16-127C60320A79}' 00:00:00.094011 HostDnsMonitor: old information 00:00:00.094011 no server entries 00:00:00.094011 no search string entries 00:00:00.094011 no domain set 00:00:00.094011 HostDnsMonitor: new information 00:00:00.094011 server 1: 192.168.0.1 00:00:00.094011 no search string entries 00:00:00.094011 no domain set 00:00:00.094011 HostDnsMonitorProxy::notify 00:00:00.094011 VD: VDInit finished 00:00:00.095012 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={37797299-3c74-4fad-9b04-afff8c65bc5a} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0 00:00:00.096012 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\vm1.vbox" with version "1.15-windows" 00:00:00.097012 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\vm2.vbox" with version "1.15-windows" 00:00:00.913616 WARNING [COM]: aRC=E_FAIL (0x80004005) aIID={40b9684d-894b-4f96-bf6a-52f56f4a0eec} aComponent={HostWrap} aText={Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer}, preserve=true aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\system.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\data.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\sdcard.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\system.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\data.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={8b35f055-7bee-4607-919c-80f108bf927c} aComponent={MediumWrap} aText={Medium 'C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\sdcard.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:00:18.047700 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={b988cc4e-052f-41b7-8ef5-64c837bf2ee1} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0

pidgeon777 commented 8 years ago

Now I did another thing: I manually removed LeapDroid VM from VirtualBox, keeping the VM files on my HDD, and it still run. Here is the new VBoxSVC.log file:

VirtualBox COM Server 5.0.8_OSE r103449 win.amd64 (Aug 4 2016 19:39:49) release log 00:00:00.006000 main Log opened 2016-09-27T19:41:19.604810300Z 00:00:00.006000 main Build Type: release 00:00:00.006000 main OS Product: Windows 7 00:00:00.006000 main OS Release: 6.1.7601 00:00:00.006000 main OS Service Pack: 1 00:00:00.019502 main DMI Product Name: N56VZ 00:00:00.027003 main DMI Product Version: 1.0
00:00:00.027003 main Host RAM: 8077MB total, 2811MB available 00:00:00.027003 main Executable: C:\Program Files\Leapdroid\VM\LeapdroidVMSVC.exe 00:00:00.027003 main Process ID: 3340 00:00:00.027003 main Package type: WINDOWS_64BITS_GENERIC (OSE) 00:00:00.029003 Home directory: 'C:\Users\Pidgeon\Documents\Leapdroid' 00:00:00.029003 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VirtualBox.xml" with version "1.12-windows" 00:00:00.030003 USBLibInit: USB Service not found 00:00:00.035504 Skipped non-Ethernet 'Loopback Pseudo-Interface 1' 00:00:00.035504 Skipped non-Ethernet 'isatap.{DE343537-DCFC-4C60-9FEA-AD8DD34BCCC8}' 00:00:00.035504 Skipped non-Ethernet 'isatap.{7D721AA4-2269-48B4-916D-CF03E383E90C}' 00:00:00.035504 Skipped non-Ethernet 'isatap.{6F7BEC30-7455-4BCF-A9BA-1BF01FE7D6E7}' 00:00:00.035504 Skipped non-Ethernet 'Teredo Tunneling Pseudo-Interface' 00:00:00.035504 Skipped non-Ethernet 'isatap.{9830AE4E-C2A4-4ED1-8B20-AD26831AEF7A}' 00:00:00.035504 Skipped non-Ethernet 'isatap.{008B40B0-5C02-4880-BC8A-765CC56599E0}' 00:00:00.035504 Skipped non-Ethernet 'isatap.{00F38D98-4B9A-43AE-9D16-127C60320A79}' 00:00:00.041505 HostDnsMonitor: old information 00:00:00.041505 no server entries 00:00:00.041505 no search string entries 00:00:00.041505 no domain set 00:00:00.041505 HostDnsMonitor: new information 00:00:00.041505 server 1: 192.168.0.1 00:00:00.041505 no search string entries 00:00:00.041505 no domain set 00:00:00.041505 HostDnsMonitorProxy::notify 00:00:00.042005 VD: VDInit finished 00:00:00.042505 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={37797299-3c74-4fad-9b04-afff8c65bc5a} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0 00:00:00.043505 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm1\vm1.vbox" with version "1.15-windows" 00:00:00.044505 Loading settings file "C:\Users\Pidgeon\Documents\Leapdroid\VMs\vm2\vm2.vbox" with version "1.15-windows" 00:00:01.136144 WARNING [COM]: aRC=E_FAIL (0x80004005) aIID={40b9684d-894b-4f96-bf6a-52f56f4a0eec} aComponent={HostWrap} aText={Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer}, preserve=true aResultDetail=0

pidgeon777 commented 8 years ago

Update: I rebooted my PC, started LeapDroid, same error. Then I did again the thing I described here:

https://github.com/leapdroid-team/leapdroid/issues/39#issuecomment-249975045

and it worked.

pidgeon777 commented 8 years ago

This appears to happen every time I reboot my PC. Any news about this issue? Anyway, in a few weeks I'll have to format my HDD, so I'll see what happen after re-installing LeapDroid again.

TheTechGenius-Net commented 8 years ago

I was getting this error today, I have even stopped all the LeapDroid services that were running, and I was still getting the "Unknown Internal Error". However, I used the commands above via CMD running in Admin Mode, and everything seems to be running perfect again. I don't know what happened.

The command I used was "DoCustomActions.exe InstallRPrepare".

EthernalFire commented 8 years ago

I've just experienced this error few minutes ago and I've used the same solution as with the Explorer++'s crash issue. I've run the app as administrator. It fixed the issue for me.

Milad-jfr commented 6 years ago

Recently i have this error on my new PC . In my case ( Windows 10 Enterprise 64bit ) problem is with "unsigned driver signature" . I made my installation in "disable driver signature enforcement windows" mode , and if i load windows in this mode leapdroid work properly without "Unknow internal Error" , but if i restart the system in normal mode , the error eppar .

hope this will help

Cserleo commented 6 years ago

Click the Start menu and select Settings. Click Update and Security. Click on Recovery. Click Restart now under Advanced Startup. Click Troubleshoot. Click Advanced options. Click Startup Settings. Click on Restart. On the Startup Settings screen press 7 or F7 to disable driver signature enforcement. Your computer will restart and you will be able to install non-digitally signed drivers. If you restart your computer again the driver signature enforcement will be re-enabled, but you'll be able to run Leap Droid!

pidgeon777 commented 6 years ago

Thanks for the reply, unfortunately I'm not able to test your answer give that Leap Droid has been discontinued.

I'm currently using this Android emulator which seems to perform even better than LeapDroid:

http://en.ldmnq.com/

Cserleo commented 6 years ago

THE DISRESPECT HAHA, I'll try it though thanks for the recommendation.

wolfzi commented 5 years ago

Hello I have problem with leapdroid. I just download and opened it but I saw: http://prikachi.com/images.php?images/7/9470007a.png Please tell me how to solve it

GlacyAnime commented 4 years ago

I have just installed leapdroid it it is showing uknown internal error. After reading comments here i closed all processings related to leapdroid even that didn't solved my problem. What should i do.

pidgeon777 commented 4 years ago

@GlacyAnime Leap Droid has been discontinued. Use BlueStacks instead:

https://www.bluestacks.com/

Saya47 commented 8 months ago

I'm getting the same error. I don't want to use any other Android emulator. I'm on Windows 11.