They'll Never be "done with it". Given that, Does that mean support for 10240 stops 24 Months after 10586, and then 10586 will stop 24 Months after The AE I'm sure at some point I'll want to say Enough and lock in the features
Practically 10240 will be supported for 5/10 years given the LTSB. Just like XP , which is still supported until 2019 given the Posready 2009 version.
come on with the new build I have tonight band night why don't they start early with pressing the red button
Sorry for the delays, I answered you via PM but I will post here as well in case anyone else was having similar issues. You were right, I thought that ResetBase command had locked in the drivers, it hadn't. So I thought about it and the only other place the re-install routine could have gotten the third party drivers from was the cache of drivers I had exported to a memory card that was inserted when I "Reset" Windows. The upgrade/update procedure usually exports the current drivers to a working folder in the $WINDOWS.~BT folder during the upgrade process and something must be interfering with this. Possible work around may be to disable your antivirus before installing new builds, of course that may not always be convenient so something else that will work is to create a cache of your current third party drivers somewhere that Windows will find them during the installation. What I did this morning to test this was create a folder on my C:\ drive but you could use any drive that will be visible to Windows during the update/upgrade process. I named it Drivers, then opened an elevated command prompt and ran DISM /Online /Export-Driver /Destination:C:\Drivers Of course change the "C" if using another drive. I reset Windows and it worked perfect. Windows automatically reinstalled my cache of drivers from C:\Drivers when I reset Windows and chose the option of removing everything.
14388 not showing up here, 2 possibilities: MS servers suck ? 14390 ready to rollout and 14388 retained