you know, I was thinking about this as well, and was wondering if these 2 additional files brought forth some unintended consequences for someone with the freezing problem, it would be nice if you could just install using the 4 files and see if that fixes it!
So let me get this right, out of the 6 files, the only 2 that does NOT necessarily need to be installed (and that might be causing some problems on peoples PC's) are KB2938439 and KB2937592?
that's why am still not updated the toolkit as the files sent to oem doesn't contain these two updates. so wait for official release.. but so far I don't have issues with the pc using the update 1
KB2939087 is a Preparation Update and needs to be installed before KB2919355. KB2938439 and KB2937592 are "Feature Packs"
This drives me crazy as well. Every time there is a new OS or a big Update like a service pack or something major, people go around whining about how their custom software doesn't work. FFS, why would you expect it to?
if KB2938439 is referring to Tablet PC, why install it on desktop and laptop PC ? and KB2939087 has build 16655. why install it ?
Windows includes Tablet PC components, in taskbar Toolbars->Touch Keyboard. 884905, this is not part of the update, as being not in the main service branch.
Mostly I'm just tired of people complaining that their a/v program or drivers aren't performing flawlessly after those huge updates. I could only speculate at the various reasons that a/v programs get all messed up after large OS updates, but if I had to guess; they're probably not using very good coding practices or following MS's advice in some way. The driver stuff seems obvious... Still, it never seems to stop people from going around 2 seconds after a leaked version of Windows and claiming that the performance isn't up to par or that their drivers are buggy.
Don't mind . Got it working that way ... : Spoiler Code: set algo=SHA1 set updatefolderpath=E:\###.PROGRAMME.###\WIN.8\###.UPDATES.###\Spring.2014.Update set ext=msu for /r "%updatefolderpath%" %%g in (*.%ext%) do ( for /f "tokens=1,2,* delims= " %%a in ('powershell get-filehash "%updatefolderpath%\%%~ng.%ext%" -algorithm %algo%') do ( if not %%b EQU Hash if not %%b EQU ---- echo %%~ng %algo%: %%b ) ) Output: Code: Windows8.1-kb2894853-x64 SHA1: 2CE58DF63311828BEAEB43BDCEC562AC50CE2CF0 windows8.1-kb2919355-x64 SHA1: E6F4DA4D33564419065A7370865FAACF9B40FF72 windows8.1-kb2919442-x64 SHA1: F97D8290D9D75D96F163095C4CB05E1B9F6986E0 Windows8.1-kb2928680-x64 SHA1: 0D9E06A995EB9A2323C9FD10523929038F8838E2 windows8.1-kb2932046-x64 SHA1: 6AEE5FDA6E2A6729D1FBAE6EAC08693ACD70D985 windows8.1-kb2937592-x64 SHA1: 4ABC0A39C9E500C0FBE9C41282169C92315CAFC2 windows8.1-kb2938439-x64 SHA1: 3ED1574369E36B11F37AF41AA3A875A115A3EAC1 windows8.1-kb2939087-x64 SHA1: 89D4949CD698C645C7A6E96A012EECAB44D5C5E1 Indeed a very useful feature .
Murphy is right but don't forget, create a restore point, install update...not happy do a restore, done.
Wouldn't it be far easier to use a tool like md5sum or sha1sum, which have been command-line staples on Unix (and various free ports/versions available for Windows, too) for many, many years? Or HashCheck if you go the GUI route?
Might be ... but i was looking to integrate to my script tool and refuse using 3rd party if it can be done via Powershell .
Code: PS C:\Windows\system32> C:\hash.ps1 At C:\hash.ps1:4 char:8 + for /r "%updatefolderpath%" %%g in (*.%ext%) do ( + ~ Missing opening '(' after keyword 'for'. + CategoryInfo : ParserError: (:) [], ParseException + FullyQualifiedErrorId : MissingOpenParenthesisAfterKeyword