Default Gateway not holding after windows update

[Rosco2382]

My laptop won't hold the default gateway anymore. I did a system restore back to 2/4/14 prior to a windows update. When I did this I followed all the steps I saw on previous threads with similar issues and it worked. I allowed my laptop to run the windows updates last night and today it wouldn't connect to the internet. I couldn't connect via wireless or through my work network. I did a system restore back to 2/4 and I am able to connect again. Anyone have any ideas as to what could be causing this or what I can do to fix this. My IT department has looked into this but can't seem to figure it out. Since it is my personal laptop they can only do so much as well. Please I need help it is getting frustrating to have to do system restore to get on the internet.

Attached are a screenshot of the windows updates trying to go through and the ipconfig all file.

 

[chev65]

My laptop won't hold the default gateway anymore. I did a system restore back to 2/4/14 prior to a windows update. When I did this I followed all the steps I saw on previous threads with similar issues and it worked. I allowed my laptop to run the windows updates last night and today it wouldn't connect to the internet. I couldn't connect via wireless or through my work network. I did a system restore back to 2/4 and I am able to connect again. Anyone have any ideas as to what could be causing this or what I can do to fix this. My IT department has looked into this but can't seem to figure it out. Since it is my personal laptop they can only do so much as well. Please I need help it is getting frustrating to have to do system restore to get on the internet.

Attached are a screenshot of the windows updates trying to go through and the ipconfig all file.

I'm really not sure which update might be causing this problem, you could try installing one update at a time until you find the culprit then hide that particular update so it won't install again.

Have you tried connecting with DHCP enabled?

Have you tried typing the default gateway into the IPv4 properties manually?

 

[Rosco2382]

I'm really not sure which update might be causing this problem, you could try installing one update at a time until you find the culprit then hide that particular update so it won't install again.

Have you tried connecting with DHCP enabled?

Have you tried typing the default gateway into the IPv4 properties manually?

The office I work out of uses a VPN connection so they have all the computers here manually set up with static IP address. When I try to manually add the Default Gateway it takes it, but then after I hit Ok it doesn't hold it. I even have tried going into the advanced menu and add it there as well. Still won't hold. If I try to connect to the wireless I get the Limited Access to my hotspot. I suppose I can try to do one update at a time but does it seem like the windows updates might be the issue?

 

[chev65]

I'm really not sure which update might be causing this problem, you could try installing one update at a time until you find the culprit then hide that particular update so it won't install again.

Have you tried connecting with DHCP enabled?

Have you tried typing the default gateway into the IPv4 properties manually?

The office I work out of uses a VPN connection so they have all the computers here manually set up with static IP address. When I try to manually add the Default Gateway it takes it, but then after I hit Ok it doesn't hold it. I even have tried going into the advanced menu and add it there as well. Still won't hold. If I try to connect to the wireless I get the Limited Access to my hotspot. I suppose I can try to do one update at a time but does it seem like the windows updates might be the issue?

I'm pretty sure it will be just one Windows update that is causing the problem but no idea which one it might be.

If the static gateway settings aren't sticking they could be over ridden by what ever is controlling the static IP's which could be the router or the server.

About the only other fix I see for this would be to reset winsock and TCP/ip using the following commands, one at a time paste into elevated command prompt.

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)