Take's 5 mins to connect to the interent from boot up.

This has gone on for ever it seems like. When I turn the PC on windwos will boot up try to get the intenret working but nothing is connected causing everything else starting up to not work or go crazy saying it can update and what not. I've tried reinstalling the drivers updating the drivers and still nothing. It doesn't do this on the other PC they all are up and running when they boot up.

when you start open cmd prompt type ipconfig /all does it have a valid ip not one starting 169? Try setting a static ip

nope on boot up it shows nothing but "windows IP condfiguratio" and "tunnel adapter isatap.home" only after connecting does it show anything from the ethernet adapter local area connection

So it shows the device ok but no ip? did you try setting a fixed ip?

if i try to set the IP i get DHCP is not enabled for "local area cnnection"

Tried it anyways with a restart and no go.

If your getting that message you have set it up wrong post results from ipconfig /all when it's working and we can you the right numbers

One screen shot coming up (filler)

there was only three number i could use so not sure what would mess up on it

Set IP to 192.168.254.30 subnet 255.255.255.0 gateway 192.168.254.254 DNS 208.67.220.220 & 208.67.222.222

same error

samuria knows way more about such things than I do, but I do have a question.

Are you using a VPN?

Jack

Nope no VPN

even with the error with them settings still no auto connecting on boot up. It seem like it almost doesn't start the driver or something till after the PC is on for a bit.

well was worth a shot too bad windows can run internet at start up maybe in windows 11 HA

wonder if mac at least lets you connect since windows wont

If you can connect after a few minutes, then there's probably some junk that's loading at bootup which is taking a lot of time to load.

Go into MSCONFIG, and click on the Services tab. Check the box that says "Hide all Microsoft services". Now check all the rest, then click "Disable all". Now restart the computer.

If doing the above fixed the problem, then there is a non-Microsoft service that was running that was causing the problem.

You could leave all of the non-Microsoft services disabled; but if you do that, some things aren't going to work (e.g. your anti-virus protection). To enable all except the one that caused the problem, go back into MSCONFIG, to the Services tab, and enable everything that you are sure didn't cause the problem. Now reboot. If the problem has not returned, then enable one service at a time (rebooting after each re-enable), till you find the culprit. Leave the bad service disabled, and you should be good to go.