I really wouldn't know why a simple cmd with it's own standalone exe's, etcetc...would not work on any build.
I think that the HP Compaq Tc4400 that I'm using to test Windows 10 is not going to be supported any longer because Microsoft doesn't fix the Intel driver bug and every time I switch to Basic Driver it comes back to the buggy one.
v27 (which was used for quite a few months) also works, so what old, no longer supported, version did you use?
I have 14965 enterprise x86 en-US installed this afternoon, to fetch the full esd temp url, if it gets offered it will be later tonight or early tomorrow.
I have a Tower Desktop PC. I had to buy new Hardware to be able to install any Build 14986 and newer. Seems between 14971 and 14986 MSFT dropped support for my Hardware.
With the basic driver operates the build and video It will be for only having 32mb of video ram I left it with the basic drivers and it works perfect
What happened to turning on Fast Ring looks like the option is removed in 15019?............. Did a search didnt read whole thread cause the others were mindless..........
It's true that it works but it is laggy... I have a Dell Latitude D630 with Insider Builds and 0 problems so I'll think what I'm going to do :/
You dont have to use windows update you justneed to learn how to work around it by blocking driving installs and disabling windows update in services.msc. Search HowtoGeek how to prevent windows from updating specific drivers (sorry dont have post count to post links here LOL ) use gpedit.msc to block certain drivers with device manager hardware ids and gpedit that way you can leave windows update on and it wont overwrite your drivers you dont want it to change.