Windows 10: How Windows 10’s “Builds” Are Different From Service Packs
How Windows 10’s “Builds” Are Different From Service Packs
If you’re a long-time Windows user, you’re probably familiar with service packs. But Microsoft seems done with service packs. Windows 10’s first big update — the “November update” — is a “build” rather than a service pack. Windows 10’s future big updates will be builds, too.
Microsoft actually gave up on service packs years ago. The last service pack released for a consumer version of Windows was Windows 7 Service Pack 1 back in 2011. Windows 8 never received service packs — instead, Microsoft release. (Who comes up with these names?)
Interesting .. thanks for posting.
Thanks for the interesting post.
Service packs contained new features and changes to core files not available before or after as updates. They also contained a roll up of updates released after the last service pack. Only updates not already installed were downloaded. A service pack was a new version of Windows.
A build is a complete copy of the OS. It may or may not be a new version 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).
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. Insider builds are candidate new versions of Windows released for testing and evaluation every few weeks.
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.
Each service pack level had (or still has) its own support lifecycle. The current lifecycle table is added below.
With Windows 10 Microsoft has added a new wrinkle to the support lifecycle. In the table below you can see a significant change to the support lifecycle policy. Windows 10's lifecycle is based not on versions but on the user having applied all updates to-date. Please read the **footnote carefully. The information in the footnote may explain why Microsoft is forcing updates now.
Couple of notes:
--Microsoft did this one time before when they released Windows 8.1. Windows 8.0 and Windows 8.1 are completely different builds and are unrelated to each other, just like the Windows 10 builds.
--Until Microsoft completely revamps the upgrade process, this will be a bad way to do updates. As in any upgrade, the upgrade process sucks. Some things work after; others do not. We saw that with the 10586 upgrade in November. Some settings made it; some didn't. Some programs worked fine afterwards; others didn't. Upgrading from one build to another uses the EXACT same mechanism that is used to upgrade from Windows 7 to Windows 8, which we all know is a troublesome process.
Hey guys! First post for me. :) Been taking up the problem of system and service host: local service eating all the ram. So I've been clicking some stuffs at the settings when suddenly I solved my problem unexpectedly! So here's how you do it. :)
Hello guys I've had this issue that has really been getting on my nerves for the past couple of weeks now ever since upgrading to windows 10 from windows 7. For some odd reason at random times this Service Host: Local Service...
I heard around October is when they'll release a major update for 10 but there wouldn't be any service packs
No Service Packs For Windows 10; Support ends 2025 | www.infopackets.com
Hello everyone, I'm new member here and I hope to be a good member. :)
I need to the list of all language packs of Windows 10. And I wish to know that is this version of Microsoft Windows contains Kurdish language pack?