Windows 10: How Windows 10’s “Builds” Are Different From Service Packs

More: http://www.howtogeek.com/235953/how-...service-packs/

 

Interesting .. thanks for posting.
Jeff

:)

 

Touchscreen making some websites unusable

I am seeing it on:

Windows 7 Pro Version 6.1 Build 7601: Service Pack 1

Windows 10 Pro Version 1607 OS Build 14393.1066

Windows 10 Pro Version 1703 OS Build 15063.138

I have Windows 8.1 machines experiencing the exact same problem but I don't have access to those at this time to get you exact versions and build #s.

 

Windows 10 1709 64bit, windows image restore to a new drive fails, error 0x80042302

Thanks for the link. That is good to know. Anyway rb1012 suggested an easier way, just going to command prompt after booting from the installation media.

You can see the display below from 2 ISO's one downloaded on 10/17/2017 and the second downloaded today 02/10/2018. The second one is bigger probably because it has updates to bring the installed windows to service pack build 125, but both packages show
a service pack build 15. There should not be any difference in the actual installer. 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
backup image file.

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
with format option checked.

Hopefully they will not break it again on the next build after 214

Details for image : K:\sources\install.esd
Index : 1

Name : Windows 10 S

Description : Windows 10 S

Size : 15,748,508,043 bytes

WIM Bootable : No

Architecture : x64

Hal : <undefined>

Version : 10.0.16299

ServicePack Build : 15

ServicePack Level : 0

Edition : Cloud

Installation : Client

ProductType : WinNT

ProductSuite : Terminal Server

System Root : WINDOWS

Directories : 20444

Files : 101280

Created : 9/29/2017 - 6:49:29 AM

Modified : 10/17/2017 - 8:51:36 PM

Languages :

en-US (Default)

The operation completed successfully.

Details for image : K:\sources\install.esd
Index : 1

Name : Windows 10 S

Description : Windows 10 S

Size : 16,024,379,911 bytes

WIM Bootable : No

Architecture : x64

Hal : <undefined>

Version : 10.0.16299

ServicePack Build : 15

ServicePack Level : 0

Edition : Cloud

Installation : Client

ProductType : WinNT

ProductSuite : Terminal Server

System Root : WINDOWS

Directories : 21469

Files : 107844

Created : 9/29/2017 - 6:49:29 AM

Modified : 2/10/2018 - 2:58:08 PM

Languages :

en-US (Default)
The operation completed successfully.

 

Thanks for the interesting post. *Smile

 

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.