No ESD for new build 14986 download?

Kari said:

Please see this post: Insider Announcing Windows 10 Insider Preview Build 14986 for PC - Page 27 - Windows 10 Forums

So Many Thanks! Quicker than reading entire news thread. Still, good info in thread,though. Update MBAM if you go to the new build 14986!

UPDATE: Made build 14986 ISO using info supplied here and suggestions in "News thread", and installed ISO in VMware Workstation Player 12. (free)
[ Used option 2 in updated ESD to ISO app to make ISO from "install.esd" file obtained after registry hack
(and re-imaging to build 14965, then Selecting "Fast ring", and updating for 6 hours to get Install.esd file.)]
Edge works.
Installed MBAM 3.0 Free, from web.
Edge works. MBAM works.
Installed AVG Protection Free from previously downloaded Setup file AVG 1606 (v.1.3.29.5)
[newest version is 1.3.31.5 (See no reason that wouldn't work,too.)]
AVG works.
EDGE will not do a search, now.
Installed Chrome from previously downloaded Setup file.
Chrome works flawlessly.

Thanks , again Kari!
And thanks, fdegrove, for pointing me back to the other pages in the "News thread"!

Update to Update:
AVG install destroyed Network! Uninstalled it; still no Network!
Re-imaged to MBAM only in case of conflict. Network OK, but Blue Screen after starting uTorrent!

Per MS: Remember to change those two registry settings back to '1' to re-enable the new updating method. I specifically inquired about that in the Win 10 developer forums @ MS and they said while it works now if your having issues downloading the 14986 update, leaving the registry settings to 0 or disabled will cause problems in the near future with respect to updates.

I too prefer to have the entire 'esd' file to create an ISO....which I did this time....but I don't know if it's just MS being overly cautious OR if it really will mess things up.

Obviously it makes sense to provide only the files which need updating due to download time/disk space, however, I prefer the entire ball of wax approach

Tim

N9NU said:

Per MS:

Quote from another thread:

Kari said:

There's nothing to worry, that warning first seen on Microsoft Community being somewhat pointless. Both EnableUUPScan and SupportsUUP DWORD values will be reset to default 1 (UUP enabled, no install.esd) when upgrading, and need to be manually changed to 0 after the upgrade if you prefer ESD file also in future build upgrades after 14986 (will work as long as Microsoft offers the ESD option).

Winuser said:

I just checked my registry and under HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>Windows>CurrentVersion>WindowsUpdate>Orchestrator
I don't have the DWord EnableUUPScan. Should I add it or leave it as it is?

EnableUUPScan is removed from registry as unnecessary after a reboot when it and SupportsUUP are disabled (value 0). When UUP is disabled, scanning for existing installation to know what to upgrade is not necessary, upgrade does not need EnableUUPScan. A good example how Windows really can take care of registry all by itself.

Next upgrade will reset both values, setting SupportsUUP to enabled (value 1) and recreating EnableUUPScan setting it to enabled (1).

Kari