RealTek PCIe GBE Family controller always sees no cable when booted.

IrvSp

Distinguished
Aug 17, 2013
92
0
18,660
This just started AFTER I updated the driver to the latest release this month. Before that the cable was always seen when booting as connect and the network was working. Now I always get a RED X and it says no cable connected. Open the NETWORK SHARING CENTER, NETWORK CONNECTION, highlight the NIC, DISABLE, ENABLE and it finds the cable OK and connects. Have to do this on every boot, whether it is a cold start from power off or a re-boot.

I've tried rolling back the driver, no change. I've tried deleting the NIC and on re-boot it works fine, Windows re-installs it as it sees it there during boot, however the next boot and the problem is back?

I've completely uninstalled the driver and re-installed, vs. doing a repair, problem persists.

Suggestions? Suspect it might be a service loading order problem?
 

IrvSp

Distinguished
Aug 17, 2013
92
0
18,660
ASUS RT-N56U running the latest Padavan s/w flash.

This has NEVER been a problem as I was running an older RealTek driver too, not the default MS one, 8.7.1025.2012, which was signed by Microsoft Windows Hardware Compatibility Publisher. The older RealTek replaced that one with no problems. Once I installed the latest, from 7/23/13, 8.018_0723013, the problem started.

What makes it worse, I lost the OLDER RealTek that was working. Now since I've played with it and did some Rollback's, there is none now? If I delete the device and driver in Device Manager, and re-boot it will install the MS default one, but that now exhibits the same problem of not finding the cable initially?
 

IrvSp

Distinguished
Aug 17, 2013
92
0
18,660
Well, today, it worked fine, that is the NIC initialized and connected to the internet on boot. I am running with the included MS W8 driver from 2012 though. It appears to work fine.

Yesterday it wouldn't, and I know I booted with it a few times. I did so many rollback's, updates, deletes, uninstalls, I lost count, and yesterday it never worked either with a re-boot or shutdown and boot?

I'll not call this solved yet though.

I guess the real question is do I really need the RealTek driver, or I guess the question should be WHY would I need it?
 

IrvSp

Distinguished
Aug 17, 2013
92
0
18,660
Aatje92, I agree. I was using the prior RealTek without problems, but now I'm back to the MS default driver, and I'll keep using it. 2 days, a few boots, both from power off and re-boot, and no problems.

Has to be either some sort of delay in seeing the cable and it times out or some order in starts up drivers or services is not correct for that driver.