Unable to load Process Monitor device driver In the Event Viewer, I get the follow. Stack Exchange Network Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to. How about adding something like a 'Monitor drivers' feature to Process explorer where it uses the same sequence of debugging steps to maintain a list of non-microsoft device drivers that frequently use a lot of cpu? I know some would always be expected to show up but perhaps these can be marked as known and then unknown ones highlighted?
![]()
Laco09 wrote.Extract: INSTALL -win32.txt. 100%Extract: COPYRIGHT.GPL. 100%Extract: icon.ico.
100%tapinstall hwids returned: 0TAP UPDATEUpdating drivers for tap0901 from C:Program Files (x86)OpenVPNdriverOemwin2k.inf.tapinstall.exe failedtapinstall update returned: 2tapinstall cumulative status: 2.That looks interesting. Why are you installing into the x86 directory?
![]()
I am running win7 64 and it installs into the non-x86 directory. Did you completely delete the program files(x86)/openvpn directory before you tried to reinstall?Do a complete uninstall and delete any openvpn directories.
Then use the current stable version (not the x8664 but the x686 version). Maybe it is looking there first when it is either not in that location or there is an older installation that you have. So, I've had this issue numerous times and I just had it again. However, the fix I posted on the official bug report here worked again for me.I stopped all virtualization software and kicked off the install again (didnt even have to reboot). The install went through just fine.
The only virtualization software I use is VirtualBox and Sandboxie. I stopped Virtualbox machines and closed all Sandboxie Sandboxes.It's most likely a driver conflict with another software. It's easily reproducible by just using the above software. I'm guessing it's mostly Sandboxie in my case. It may be something similar for everyone else. Check all of the services you have running in services.msc.
Another way to try and help diagnose it would be using Process Monitor to monitor any errors that appear to come from the installer while you're installing.BTW, this was with the latest version as of July 3, 2018: 2.4.6.
![]()
I listen to Tim, Tony, Chris et al talking on LMTV about networking and I realise how little I know about real networking; you know that layers 1 to 3 stuff. I m a layer 4 to 7 type of guy, and so I m always going to push the boundaries on this forum. Have I gone too far this time.
Let s see.I saw a post on another forum this week from a guy who had a particular problem with files on a Windows server. A user deleted a file, but when he came back in the following day it had reappeared.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |