New
#150
At least sfc /scannow goes thru without apparent errors. I say "Apparent" because last time when it did report errors unable to fix, there was nothing wrong in the .log file that suggest there was something wrong.
I hope we will be able to create an ISO. It could be months before the 16xxx builds appear on the slow ring
Marty, I'm sure you know about this, but here's the link. Worked for me and lots of others. Here's a link to one member's post.
UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 61 - Windows 10 Installation Upgrade Tutorials
Yes I have used it. But nobody has claimed to have created an ISO from the upgrade to 16170 - or did I miss it? I certainly saw no esd in the ~BT folder or esd'sin the software distribution folder. If I missed it I'll catch it next time. Just finishing up with iupgrading to 16170 on my Hyper-V VM. This took numerous retries.
Marty, the update came as an express update using UUP. Follow the tutorial and you get your ISO. ;-)
UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files
The update files are located in:
Before Update Process:
C:\Windows\SoftwareDistribution\Download\15c201be9020c9e30a33aa5a9dca501c
After Update Process:
C:\Windows.old\WINDOWS\SoftwareDistribution\Download\15c201be9020c9e30a33aa5a9dca501c