New
#170
At this point, I have had very few issues with UUP, and have stopped using the registry hack for getting .ESD files anymore. The one problem I had on this update on the main computer (host machine for my VMs) is that it got stick trying to boot, looking for a disk in the BDRW I have installed during POST and hung there. It had happened once before to me, a couple of builds ago, but other than that it works perfectly fine.
I have not found a real solution to this issue, so I may just disconnect the drive before the next update to see if it works better or not.
Update came down quickly and smoothly via UUP on my Surface Pro 3. Running well so far.
First attempt to update on my Surface Pro 2 hung at "Working on updates 6%". Clearing the update cache and then redownloading the new build seems to have gotten past that hurdle though. Glad to see that we're likely in the home stretch for RS2.
ok finally had to
https://answers.microsoft.com/en-us/...=1487959098001
at the command prompt
reg delete HKEY_LOCAL_MACHINE\system\setup\upgrade\nsimigrationroot /f
netsh int ipv6 set locality state=disabled
reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a01-9b1a-11d4-9123-0050047759bc}\28 /f
did this and it took care of the home version that was hanging
Is anyone else seeing the difference in Windows Defender?
On the last few builds periodic scanning by Defender was available even when a 3rd party antivirus was in use. Definition updates for Defender were installed through Windows Update. And periodic scanning did occur.
I am running Vipre Pro AV. In this build 15042 a different page (compared with previous builds) opens when the "Turn on Windows Defender Antivirus" button is clicked, but it closes after about 3 seconds. The page is not populated, other than the shield logo.
I found that shutting down Vipre allowed the Window Defender page to open and be populated, and to remain open. After restarting Vipre, the first time I opened the Defender page it opened (and was populated) but closed after a few seconds. Subsequent attempts to open the Defender page result in an un-populated page appearing for about 3 seconds.