Network card issues

Hi,

I'm hoping someone can point me in the right direction, as this issue is driving me nuts.

When I turn my PC on from not being used for a few hours, it shows that there is no network card and when I go into network connections, the onboard (inbuilt into my motherboard) network card is not detected. I can only get a network card to be detected if I do 1 of the two following:

A) Restart the PC and the network card is detected straight away.

or

B) Go into Administrative Tools > Device Manage and select 'Scan for hardware changes' and then the network card is instantly detected and I have a network connection again.

I have tried removing the driver and reinstalling it, but that doesn't resolve the issue. Any ideas on what could be causing this?

Thanks in advance.

Cheers,

Ross

Thanks for that. I will give it a try when I get home. I know for certain my network card doesn't have that setting under power management settings as I looked for it earlier.

Thanks again for your help.

topgundcp said:

Things to check:

1. Open Devices manager, under Network adapter, right click on the Network card->Properties->Power Management and uncheck: Allow the computer to turn off this device to save power.
2. Check if the cable is properly seated.
3. Download: Release DriverStore Explorer v0.8.4.2 · lostindark/DriverStoreExplorer · GitHub
   then run. Delete the driver completely then re-install

I gave all of these a go and unfortunately it hasn't resolved the issue. When I just turned on the PC again I had to go into Device Manager and select 'scan for hardware changes' to get the network card to be detected.

Try disabling hibernation. In a Command Prompt (Admin) or Powershell (Admin) run:

powercfg -h off

You can turn hibernation back on with powercfg -h on if disabling hibernation does not fix the problem.

Thanks for the responses. So far I am still having the issues, despite trying all the fixes kindly suggested to me.

It is my workhorse desktop PC (i7 2600k, 16gb Ram, Sabertooth P67 mobo). It does have a VPN on it as I need it for development testing at the moment. I'm pretty sure this issue presented itself before the VPN was installed though and have removed it previously to see if it helped the issue and it didn't unfortunately.

The only other software I have installed that I assume impacts on my network connections is Kaspersky Internet Security 2017.

bro67 said:

Ditch Kaspersky. There was a note put out that they have been getting private files sent to them when their software tags it was needing further inquiry. It also interferes with the VPN and most likely your issue is with Kaspersky.

Windows Defender and Firewall are up to par with anything you can buy these days. I use Symantec's Cloudpoint security on our desktop and the Macbook and have not had any issues with it. The Cloudpoint group had to help with issue that I was having when it balked and they worked through that at no extra cost and went beyond anything I expected.

I use OpenVPN with SmartDNS and Tunnelbroker on my Macbook Air. Zero issues with it and Symantec. If you need to harden Windows 10 after removing Kaspersky, use this guide. Harden Windows 10 - A Security Guide. How to secure Windows 10 Yes the NSA did the hardening and firewall rules, nothing gets sent to them from those rules. Just be careful when hardening and make a copy of your hard drive before doing. You can use Clonezilla to make a image to a NAS or Pocket drive larger than your computer hard drive.

This of course happened in 2015, but with the current state of affairs, I would stay away from anything that has foreign ties, especially with Russia. Kaspersky says NSA hacking tools obtained after malware was found | ZDNet

Thank you for that. I wasn't aware of that, so when I have finished this project I will look to ditch it.

Some good news on the network card issue - For the past few days the issue hasn't occurred and I have no idea why. I'm not complaining though, so fingers crossed it is resolved for good now.

Thank you very much for everyone's assistance.