Since latest Windows 10 versions don't install RNDIS network automatically I need to perform the following procedure after each Windows reboot to connect to my evaluation board:
Device Manager > RNDIS > Update driver > Browse... > Let me pick... > Microsoft > Remote NDIS compatible device
I couldn't figure out how to do it neither in Powershell nor in pnputil.
Is there a way to automate it?
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 have a clean install of Windows 10. After installing Visual Studio 2015 and Xamarin Bussiness edition I installed Xamarin Android Player x64 and now I receive the following error:
Error when attempting to find VirtualBox please check it's installed and try again.
Xamarin Android Player will now exit.
A solution is referenced in Xamarin fourms stating
Fixed it by adding "C:\Program Files\Oracle\VirtualBox" to my %PATH%
I am able to open VirtualBox version 4.3.28 r 100309 without issue.
How do I implment this solution or is there a newer solution?
I am running Windows 10 Professional and did a clean installation. Had the same problem. I opened the environment variables and the "VBOX_MSI_INSTALL_PATH" was set to:
C:\Program Files\Oracle\VirtualBox\
I changed it to
C:\Program Files\Oracle\VirtualBox
and it worked for me.. (notice the last backslash)
Thanks .. Ragnar Kofi Billy Force on facebook
Try installing the Latest version of Virtual Box, Since v5.0 has fixes for Windows 10
http://download.virtualbox.org/virtualbox/5.0.4/VirtualBox-5.0.4-102546-Win.exe
Changelog: https://www.virtualbox.org/wiki/Changelog
Windows hosts: fixed crash when opening Windows dialogs from the VM process on Windows 10 (bug #14351).
Windows hosts: fixed host-only adapter creation issues on Windows 10 (bug #14040)
Windows hosts: fixed audio on Windows 10 (bug #14432).
Windows Additions: fixed a potential crash in the WDDM driver with Windows 10 (bug #14190).
VRDP: allow Windows 10 RDP clients (bug #14216).
Windows hosts: fix for Windows 10 build 10525 and later (bug #14502).
Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437).
VMM: fixed an issue with Windows 10 guest kernel debugging over the network for Hyper-V paravirtualized VMs.
I have a same problem too and installing the latest version has fix it
Add VirtualBox to your system environment PATH variable.
None of the other answers helped me. The Android Player installer was forcing the install of Virtual Box 5.0.4 which was not working on Windows 10 Home (build 14393.51).
What did work for me was to install the latest virtual box (version 5.1.2 r108956) after installing Android player. While I can't start the android devices from Virtual Box's manager, I have had no problems starting them from Android Player or Visual Studio.
Just run as admin (Right hand click on desktop shortcut)
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 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.
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