Verify the “OS Build” number matches the number of the latest stable build provided by Microsoft. You can check the current build of Windows on your device by heading to Settings > System > About. Microsoft will announce a final release date and it will be reported in the press, too. This should be hard to miss if you keep track of Windows releases.
If you want to leave the Insider Preview track when the build of Windows 10 you’re testing becomes stable, keep an eye out for the final, stable version to arrive on your device. Since Microsoft didn’t release any new Insider Preview builds for a short time after, the Insider Preview branch and Current branch were the same–and you could switch to stable without any issues.
When the Anniversary Update was finally released on August 2, 2016, it became part of the stable build–or “Current Branch”. If you’ve been using the Insider Preview, you have the opportunity to leave the Insider Preview program and return to the stable version of Windows 10 when the build you’re testing becomes stable.įor example, let’s say you opted into the Insider Preview program prior to the release of Windows 10’s Anniversary Update. RELATED: Should You Use the Windows 10 Insider Previews? The information in the footnote may explain why Microsoft is forcing updates now.Switch From Insider Preview Builds to a New Stable Build Windows 10's lifecycle is based not on versions but on the user having applied all updates to-date. In the table below you can see a significant change to the support lifecycle policy. With Windows 10 Microsoft has added a new wrinkle to the support lifecycle. The current lifecycle table is added below. Whether it was a service pack in the old days or milestone builds now, the key is that both are classified by Microsoft as creating a different version of Windows.Įach service pack level had (or still has) its own support lifecycle. Insider builds are candidate new versions of Windows released for testing and evaluation every few weeks. There is a significant difference between mainstream Windows and insider Windows in that mainstreamers receive cumulative updates until the next new version of Windows and insiders receive new builds between new versions of Windows. So far only two Windows 10 builds have also been new versions of Windows build 10240 (Windows 10 Gold) and build 10586 (Fall Update).
It may or may not be a new version of Windows. A service pack was a new version of Windows.Ī build is a complete copy of the OS. Only updates not already installed were downloaded. They also contained a roll up of updates released after the last service pack. Service packs contained new features and changes to core files not available before or after as updates. Hopefully they will not break it again on the next build after 214ĭetails for image : K:\sources\install.esd So the problem is not on the 1709 Repair disk used, but the difference is in the actual backup image files obtained with build 16299.192 and below which fail to restore versus the ones obtained with build 16299.214 which do not present the bug during restore
Anyway the 2 resulting install media used to restore the image did not show any difference in behavior, they all fail with old backup image file and all work with the newer There should not be any difference in the actual installer. The second one is bigger probably because it has updates to bring the installed windows to service pack build 125, but both packages showĪ service pack build 15. You can see the display below from 2 ISO's one downloaded on and the second downloaded today. Anyway rb1012 suggested an easier way, just going to command prompt after booting from the installation media.