No access to Internet Protocol (v4 or v6) in 10049


anyone else notice when looking @ properties of network adapter
properties button disabled both ip v4 , v6? haven't
tried netsh yet, how 1 go changing these settings , is
change temporary or permanent?


paul adare - fim cm mvp
hope that's not ui -- proper term "jet database", accessed
through "jet engine". fitting name, considering sucks and
blows. -- felix exchange's mailbox format


this known issue in 10049.  button greyed out, , there's no easy way back.  not how product ship; we'll bring button possible.

if need set static ip address on build 10049, can use new-netipaddress cmdlet, or netsh utility.

i'm sorry trouble causes you.  don't mess things without reason.  in case, re-worked plumbing installing network drivers more reliable, , can done offline vhd.  unfortunately means had temporarily disable ipv4 , ipv6 properties guis, since weren't ready work in new engine yet.



Windows 10 Insider Preview  >  Windows 10 Insider Preview Feedback



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...