Has anyone ever seen a behavior in Windows 8 or 8.1 where assigned static IP settings fail to display in the tcp settings fields on a nic configuration window?

As an example, if we configure a NIC with static settings, save, close the settings windows and immediately re-open, it shows everything as DHCP defaults. 

This is not a matter of invalid entry or IP settings.

If we run ipconfig right after saving, you clearly see the saved static settings and the network card is in-fact operational on the settings. The issue is simply the GUI displays DHCP defaults each and every time, regardless of. Ironically, if we run "diagnose" on the NIC (while on a different subnet) it recommends switching back to DHCP. So the logic clearly confirms a static address is defined, the GUI seems to have a bug. 

This only affects Windows 8 and 8.1 machines, never seen it on 7 or back. 

Already attempted the fix listed on the BOTTOM of this other thread:
http://social.technet.microsoft.com/Forums/en-US/70762c1c-da6d-45b7-b3bf-b7079abf8469/windows-server-2008-can-not-see-static-ip

Hi,

Were the machines in a domain environment?

Please check the Group Policy.

Based on my test ,I didn't get this situation.

I suggest you try using the command to configure the static IP.

To set the machine with a static IP address

At a command prompt, type the following to show interfaces:

netsh interface ipv4 show interfaces

ADD IP ADDRESS:

netsh interface ipv4 set address name=Local Area Connection source=static address=192.168.0.10 mask=255.255.255.0 gateway=192.1.0.1

DNS SERVER:

netsh interface ipv4 add dnsserver name=Local Area Connection address=192.168.0.15 index=1

netsh interface ipv4 add dnsserver name=Local Area Connection address=192.168.0.15 index=2

Then,we open "Internet Protocol version 4(TCP/IPv4) Properties" to check the result.

If the issue persists,please upload the screenshot for ipconfig /all.

Re

Hello.-

We have same problem. Netsh commands changes address and other properties succesfully. However when these properties are accessed via rightclick ->properties of nic, keeps showing that DHCP is enable and not IPs are shown !.

We have reset tcp/ip, disable and reboot the PC but no success.

Thanks.

Exactly the same thing we are having ... 

What brand of PC? Type of NICs? 
The windows image you are using, is it OEM/PKC, Volume, etc?

We've seen this on HP laptops thus far, nothing else. 

This is a Intel Motherboard, not  a Brand computer.

The only special condition is that the PC was an upgrade from a Windows 8.0 installation.

Hello.-

I am not agree that this was marked as a answer. As I mentioned bellow, these steps were followed without success. There is another condition that is not covered by this recomendation.

Hello <o:p></o:p>

I'm having the same problem. Netsh commands changes address and other properties successfully. However when these properties are accessed via the GUI display, it keeps showing that DHCP is enable. Im running on a surface pro 2 with windows 8.1. The problem occurs with different USB nic adapters, and on or off the domain.<o:p></o:p>

Hello.-

Apparently this link fixes this issue in windows 8.1.

http://support.microsoft.com/kb/937056

• Proposed as answer by WillPeters Thursday, September 18, 2014 9:44 AM

The above article may work temporarily, but this problem keeps coming back for me. And it happens to ALL of my network adapters. I own an IT consulting firm and have been doing IT for over 15 years, and this is one of the only things that has stumped me completely. It has to be a bug in Windows, along with something in my environment that makes it keep coming back. I've even reformatted my Win 8.1 computer from scratch, which fixed it for a very short time, then the problem came back. Here's the things I've thought of or taken note of thus far about my environment that may be a trigger:

- I've uninistalled anti-virus software just in case
- I have VMware Workstation installed, which creates virtual interfaces
- I use a FortiClient VPN, which also creates virtual interfaces (IPSec & SSL)
- I use a USB 3.0 docking station while I'm at the office, which has GB ethernet built in

In addition to the problem with being unable to manage IP settings via GUI, I've had continual problems with my FortiClient VPN software and my hunch is that these two symptoms are related because the same exact FortiClient (and configuration) works on my Windows 7 computer fine.

If anyone could lead me to an answer on this I'll buy you a virtual beer! (or a real one if you live close enough)

• Edited by Hero Tech Inc 9 hours 55 minutes ago

The above article may work temporarily, but this problem keeps coming back for me. And it happens to ALL of my network adapters. I own an IT consulting firm and have been doing IT for over 15 years, and this is one of the only things that has stumped me completely. It has to be a bug in Windows, along with something in my environment that makes it keep coming back. I've even reformatted my Win 8.1 computer from scratch, which fixed it for a very short time, then the problem came back. Here's the things I've thought of or taken note of thus far about my environment that may be a trigger:

- I've uninistalled anti-virus software just in case
- I have VMware Workstation installed, which creates virtual interfaces
- I use a FortiClient VPN, which also creates virtual interfaces (IPSec & SSL)
- I use a USB 3.0 docking station while I'm at the office, which has GB ethernet built in

In addition to the problem with being unable to manage IP settings via GUI, I've had continual problems with my FortiClient VPN software and my hunch is that these two symptoms are related because the same exact FortiClient (and configuration) works on my Windows 7 computer fine.

If anyone could lead me to an answer on this I'll buy you a virtual beer! (or a real one if you live close enough)

• Edited by Hero Tech Inc Wednesday, June 03, 2015 9:29 PM

@Hero Tech Inc,

Does your USB Docking Station use the DisplayLink Manager software/driver by chance?  I just updated to the latest version (7.8.63104.0) and right afterwards, I started running into this issue.