Most of the time the DHCP is fine, but on occasion I need to use a static IP. Suddenly after build 10049 loaded, I cannot.
Ideas?
Yes I am logged in as administrator. btw, it was fine in build 10041.
I think I remember having read in a thread on the official forums, that if you uninstall the network device through Device Manager, and let Windows install it again by refreshing the list, the bug is gone. I still have to test it myself, but just my 2 cents if you feel like giving it a shot
No, deleting Network adapters doesn't help, just tried it. Answer is:
This is a known issue in 10049. The button is greyed out, and there's no easy way to get it back. This is NOT how the product will ship; we'll bring the button back as soon as possible.
If you need to set static IP address on build 10049, you can use the New-NetIPAddress cmdlet, or the netsh utility.
I'm sorry for the trouble this causes you. We don't mess with things without a good reason. In this case, we re-worked some plumbing so that installing network drivers is more reliable, and can be done offline into a VHD. Unfortunately that means we had to temporarily disable the IPv4 and IPv6 properties GUIs, since they weren't ready to work in the new engine yet.
Posted by Jeffrey Tippet here: https://social.technet.microsoft.com...ew2014Feedback
Quote