New
#370
I even done the skip ahead registry trick but there’s nothing to skip ahead to :)
Sooo...RIGHT after the system booted with for the first time with build 17074, even though the network configuration is correct (IP/DNS/Default Gateway all correct etc.), even despite that I tried reseting device/Netsh Interface Ip Reset, also router itself just for the heck of it, still windows network problem solver gave the "cant connect to primary dns server" error plus the "firewall may be blocking..." error also for the heck of it tried turing windows defender firewall off, still pinging outside world gave nothing while local network worked splendidly.
Rolled back and right after the boot network worked flawlessly, so yeah, wierd that I was the only one with that problem in this build.