Page 1 of 1
Apparently common error starting the Win10 VM
Posted: 17. Dec 2014, 01:33
by GaryBouchard
Failed to open a session for the virtual machine Windows 10 TP.
The virtual machine 'Windows 10 TP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Windows 10 Preview\Windows 10 TP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Attached is the log, but it was also previously giving me an error about Wintab32.dll missing... I dont know what app this is from but i managed to download a clean copy of it so that error is no longer showing in the VBoxStartup log. What is this file that it requires and where do I get it from? Why isn't it included in the installation?
Can someone please tell me what the problem is and what I should be looking for?
I apologize if this post is in the wrong place.
Re: Apparently common error starting the Win10 VM
Posted: 17. Dec 2014, 02:20
by Perryg
Search for wintab32.dll shows what probably needed it ( hint: wacom )
Code: Select all
29c4.2ae4: Error (rc=0):
29c4.2ae4: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume1\Windows\System32\Wintab32.DLL
29c4.2ae4: Error (rc=0):
29c4.2ae4: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\wintab32.dll' (C:\Windows\system32\wintab32.dll): rcNt=0xc0000190
Now your issue is probably due to wintab32.dll not being signed
Re: Apparently common error starting the Win10 VM
Posted: 18. Dec 2014, 00:58
by GaryBouchard
Yes, I am not even sure if this version of wintab32 I have is even compatible with this! Am I missing some other program that needs to be installed as a prerequisite?
Re: Apparently common error starting the Win10 VM
Posted: 19. Dec 2014, 18:57
by GaryBouchard
Perryg wrote:Search for wintab32.dll shows what probably needed it ( hint: wacom )
Code: Select all
29c4.2ae4: Error (rc=0):
29c4.2ae4: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume1\Windows\System32\Wintab32.DLL
29c4.2ae4: Error (rc=0):
29c4.2ae4: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\wintab32.dll' (C:\Windows\system32\wintab32.dll): rcNt=0xc0000190
Now your issue is probably due to wintab32.dll not being signed
Ok, I finally saw your hint
I installed the wacom but it is still errored out;
Failed to open a session for the virtual machine Windows 10 TP.
The virtual machine 'Windows 10 TP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Windows 10 Preview\Windows 10 TP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Attached is the new log file.
Re: Apparently common error starting the Win10 VM
Posted: 30. Dec 2014, 00:28
by GaryBouchard
Hi, Just wondering if anyone had an idea what the problem is? I sure would like to give the VM a try :
Re: Apparently common error starting the Win10 VM
Posted: 30. Dec 2014, 00:43
by Perryg
GaryBouchard wrote:Hi, Just wondering if anyone had an idea what the problem is? I sure would like to give the VM a try :
Looking at your last startup.log shows something that can be very bad.
Code: Select all
supR3HardenedMonitor_LdrLoadDll: error opening 'c:\program files\settings manager\smdmf\x64\sysapcrt.dll': 3 (NtPath=\??\c:\program files\settings manager\smdmf\x64\sysapcrt.dll; Input=c:\program files\settings manager\smdmf\x64\sysapcrt.dll)
This can indicate a virus or some other malware being installed on the host. Search for sysapcrt.dll and see for yourself. I would conside running a deep test with a good virus scanner.
Re: Apparently common error starting the Win10 VM
Posted: 30. Dec 2014, 01:15
by GaryBouchard
Perryg wrote:GaryBouchard wrote:Hi, Just wondering if anyone had an idea what the problem is? I sure would like to give the VM a try :
Looking at your last startup.log shows something that can be very bad.
Code: Select all
supR3HardenedMonitor_LdrLoadDll: error opening 'c:\program files\settings manager\smdmf\x64\sysapcrt.dll': 3 (NtPath=\??\c:\program files\settings manager\smdmf\x64\sysapcrt.dll; Input=c:\program files\settings manager\smdmf\x64\sysapcrt.dll)
This can indicate a virus or some other malware being installed on the host. Search for sysapcrt.dll and see for yourself. I would conside running a deep test with a good virus scanner.
Thanks for the heads up... I cleaned that as it was a drive by install from going to WorldTruth.TV facebook page and looking at one of their articles!
I still dont understand why I have to install the Wacom Pen Tablet drivers and software on my machine when I dont use them... Its still complaining it cant find them even though its there!
I just tried it again (now that the above is cleaned);
Failed to open a session for the virtual machine Windows 10 TP.
The virtual machine 'Windows 10 TP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Windows 10 Preview\Windows 10 TP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Re: Apparently common error starting the Win10 VM
Posted: 30. Dec 2014, 01:21
by Perryg
You should be able to work around the tablet issue by selecting the PS2 mouse in the guest settings instead of the touch pad.
Re: Apparently common error starting the Win10 VM
Posted: 30. Dec 2014, 01:27
by GaryBouchard
Perryg wrote:You should be able to work around the tablet issue by selecting the PS2 mouse in the guest settings instead of the touch pad.
Thank you Perryg! It was already set to ps2 mouse.