Yes, there are already a number of reports on this in the feedback app. I suggest you Me Too them.
Mystere I am not sure what you want. after 6 hours with the update I have no ethernet connection.
are there any fixes or work arounds?
According to someone on TechNet, the situation is intentional in order to change where the configuration information is maintained.
The suggestion is, if you need to change the settings, you use netsh or Powershell. The issue should go away on or before the RTM.
This is the answer by Jeffrey Tippet here: https://social.technet.microsoft.com...ew2014Feedback
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.
One of the most common reasons for modifying LAN settings is the need/desire to use DNS other than default from ISP for Ipv4. If you want to change your DNS, for now do it through your router settings. The lan will still use 192.168.1.1 (most common) to point to router, but router will use what you set DNS primary/secondary.
I might change my Network settings if the network is being recognized a Unknown. On occasion, using a known good IP address helps the network see that network adapter.
But I was wondering if the work Microsoft seems to be doing on the Networking might be related to the option to Download updates from another PC on your own system, or one on the internet...? I would think anyone with a computer being used as a seed would have to be notified prior to such an action.
I do have a workaround that partially works (for awhile).
Click on the icon for your router/Internet/network in the System Tray. Then click on your Wi-Fi (router)>click Disconnect, wait a few seconds and then click on Connect. Be sure that Auto-Connect is selected, although I don't think it works. There are too many folks who have complained that it doesn't Auto-Connect for them.
And, this is the main reason I will not let Windows 10 replace my Windows 8.1.