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

is sets in this build?

Brink said:

It updates to build 17004.1002 (new) vs 17004.1000 (old), but basically just a patch for this release.

----------------------------------------------------------------------------
UPDATE 1/18: Today we have released Windows 10 Insider Preview Build 17074.1002 to Windows Insiders in the Fast ring. This build is the same as the version of Build 17074 released last week with 2 additional fixes. We have fixed the issue causing AMD PCs to become unbootable – which means we have removed the block for AMD PCs we put in place last week. And we also fixed the issue causing certain devices to hang on the boot screen after upgrading if virtualization is enabled in the BIOS.

Almost tempted to put the old Intel DX58SO back together and try one last time with these new fixes :)

geisenhorn said:

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.

slicendice said:

Have you tried to completely disable IPV6 stack in both your router and in Windows?

And disable Chromebox or Chromecast if you have one in network ...

slicendice said:

Have you tried to completely disable IPV6 stack in both your router and in Windows?

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.

AndreTen said:

And disable Chromebox or Chromecast if you have one in network ...

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?

squaleca said:

is sets in this build?

Don't know, but will be interesting to see. Mine is still there.