Announcing Windows 10 Insider Preview Slow Build 17074.1002 - Jan. 11 Insider

Edwin said:

I'm good at beatin stuff up! I could lend my talents out for a poultry price!

Poultry price - as in ”Winner, winner, chicken dinner”?

johngalt said:

Poultry price - as in ”Winner, winner, chicken dinner”?

Beat me to it!

Edwin said:

This Build have the new Fonts page in Settings?

Not yet enabled, but the next one might.

Edwin said:

I'm good at beatin stuff up! I could lend my talents out for a poultry price!

No way I'd expect a "paltry" price, Edwin. You should get at least a decent wage for that type of effort! :) No chicken feed for you!

geisenhorn said:

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.

You're probably not the only one, Geisenhorn. There're a few gazillion Insiders that have never heard of TF out there. Just sayin' ...

geisenhorn said:

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.

Well, you have one problem that seems unique, but many people have a vast number of ‘unique’ problems in this build. Other people are having no problems with it, so go figure. Strange array of things with the build.