New
#420
is sets in this build?
Build didnt change it so it stayed private as always, I srsly failed to find what this build change to cause the issue, I even checked the DHCP and DNS client windows services whether they were working, but I already knew it since the net config was correct, but just for the heck of it checked and obviously the were.
Last edited by geisenhorn; 19 Jan 2018 at 04:57. Reason: typo
On the router it was disabled by default, so I actually tried enabling it with no result, but I didnt try it as You suggest, the other way around, i.e. disabled on both devices, so who knows, maybe it could be the solutions, but not sure if worth reupgrading just to check it ^^.
Just gonna stay with the current, no sound in Firefox build.
Just few hours before upgrading to 170704 I replugged and configured the Chromecast after some weeks xD.
So now there are two possible casuses, althouth while Chromecast? I am aware of the recent patched issue with the mDNS flood after long hibernation, but it coudnt be it since ALL other devices had zero problems, and it simply woudnt be in any way connected to this build, since after downgrade to 17063 DNS was insta working correctly.
Good morning/afternoon/evening, fellow Insiders.
Booted up to a full Start screen is a good sign to me. Edge is kind of iffy at first, but seems to run smoothly after awhile. Had it freeze on me. Closed it out via TM, reopened, and all is well after that so far. No other problems that I can see. Network remained private.
@CountMike > No activation problem this time?
Don't know, but will be interesting to see. Mine is still there.