check this registry path to be sure: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion BuildLabEx Value it should say somthing like: 9600.16404.amd64fre.winblue_gdr.130914-1623
Still hunting for the x86 versions of the rollup. Might have to wait for GA. I don't think OEMs typically even use x86 OS versions anymore I guess. But in case one of you guys has access...
Same, 408 and 2141 in registry. I don't think we've to worry... It's bigger number than theirs ( 404 & 1623 in reg ). On the other hand, they might should
"hardware abstract layer" in msinfo32 shows the 408, reg is 404. I never noticed a difference between the two before. Cool lol even old dogs learn new tricks
look closer, where is the same? all of the planet will have 9600.16404.amd64fre.winblue_gdr.130914-2141 btw, 1623 is just an example
Go to C:\Windows\WinSxS and look for a directory that starts with amd64_microsoft-windows-os-kernel_. The full name of the directory will contain the file version of the kernel file, and that is the version that is reported as the Windows version. In my case, I have two of these directories: Code: amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.16384_none_5ceec1ab881a18dc (RTM) amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.16404_none_5d4542f187d9367b (GA Rollup A) If your version is reported as 16408, I'll bet that you'll have another directory with 16408 in the name, and that most likely came from some other hotfix that you had installed that contained a 16408 build of the kernel. As for the version reported for the HAL (hardware abstraction layer), that is the file version of hal.dll (amd64_microsoft-windows-hal_). Both the kernel exe and HAL are part of the overall kernel, responsible for different things (the former is the core, while the latter sits between that and the chipset). And as I said earlier, the ONLY thing signified by the Windows version is the file version of the kernel exe file. It's not important, and it's not something to get excited over. It's just the reported version of one single file. Nothing more. Edit: GA Rollup A contains a 16408 HAL and a 16404 ntoskrnl. If you have a 16408 ntoskrnl, it didn't come from GA Rollup A!
I also think those 5 hotfixes are no longer needed. Probably StartComponentCleanup (or cleanmgr.exe, Disk Cleanup) won't make a decision to uninstall when the hotfixes have files with exactly the same version number.
yeah just a test system, the leaked update is all that is on that machine except defender stuff. ntoskrnl is 404. you missed my edit before your post though heh.
Wait, your ntoskrnl is 404 and yet your OS version is reported as 408? HAL being reported as 408 is expected, but the OS version should be 404 if your ntoskrnl is 404. And I just looked at your screenshot, and noticed that you took a screenshot of kernel32, not windows-os-kernel, which is another source of confusion. The latter (ntoskrnl) is the actual kernel. kernel32 is really a misnomer because it's a userland DLL (it's more like a bridge between userland processes and the kernel).
Hmm, I installed all three updates, but it did not remove the secure boot watermark. View attachment 24463
I installed the three updates (Windows8.1-KB2883200-x64, Windows8.1-KB2894029-x64 and Windows8.1-KB2894179-x64) this morning and my registry shows: BuildLab - 9600.winblue_gdr.130913-2141 BuildLabEx - 9600.16404.amd64fre.winblue_gdr.130913-2141 System information reports: Hardware Abstraction LayerVersion = "6.3.9600.16408" ntoskrnl version: 6.3.9600.16404
Guys, would you tell me please, can I integrate licked hot-fixes ( KB2894179, KB2883200, and KB2894029 ) in Windows 8.1 DVD using Windows Download Integrator v.3.5 ?