It's from the windows.bt folder in windows.old ... I took the esd and dropped on abbodi's decrypter and it generated an iso with this name "14390.0.160712-1452.RS1_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US" The decrypter had an alert that it was already decrypted. I'll try installing it in a vm later on.
I don't know if the next bug is nvidia related or a WINDOWS problem, i don't have the resources to do a more extensive testing, so, if anybody here can help to test this and share his results i will apreciate a lot: Pease, if you have an AMD card or just the IGP then test too to know if this problem happen with other GPU brands. BUG DESCRIPTION: On Windows 10 (only x64 tested), even on this 14390 build, when you have Mozilla firefox open and Maximized and the windows taskbar is configured to hide automaticly, if you have more than one display connected and the main monitor is turned off (manually or automated procedure), when you turn on again and move the mouse pointer to the taskbar screen border it will not appear on top of the other onscreen objects (explorer windows or programs)as expected, even if you resize the firefox window to a non maximized state, so you can't access to them, you must click on any viewable taskbar area to bring it over all objects or you must invoke by using the WINDOWS key, the problem solves temporally restarting the explorer.exe process however it will happen again if you maximize firefox and turn off monitor again. ON MY TESTS THIS BUG IS REPRODUCIBLE ONLY ON THE NEXT SCENARY: 1- Have 2 or more displays connected to the system on the same video adapter. 2- The main screen must be on a lower resolution that the secondary ones (as example, main @1080p, secondary @2160p) 3- All secondary screens must be inactive (power off), before OS boot is recomended but not mandatory. 4- Open firefox and maximize the window. 5- Turn off the main screen or wait that system do automaticly. 6- turn on again the main screen after a few seconds and try to access to the taskbar moving the mouse to the respective screen border. NOTE: -The bug doesn't happen when i have the screens on different adapters (main on Nvidia card and secondary on IGP or vice versa) -This bug is already reported on insider feedback time ago, however only up to this day i found the right way to reproduce it. My Test system: CPU: Intel i5 3570k OC @ 4.2, Cooling: Cooler Master Seidon 120V, Mainboard: AsRock Z77 Extreme 4 BIOS 2.90, Memory: 16GB Corsair Vengance LP (CML8GX3M2A1600C9) (4x4) OC @ 1866, Video: GIGABYTE GTX 970 Gaming G1 4GB rev 1.0 (Hynx) OC Core: 1469 - Mem: 1813 (7250) BIOS F13 (84.04.31.00.B3, modded to fix TDR), Sound: Onboard Realtek ALC898, Monitor: Dell U2414H (1920x1080@60hz), Sony TV XBR-49X837C (3840x2160@60hz chroma 4:4:4) Firmware PKG3.395.0105COB, Keyboard: Corsair Raptor K30, Mouse: UtechSmart Venus 16400 DPI MMO Gaming, HDD: 3TB HGST, 1TB Seagate Barracuda, 500GB WD, 500GB SAMSUNG, 320GB SAMSUNG, 320GB Hitachi, SSD: 256GB Crucial MX100, Case: ENERMAX COENUS GUNMETAL GREY, PSU: OCZ ModXStream Pro 600W, OS: W 10 Pro x64 IP RS1 14385
As far as nobody help to test this i don't have a real evidence about what's the root of this, already posted on NV forums and fill a NV feedback form, the same way that is reported on insider feedback each time that a new build comes and check if the bug still happen.
Got it (This installation you see in the screenshots is on a VMware, the KMS activation was just a "not sure if it will work, but I dont care anyways since its a VM" but it worked?! The main question is still, using this iso won't bring me trouble such as being a insider etc?! More like, is it "RTM" and useable on a daily base?
Well as this build was very near final thought Kaspersky might have got their program to work with it...h'mm but on install gets to the last 5 secs and hangs, so cancelled after 5mins wait.