hello steven4554, installing your pack Win8.1-Update-x64.exe, the string is always 9600.17031, it should be 17042? Is this normal? thanks
I only changed the version number to 17042, cause the latest pack I created contains KB2941455 hotfix rollup.
Highest Win7 hotfix version is 6.1.7601.22596 so there is actual Windows 7 7601.22596 build somewhere and MS is keeping it from us?
I am only interested in build nos.>9622, but rumor was that MS moved the whole team to Area51, anyone leaking infos would be sent to Vulcan and have a life with Spock.
KB2925384-v4 contains build 9600.20521 That's even higher than 9600.17042 Abbodi's point is that hotfixes containing individual components with higher build #'s have nothing to do with the Windows build number. That is determined by the build # of ntoskrnl.exe and it stands at .17031 (Of course a hotfix containing a newer ntoskrnl.exe could change that though.) Build # .17042 should just be forgotten about- it means nothing to the Windows build #.
Yes, I'm sure. Look in the WinSxS folder and you'll see many version numbers for different components that have been updated. KB2941455 does contain components that are .17042, but that's just one of the many version numbers found in newer updates and in the WinSxS folder (if update was installed). The majority of the components in KB2919355 (main Spring Update) are of version .17031, but there are many other version numbers also in that update: .16459, .16503, .16484, .17019, .16517 & others. KB2935092 contains .17035. As mentioned earlier, KB2925384-v4 contains .20521... Those are just the build #'s of the individual components contained in those updates. That doesn't imply at all that there'll be a newer build of Windows (ntoskrnl.exe) or of the Spring Update.
I'm on Windows Vista and none of this stuff is working for me, in fact now their is smoke coming out of my computer, did I do something wrong?
People get too hung up on build numbers anyway. The only reason they're important is so we know when files have been recompiled. Recompiling doesn't make something better. If you never change the source code, it's the same thing, just with a different signature. Found that out the annoying way by trying to bundle pre-ga and post-ga builds on the same install.wim. They just re-compiled most of that stuff and didn't change a thing, but it was enough to change the file contents because of the new sigs.
it's happening the same thing to me very often, on many different computers. The install order was followed and I rebooted when request, no problem except for this.