it certainly does not since it will be a standard update with not that many modifications. I'm talkin' about the one that will show this coming Tuesday. Anything else concerning Threshold (?) or at least W9 will have new kernel
I believe that we shall only see a new kernel, with a new os ie, Threshold, Win 9, etc. It doesn't make sense for MS to develop a new kernel for an update.
This is outright false and the hotfix numbers show this clearly. 8.1 RTM: 6.3.9600.16384 8.1 Update 1: 6.3.9600.17031
Will there be an Official 8.1 Update 2 ISO? I have an opportunity to reformat an overdue machine, but I would like to put the latest version of Windows 8.1 on it. I know Windows 8.1 Update 2 is coming out this Tuesday, but with the recent announcement that its going to be small and silently rolled out through Windows Update, I wonder if there will be an official refresh ISO offered by Microsoft? If there is going to be one, I will wait until that shows up. If not, I can reformat now. Any info is appreciated, thank you.
The usual version confusion . On my system /Get-CurrentVersion will show 17031 whereas the BuildLabEx shows 17085.
even if there is no such new iso, which I currently doubt to appear, you can install the version which is shown "somewhere" and wait until any update arrives. Where is your problem?
That is a good statement that needs little explanations. How do you know about that? Speculating based on the August Update perhaps creates room for more information about Threshold all rather Windows 9 is refreshing. But, it is not usually the correct thing.
This silent roll-out is the basic reason why I think there will be no ISO release, at least, not for the main time.
So far only the 'Service Pack' string changed . MS also avoided to rise the build number with Update 1 .
they will do a iso release or someone will build one with the update inside i will never upgrade it causes to many bugs i do fresh installs only
Kernel Version = foundation revamp. Build Branch = major updates. Build Strings = minor fixes. Pretty easy to understand.
[rant] Where does LLStarks find the balls to make claims without any basic understanding of the topic at hand? Every single time the kernel is updated, for whatever reason, it gets a new build number. This happens multiple times per year. Bug fix in that part of the OS? New build number. Security patch in that part of the OS? New build number. I have no bloody idea why so many people on this forum (at least you're in good company) are so fracking obsessed with that bloody build number. It's the build number of just one file. Just one file out of the thousands that comprise Windows. And build numbers are no indication of the degree of change. If you're sufficiently intrepid, you can manually update just ntoskrnl.exe and get a pretty new build number that is reported for the entire OS while leaving every single other file at RTM. People need to stop obsessing over that bloody build number. It's more cosmetic than substantive, and it means next to nothing. [/rant] Now, if the first or second field (e.g., 6.4) or maybe even the third field (e.g., 9601) is updated, there might be something to talk about. But the fourth field is noise. And with the exceptions of Vista and Windows 7, Microsoft does not touch the third field (for the record, encoding the SP level in the lower 4 bits of the third field in Vista/7 was pretty damn stupid, and I'm happy that they abandoned that practice).
Actually the Kernel only gets updated once for a new version of windows after that they work off the build branches unless its a refresh like 8.1 which only really included a very small kernel update and a WDDM update with very minor UI changes which covers the key points in the foundation.
You are basically right except when it came to Win8.1 Update1, the delta(QFE code, minor build no., or what you described as "4th field") was bumped to 17031 and became the image base version, it was taken as a RTM and OEM's produced their machines with this new image, and MSDN also released new set of ISO's.