Same here. But you can use regedit to change settings. Regedit Path: HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\ExperimentalFeatures Copy this code to Notepad and save as .reg file. Run the reg file, value 0 is disable, 1 is enable. Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\ExperimentalFeatures] "VP9VideoFormat"=dword:00000001 "ExperimentalJS"=dword:00000001 "EnableServiceWorker"=dword:00000001 "EnableStandardFullscreenAPI"=dword:00000001 "WebAuthentication"=dword:00000001 "EnableIndividualTransforms"=dword:00000001 "EnableMasking"=dword:00000001 "EnableAngleWebGL"=dword:00000001 "EnableVariableFonts"=dword:00000001
Just an update from the 17017 build thread where I would lose my GPU's when I tried to update the NV drivers. Updated to this this 17025 build and had the exact same problem but now found that I can install the Nvidia driver in safe mode only, where before the installer would fail and my GPU's would disappear from task manager and having warning triangles in device manager requiring me to roll back builds. All seems good now though and have 388.00 installed.
Installed on the HP20 Pavilion without any problem! Now to install on a Machine with DFI Lanparty Mainboard, I got a problem, Error is Kmode_Exception_Not_Handled and a point for what failed: nvlddmkm.sys, which seems to be a Nvidia Driver problem. I got that error while using WU for to upgrade to this new build. I also had several times a GSOD (Green-Screen-of-Death) before with build 70017, the machine suddenly restarted, or froze! I'll now download the lasted driver from Nvidia for the Geforce GT640 which should be 388.00 for w10 64bit. Let see that will solve that problem?!
Downloaded the new driver, and within extracting, got the next error, this time for dxgkrnl.sys, which seems to DirectX related, means" same graphics problem!! Let see the install of that new driver will solve that problem too?!
Any idea what the Reg key for "Enable extension developer features (this might put your device at risk)" is ? It's Ok, I found it: Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\Extensions] "EnableExtensionDevelopment"=dword:00000001
I don't know what to do anymore. I've been stuck on 16299 since they released 17017 and all I can do is download the build, install and after the first reboot it hangs at the Windows boot screen logo with no spinning dots, nothing happens. I left the computer on for 3 hours and nothing. had to manually shut down. I recently found how to make an ISO of these new builds and tried to install the newest and nope same result. I'm not sure what's going on, I've been installing insider builds since Oct 2014 and this has never happened to me. Anyone know what I can do?
don't have none. Only defender. I installed previous builds and they work fine it's just 17017 and 17025 installation that refuse to get past the windows logo after the first reboot.
My hardware exceeds the recommended requirements for Windows 10. Only thing is my motherboard doesn't support uefi, it's on legacy. Do you think that's the problem?
that counts as a HW limitation....have u tried your your computer vendor message boards or forums and see if anyone else is reporting the same issue.
I have, and found nothing relevant. My computer is a Dell XPS Studio 9100 with few modifications like the GPU and RAM. The processor is an i7 too.
@Harry t: have you try to press just the Reset Bottom if no spinning dots showed up? If you have never done that, just try it! I use at the moment an older DFI LanParty MB because my MB has problems and is for to repair already, on that DFI MB I have the similar problem that the spinning dots not showing, I solve that with just press the Reset Bottom of the Case and at the restart, all went well!
Oh, forget to mention and asking: Have you try to run the computer in Debug Mode? Try that too! It's possible that a driver (special from Intel) is the culprit! You may have to start the Debug Mode from a Windows 10 DVD or USB Flash drive, under Advanced!