Incompatible? How you can say it? I made it on x64, and its only compiled CMD script, its architecture independent...
That could be caused by a virus on your computer. In any case, there is something not quite right there!
@George King, no offence to your work. I'm getting this message " Unsupported 16-Bit Application " " This version of D:\Windows6.1-UpdatePack-x64\Update.exe is not compatible with the version of Windows you're running. Check your computer's s ystem information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. " Thanks for your support.
@George King, I've download the file from another location ( hotfile ) and it works fine. Many thanks
Here is a Re-Up of the George Kings Update Packs Ver. 1.14 X86: Part1 Part2 x64: Part1 Part2 Part3 Nitra
Why does everyone thinks that more is better? Having correct updates its what counts, why have 10x kernel update or .net updates when mostly one or two matter for example? I have ~200 hotfixes for x64 and that are all that are all that everyone actualy needs to run "latest code". Im sure if i want to scrap all together i can get over 300, but there is absolutly no reason except having couple for hundred megabytes of used space and couple of hundred aditional registry entrys and couple of thousand aditional files in winsxs.
Thats very true, there are many superceded updates. Some updates may be for completely different issues, but replace the same files with different versions. The 7600.20xxx versions are the all inclusive updates, meaning they also include the fixes for the preceding (superceded) updates. If you think SoLoR is overstating the 10x remark, he isn't. I've seen it most apparent in .NET framework updates, its really quite silly installing each and every version.
yep... also in some cases even same updates are released under different KB number. I think in zukona februar pack there was like 3 or 4 .net updates including SAME .net components, while you can install all of them and they overwrite eachother (and its good for update count), in practice you achive same with installing only one. So ye, more is not neccessery better my goal is to run latest code, with least updates possible. Then you have other things like, for example one update have basic .net components and one extra component, then there is new .net update with only basic ones and sadly you need to install both because of that one extra in older update, even tho rest is 10MB of garbage... but with even updates like that im currently on ~200. Dont get me wrong, i dont care about 10MB and my disks are generaly 90% free. But i just want dont want to have least garbage as possible (thats also the reason why my disks are 90% free).
Somes updates are not compatible with the Windows version that are we running. So there is no point to have ALL the updates. If we don't have a use for them.