I downloaded ESD for 14931 Pro x64 en-us (sha256 6166d7a2d3d4e64c4ef0c76501a27d351c3a34e347f317e6f7d09372a18c03ab). After using decrypt-esddecrypt.cmd the Decrypted ESD sha256 is ee88ab5ffea711403fb8ccf1ee705a7aaf1595b2435a4afcfe36f5bc3cd716cd. I'm dualbooting Anniversary Update with the 14931 Insider build on another partition H. So I use dism to extract the ESD insider image to the H: partition. While extracting files Windows Defender DETECTS A TROJAN:Win32/Varpes.J!cl on H:\Windows\SysWOW64\dnsapi.dll. Is this a false positive or is really Microsoft releasing a build with a trojan inside? Never happened before with any other build. I did boot inside build 14931 and the Windows Defender from the insider build didn't detect anything though.
I've run defender after 14931 was installed and before 1st reboot. No issues was reported by defender. Just looked into Windows\System32 and found: C:\WINDOWS\system32>dir dns*.dll Volume in drive C is InsiderBuilds Volume Serial Number is 0EFF-14CD Directory of C:\WINDOWS\system32 17-Sep-16 13:39 629,088 dnsapi.dll 17-Sep-16 13:39 132,096 dnscmmc.dll 17-Sep-16 13:39 14,336 dnsext.dll 17-Sep-16 13:39 102,400 dnshc.dll 17-Sep-16 13:39 259,584 dnsrslvr.dll 5 File(s) 1,137,504 bytes 0 Dir(s) 30,081,966,080 bytes free C:\WINDOWS\system32> That is no problem with dnsapi.dll. My system: 14926->14931, en-us, x64 Pro. I have converted Install.esd to ISO as my 2nd notebook haven't received 14931 and thus I've used this ISO on 2nd notebook for 14926->14931. Defender also was run fine. So at least install.esd received by WU contains correct version of dnsapi.dll.
Wow this is the worst build yet, after I log in I just get a black screen, I can open Task manager and run programs but explorer wont run. I found this blog post with updated info But I didn't sign out or switch accounts, I tried restarting and shutting down but I just get a black screen every time, I mean I know we are meant to be testing these builds but come on, at least make it stable enough to load explorer. And yes I did try to run explorer.exe it appears in task manager for a couple of seconds and closes again, I haven't seen anyone else mention this problem so I don't know why it's happening on mine.
Okay, so wait... Are you sure they would release a build that, after a log in, somebody would get a black screen? And a build that Explorer won't run? Are you SURE?
@all, remember that is one build only for insiders then errors, bugs is normal; so NO install on principal machines
Explorer shows some copied folders late (well, they are there - just refresh to see all). E2B USB stick show me 2 drives (other one as usually and other one with "needs format" message), so it is not working properly with this build. Other than those problems, this build has been good. Edge is improved once again too and it has been very stable with this build. Waiting the next build
You need to use Windows Defender from 14393.187 (Anniversary Update). That's why I said you need to dualboot AU and latest Insider Fast Ring in order to see this.
@Jari with reference to E2B USB stick this is not error is one one functionality of Windows 10; so to resolve make this with caution: first backup Registry, after open Regedit search HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\DelegateFolder and search the key {F5FB2C77-OE2F-4A16-A381-3E560C68BC83}right click on it and choose exclude after open TaskManager (Ctrl+Shift+Esc) search for Windows Explorer select it and restart so the second icon disappear
When I updated from the previous build on my PRINCIPAL machine, I had this issue. I just had three black monitors with a cursor. I believe it had something to do with my installed themes. So, I clean installed with my created ISO. The first thing I ALWAYS do after I download from WU is create an ISO. It worked great on a clean install, so I was able to install all my programs, and mods. I then troubleshooted the RS1 themes to get them to work, and as you know I was successful. The only issue I have with this build is the Start Menu reverting to full size (double width) after reboot. It does not remember my custom width. Now I am running build 14931 without any problems.
black screen issue i reported a few threads back.....all u can do is wait and hope its fixed in the next release.
humm I need make justice althoug my information is correct, BUT this source is no me so I make repair now
Done with the same result: defender of 14393.187 system have scanned d:\Winsows\System32 corresponding to 14931 without any issue found with defender definitions of September 26. Maybe old definitions provided the result you've got.