All of my VM's can't connect to network

[Sad Nation]

Hi

I have about 10 VM's of all different OS's from old versions of Windows to Ubuntu and OSX. Until the last few days I had no problems whatsoever. From about Tuesday or Wednesday none of my VM's will connect to the network and therefore no internet with any of them. I have changed nothing on the VM's but all of them stopped connecting at the same time.

I have reinstalled Virtualbox several times, reinstalled the VBox additions and the VBox extension pack but no joy. The network card is just using the standard NAT as it has from several years ago. I have no idea why it suddenly stopped working.

My Specs:-

Windows 8.1 fully updated
i7 4770k @ 4.5 Ghz
16 GB Ram
Nvidia 780ti

VM's:-

Windows 10 Insider Preview
Windows 8.1
Windows 7
Windows Vista
Windows XP
etc

[Perryg]

Things don't stop working without a reason. What happened? Host updated, or other? I would look at the host for your answer as all of the guests must use that, and since they are all showing the same issue, well.... there you have it.

[Sad Nation]

Well the host still has network connection and internet so its not that. Just Virtualbox can't seem to see or use it! That's why I was reinstalling VB and associated programs.

[Perryg]

Post the guests log file ( as an attachment )

[Sad Nation]

Here is the log as requested. Thanks for helping!

[Perryg]

Code: Select all

00:00:20.339359 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\LavasoftTcpService64.dll: Not signed.

So did you install lavasoft and start having problems? Or was it updated and you started having problems?

[Sad Nation]

No I didn't install Lavasoft, at least not intentionally. I don't have it any more but I have had some malware which I have now got rid of which might have been related to that.

[Perryg]

Well the error message is clear and lavasoft is why your network stack will not load in VirtualBox. The unsigned driver will not be loaded and this started with release > 4.3.12

[Sad Nation]

Cool, that's a relief that there is a known problem. How do I put everything right? And thank you yet again for helping me!

[Perryg]

I'm afraid that is between you, lavasoft, and microsoft. You need to eliminate the unsigned driver or the network stack will not work.

[Sad Nation]

Well that's helpful. At least I know what I am looking for I suppose. Has anyone else had this problem before and if so, what did you do?

[Sad Nation]

Well I have run Malwarebytes, HitmanPro, Rogue Killer several times and blasted all known bad guys. Searched and deleted all mentions of Lavasoft in my OS, done the same to the registry, rebooted more times than I want to remember and still the problem persists. Arrrggghhh!!!

[Perryg]

Then post a new guest log.

[Sad Nation]

Here is the latest file, no mention of lavasoft this time so maybe that was a red herring.

[Perryg]

No such luck as a red herring. Now the link state is up for this guest.

Code: Select all

00:00:11.511419 NAT: link up

Now you need to look at the actual host network and make sure that the VBox network driver is still installed and not broken.
Also it would help if you chose a different guest as there have been issues with W-10 in the past.