Cannot load the device driver VBoxNetLwf.inf

[Andy_75]

I cannot post my question as the system thinks I have URLs in it.... So, I have to post this stupid teaser before I can post my real question. In 24 hrs, I'll ask my question.

Andy

[Andy_75]

Was already working on it.

If you like, you can post that text in my original message and delete all these other posts.

[scottgus1]

Thanks, this is the text of Andy_75's question:

Before everyone goes off on me, yes, I've searched. I have found many posts that are now closed. All of them seemed to have fixed their issues.

My Host:
M$ Windows 10 Enterprise
Version 10.0.18363 Build 18363
System: Latitude 5300 2-in-1 (Barbie Laptop)
Processor: Intel Core i5-8365U CPU at 1.60GHz, 1896 Mhz, 4 Core(s) 8 Logical Processors ----- This seems WAY slower on my system than what these specs say.
HyperVisor is turned all the way off. This was due to previous versions of VB not working AT ALL with Windows 10 and HyperVisor. If I should reenable it, let me know.

I have installed the latest version of VB today 4 times (in every configuration I could think of based upon the suggestions in about 8 posts). The binary I downloaded from the VB website was VirtualBox-6.1.32-149290-Win.exe.

What I want to do is make my system talk between the client (Slackware Linux -- no idea the version it was "current": Linux akennedySlack.me.net 5.4.75 #1 SMP Thu Nov 5 13:23:27 CST 2020 x86_64 Intel(R) Core(TM) i5-8365U CPU at 1.60GHz GenuineIntel GNU/Linux - kernel was updated and APCI was turned off as it kept BSODing my system) and the host. From all of what I read, all I have to do is enable "Local Host Only device" put in 192.168.56.1 as the host's IP address, and 192.168.56.56 as the client IP address. I have already added the firewall rule to allow all traffic through this connection. The issue is, I cannot get VBoxNetLwf.inf to install. When I install it by browsing to the VB drivers directory, right click and select "Install", I get back "The operation completed successfully". I open the Device Manager and it shows up in the list for just a few seconds (with a yellow exclamation point above it) and goes away. At one point it stayed around for a brief moment so that I could see the message "This devices does not work properly with this system."

There was no way to temporarily disable my virus software, so, I uninstalled it. No workie. I cannot make the device driver install.

There are other protective-ware utilities installed on my system. I am about to go through and uninstall all of those too (just to see if I can make it work disabling that). BUT, if anyone has any ideas about what I can do to make this work, please provide it.

Thanks,
Andy

[scottgus1]

Thanks for the text file.

The special install reps for that driver file aren't normally necessary. Please try uninstalling Virtualbox then reboot the host.

Then go to C:\Windows\System32\Drivers and look for .sys files starting with 'Vbox' There could be up to 5 such files. Delete them if found.

Then right-click the Virtualbox installer and choose Run As Administrator. Try Virtualbox and please let us know what happens.

[scottgus1]

akennedySlack.me.net

This could be the URL being triggered on, BTW.

[Andy_75]

Will do. Done most all of that (the one thing I didn't do was remove the driver cache).

[Andy_75]

Okay, hurdle one done. So, I can see the eth device in the host, it has the expected IP addr. I set the IP addr in the client and I cannot ping. I'm going to check the firewall settings again to see if they got changed by my IT (very likely).

BUT, thanks for the help. As far as the match on the U R L, I think it may be any dot followed by NON white-space. I believe even my ellipses chocked me. And, I use too many ellipses.

Thanks again for the help.
Andy

[Andy_75]

Thanks for the text file.

The special install reps for that driver file aren't normally necessary. Please try uninstalling Virtualbox then reboot the host.

Then go to C:\Windows\System32\Drivers and look for .sys files starting with 'Vbox' There could be up to 5 such files. Delete them if found.

Then right-click the Virtualbox installer and choose Run As Administrator. Try Virtualbox and please let us know what happens.

So, yes, this was the fix. The other issue with it not working is that I had my VPN engaged. Stupid VPN. There seems to be no way around that. I guess, when I need to do my work, I'll have to disconnect from the corp VPN.

Thanks Scott!
Andy

[mpack]

As far as the match on the U R L, I think it may be any dot followed by NON white-space.

It doesn't really matter what the rule may be, right? Because the indicated string clearly is a URL.

[fth0]

Because the indicated string clearly is a URL.

FWIW, the input string is only a (fully qualified) domain name. The BBS software automatically converts it to an URL under certain circumstances, that's where the problems start.

[scottgus1]

any dot followed by NON white-space

No, not quite so restrictive. Otherwise things like '1.60GHz' wouldn't be postable, and they are from the beginning.

'.net' is a valid 'last part' of a web address (along with .com, .edu, and a slew of new ends). And as can be seen by Intel's processor information website 'ark.intel.com', the first two parts of the typical 3-part web link can be pretty much whatever the web site maker desires.

As fth0 points out, 'akennedySlack.me.net' looks like a web link and gets turned into a URL by the forum software, and as Mpack points out, that trips on the 'first day' rule.

Though it's pretty much a moot point by tonight, folks can obfuscate web links they feel must be in the post by adding spaces around the dots to break up the zzz.yyy.xxx pattern of the link, then the mods investigate and decide if the link is appropriate. Or folks can add things in an attached zip.