There are users out there who do not integrate anything. They just install the updates. And if the user installs the updates with the "BF" method when using the install.cmd the updates in the SatisfyWU folder are needed to install it with the "normal" method in order to satisfy WU. The 7zip files will be updated when all the hotfixes from Microsoft are available this week.
@Mcrip, first...thank u, for your hard work. i have a question, will there be office 2010 updates soon?
Sorry, but I don't understand why even on a live system they'll need to install KB2679255 twice, or KB2556532 (superseeded by KB2679255, also found in the satisfyWU folder) only for the sake of installing. Also, have a last question: DisableCoreparkingWin7.exe is a script of yours to install those two AMD-system related updates? Thank you for your hard work once again
All of these updates are needed to satisfy WU on my computers. And I have several comps... DisableCoreparkingWin7.exe does not install any updates or hotfixes. It only sets the correct registry settings. There are more registry settings than described here in this forum.
McRip sorry but you do know you dont have to create a new post for each hotfix? Just use the same post for all 5
I think it's because this thread updates very rapidly, and his post will get buried quickly. I wish this forum had a setting for how many post to display per page! (OK just found that it does, in my profile settings! Oops!)
Does this really not happen for the rest of you? Please look at your Event Viewers. I always receive these warnings after an installation of a hotfix integrated image. Each time that I make a new image, I start with fresh files from an untouched MSDN ISO. I used KUC (v.0.8.005.020) to integrate updates for my last image.
Hi Forever, Yep, I just looked at the event viewer after reading your post, and there are over 80 warning events for the .NET Runtime Optimization Service (2.0.50727.5723) - Version or flavor did not match with repository: ehiwmp Another exact entry has BDATunePIA at the end of the report. I have no idea what is causing this, and the image I'm using is fully up to date. Any of our resident gurus have any ideas?