New
#350
Yep. from Shawn's the first post:
New Windows Defender dashboard: We are making it easier for you to view and control Windows 10 device security and health features available on your PC or tablet with the availability of a new dashboard coming in the Windows 10 Creators Update. Windows Insiders will get a preview of the new experience beginning today. After upgrading to this build, Insiders will have to restart their PC. After that, they can find the dashboard by searching for “Windows Defender” and clicking on the search result that says “Windows Defender/Trusted Windows Store app”. Remember, the dashboard is a work-in-progress and not fully functional just yet.
Yes, I miss old Security Center, as it is "Security and Maintenance" in control panel addressees 2 different things.
Good to hear.
I am at this very moment doing screenshots of this procedure for a tutorial (Windows 10 - Create customized ISO from existing installation), will write the tut today, add videos later today or tomorrow.
Done a few different scenarios, all working just perfectly. You can make highly customized ISO images for clean, in-place and repair install.
It has one disadvantage compared to ESD to ISO conversion: there's no fast way to capture the install.wim for ISO image. ESD to ISO conversion takes just minutes, whereas using DISM to capture install.wim after UUP upgrade takes on my low end laptop over 40 minutes, with mid end desktop almost half an hour.
At 80% now, started the stopwatch when I executed DISM command:
Other than that, the method is easy and fast (you only need two or three minutes for the commands, excluding the above mentioned waiting for DISM to capture the image).
A clear advantage is that clean installing Windows with ISO this method creates is at least 30% faster because the OOBE phase (setup after last reboot when clean installing) will be skipped as unnecessary.
Kari
When I first attempted to upgrade through WU to 14986 from 14971, the system sat for a while at 0% downloaded and I got tired of waiting for it so I rebooted and tried again. This time the upgrade install failed due to an internal error #. I removed the .bt~ folder on c:\ and then went to c:\windows\software distribution and deleted all files and folders inside that were dated that day (so you know they came from the botched 14986 install attempt.) After those steps I rebooted and tried the upgrade through WU again--this time, being careful not to interrupt it, the WU upgrade install to 14986 from 14971 proceeded without incident. Build is running fine, thankfully.
Offered for whatever it is worth...
Last edited by waltc; 11 Dec 2016 at 11:30.