I have a Virtual Smart Card Reader driver. It installs correctly at my PC (Windows 7 x64). But installation fails when I install it at another Windows 7 x64 PC. Of course I install them in the same way:
devcon install <inf> <hwid>
I compared setupapi.dev.log files and found the difference at very first line:
Successful sessions at my PC always starts from
[Device Install (Hardware initiated) - {892EDE5E-BE49-443c-A0B3-005D74F2D69C}\ScFilter\1&3908c5bd&9&01]
Failed sessions at another PC always starts from
[Device Install (UpdateDriverForPlugAndPlayDevices) - root\BixVirtualReader]
I had another Virtual Smart Card Reader at Divice Manager. But I switched it off before the installation of new driver.
Related
I'm facing a problem while trying to install a signed driver on my Windows 7 computer.
In order to install the driver I'm using the command (CMD as Administrator):
sc create my_driver type= Kernel binPath= "c:\my_driver\driver.sys"
Windows Failure
Driver signatures
The driver is working just fine in Windows 10
I try to install .cab file via Windows Device Portal running on Raspberry Pi 3 with Windows IoT Core 10.
How ever there is eternal update process.
I get error:
Failure reason: Failed to install CAB file as device is in the middle of an update.
Some other error I get via Power Shell: Windows IoT error on driver install: Could not start update, (0x8024A10F)
I stopped the update service as described here: https://developers.de/blogs/indraneel/archive/2016/04/22/how-to-disable-the-auto-update-on-windows-10-iot-core.aspx and made restart, however it didn't solved the problem.
UPDATE
Here a write about the way, I assembled the driver:
Windows IoT error on driver install: Could not start update, (0x8024A10F)
I'm new on LG smart TV apps. I've installed the SDK provided by LG (Oracle Virtual Box, Safari, Eclipse, sdk itself).
Now everything is running, but when I try to launch the emulator, a remote control is displayed, and on the virtualbox window, I see an error and no emulator is launched.
This is my plataform:
Windows 7 on a intel i7, 8 gb ram
Virtual Box 4.1.18 (I've installed 4.2.4 before, but sdk installer replace it to 4.1.18)
Safari 5.1.7
Java JRE 1.6
LG Smart TV SDK 3.0.0
This is the log generated by Virtual Box:
VirtualBox 4.1.18 r78361 win.amd64 (Jun 5 2012 15:58:23) release log
00:00:05.144 Log opened 2015-09-28T15:09:54.564361900Z
00:00:05.144 OS Product: Windows 7
00:00:05.144 OS Release: 6.1.7601
00:00:05.144 OS Service Pack: 1
00:00:05.144 Host RAM: 7926MB RAM, available: 864MB
00:00:05.144 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:05.144 Process ID: 12536
00:00:05.144 Package type: WINDOWS_64BITS_GENERIC
00:00:05.145 Installed Extension Packs:
00:00:05.145 None installed!
00:00:05.156 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:05.439 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false
Is there any known issue about this? What is the reason because "Power up failed"? How can I fix the VM? Does this software really works on Windows?
Thanks!
I would try 4.2.18 and make sure you are installing the correct SDK for your OS (x64/x32).
You can uninstall VBox and reinstall if needed and again check your architecture
I get a MSI failed message every time when I install Vmware Worksatation 11 on my windows 8.1 computer. I've tried to clear previous temp data but it doesn't work.
Thanks.
I have the same problem and have fixed it.
Try to disable Hyper-V on Control Panel >>> Programs >>> Turn windows features on or of >>> Unselect Hyper-V >>> Click Ok and restart your computer
If you attempt a VMware Workstation 11 install, and it fails part-way through, a reboot typically addresses the install failure. If not, can you:
post some more information about what the error is
post the %TEMP%\vmsetup*.log files from your failed install attempt
I have working
kernel debug setup on old host computer with Windows Xp. On the new computer i
get preinstalled Win 7. I have installed PCI to Firewire card (usb-5pci3pfw).I
have installed WinDDK (7600.16385.1).
So I go to
C:\WinDDK\7600.16385.1\Debuggers and run as administrator windbg.exe
(6.12.2.633)
Choose File
> Kernel Debugging > 1394 > and select channel like on target and get
this message:
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\SysNative\drivers\1394kdbg.sys.
Cannot install a 32 bit driver on a 64 bit host.
Please run the 64 bit native version of this debugger to
upgrade to the latest version of 1394kdbg.sys.
Kernel debugger failed initialization, HRESULT 0x80004005
"Unspecified error"
I expect that
WinDbg will make install of the 1394kdbg.sys driver.
Yes in C:\WinDDK\7600.16385.1\Debuggers\1394 directory there 1394kdbg.sys and
1394dbg.inf.
In inf file
there install section only for 32 bit.
I try to add
64 bit section and install driver but it doesn't helps.
Does somebody know the right way to
install kernel debugging on Win 7 64 bit Host?
You have to install and use the x64 debugging tools.
These should be part of the Windows SDK.
So yes install of "Debugging Tools for Windows (x64)" did help.
I downloaded Windows SDK as Christopher wrote.
Selected install of debug tools, i did have some problems during installation because i have installed Visual Studio Compilers so i use Help from Here
Then Windows SDK copy installation .msi files here:
"C:\Program Files\MicrosoftSDKs\Windows\v7.1\Redist\Debugging Tools for Windows"
In this folder:
dbg_amd64.msi - (64 bit version of debuging tools)
dbg_ia64.msi - (for Itanium processors)
dbg_x86.msi - (32 bit version of debugging tools)
i install "dbg_amd64.msi" and get 64bit debugging tools folder here:
"C:\Program Files\Debugging Tools for Windows (x64)"
now in 1394 subfolder there "1394kdbg.sys" and "1394dbg.inf" for 64bit.
so now i connect my host win7 64bit computer over firewire to target.
run "C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe" as administrator
Choose File > Kernel Debugging > 1394 > and select channel like on target
and get finally
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\system32\drivers\1394kdbg.sys.
Attempting 1394 debug driver installation now. "i get pop up to install drivers"
Driver installation successful.
Retrying 1394 channel open.
Opened \.\DBG1394_INSTANCE10
What is interesting when i did install "Windows Drivers Kit 7.1.0"
i didn't found 64bit version of debugger in "C:\WinDDK\7600.16385.1" folder.
Installation of 1394 kernel debugging on Target side for winxp x86:
Open a CMD window
attrib -s -h -r c:\boot.ini
notepad c:\boot.ini
Add these lines:
[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows" /fastdetect /debug /debugport=1394 /channel=10
Reboot the machine
Installation of 1394 kernel debugging on Target side for Windows Vista up:
Read Here