Windows 10 (NIC) network connect on boot

%3CLINGO-SUB%20id%3D%22lingo-sub-1591373%22%20slang%3D%22en-US%22%3EWindows%2010%20(NIC)%20network%20connect%20on%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591373%22%20slang%3D%22en-US%22%3E%3CP%3EMore%20a%20niggle%20really%2C%20I%20have%20a%20new%20Z390%20UD.%20it%20has%20been%20working%20happily%20on%2010%20update%201909%20since%20production.%20I%20have%20resently%20had%202004%20pushed%20and%20installed.%20Ever%20since%20I%20have%20noticed%20that%20the%20connect%20time%20is%20upwards%20of%2045%20seconds%20from%20Power%20on%2C%20that%20is%20shown%20by%20the%20globe%20symbol%20with%20no%20entry%20sign%20in%20the%20bottom%20right%20of%20screen%20then%20changes%20to%20Network%202%20Internet%20access%20symbol%20ie%20connected.%20I%20can%20log%20in%20at%20any%20time%20after%20the%20windows%20home%20screen%20becomes%20available%206%20to%2015%20seconds%20I%20think%20as%20I%20use%20local%20password%20however%20the%20desktop%20is%20available%20with%20no%20network%20connect.%20Until%20Network%202%20becomes%20available.%20Have%20checked%20to%20my%20satisfaction%20that%20it%20is%20not%20just%20connection%20to%20internet%20but%20also%20connection%20to%20router.%20(set%20chrome%20browser%20to%20home%20page%20as%20router%20maintenance%20page%20and%20got%20no%20connect).%20I%20have%20swapped%20network%20cable%20back%20to%20my%20old%20pc%20and%20that%20works%20fine%20so%20not%20cable%20either.(total%20connect%2012%20seconds%20ish.%20Windows%20performs%20normally%20after%20connection%20not%20slow%20or%20slow%20network%20file%20transfer.%20Has%20anybody%20else%20had%20similar%20problem%20at%20boot%20with%202004%20or%20solution%20%3F%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591399%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20(NIC)%20network%20connect%20on%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591399%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F760603%22%20target%3D%22_blank%22%3E%40Millfield%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20already%20install%20the%20latest%202004%20compliant%20LAN%20driver%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.gigabyte.com%2FMotherboard%2FZ390-UD-rev-10%2Fsupport%23support-dl-driver-lan%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.gigabyte.com%2FMotherboard%2FZ390-UD-rev-10%2Fsupport%23support-dl-driver-lan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Spigolo_0-1597578305291.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F212646i00184659F1B03433%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Spigolo_0-1597578305291.png%22%20alt%3D%22Spigolo_0-1597578305291.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1592430%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20(NIC)%20network%20connect%20on%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1592430%22%20slang%3D%22en-US%22%3EYes.%20Downloaded%200212.2020%20from%20the%20gigabyte%20site.%20This%20did%20not%20change%20the%20problem.%20I%20have%20rolled%20back%20the%202004%20update%20and%20confirmed%20that%20the%20NIC%20connects%20early%20in%20boot%2C%20also%20the%20rollback%20rolls%20back%20the%20driver%20to%201118.2019.%20I%20have%20put%20off%20accepting%202004%20for%20a%20163%20days%20but%20the%20problem%20of%20the%20update%20is%20not%20going%20to%20go%20away%20of%20its%20own%20accord.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1592449%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20(NIC)%20network%20connect%20on%20boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1592449%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F760603%22%20target%3D%22_blank%22%3E%40Millfield%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet%20in%20touch%20with%20Gigabyte.%3C%2FP%3E%3CP%3EThey%20could%20be%20aware%20of%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

More a niggle really, I have a new Z390 UD. it has been working happily on 10 update 1909 since production. I have resently had 2004 pushed and installed. Ever since I have noticed that the connect time is upwards of 45 seconds from Power on, that is shown by the globe symbol with no entry sign in the bottom right of screen then changes to Network 2 Internet access symbol ie connected. I can log in at any time after the windows home screen becomes available 6 to 15 seconds I think as I use local password however the desktop is available with no network connect. Until Network 2 becomes available. Have checked to my satisfaction that it is not just connection to internet but also connection to router. (set chrome browser to home page as router maintenance page and got no connect). I have swapped network cable back to my old pc and that works fine so not cable either.(total connect 12 seconds ish. Windows performs normally after connection not slow or slow network file transfer. Has anybody else had similar problem at boot with 2004 or solution ? Thanks

3 Replies
Highlighted

Hi @Millfield  

Did you already install the latest 2004 compliant LAN driver?

https://www.gigabyte.com/Motherboard/Z390-UD-rev-10/support#support-dl-driver-lan 

 

Spigolo_0-1597578305291.png

 

Highlighted
Yes. Downloaded 0212.2020 from the gigabyte site. This did not change the problem. I have rolled back the 2004 update and confirmed that the NIC connects early in boot, also the rollback rolls back the driver to 1118.2019. I have put off accepting 2004 for a 163 days but the problem of the update is not going to go away of its own accord.
Highlighted

@Millfield 

Get in touch with Gigabyte.

They could be aware of the issue.