none
Windows Update keeps failing to install 4 recommended KB;s

    Question

  • I have tried 6 times to get these updates to install: KB2515325,KB2522422,KB2492386,KB982018. every time Windows Update says it failed to install them. 2 other Updates KB2310138 and KB2467173 installed succesfully. How do i install/stop these updates as everytime i reboot i get asked to install them again.

    My System specs.

    Windows 7 Ultimate

    Q9650 cpu

    2x 500Gb HDD's (SATA-AHCI)

    Powercolor 4870 1GB

    8Gb DDR2 1066

    cheers

     


    Who cares who wins
    Wednesday, April 27, 2011 12:45 PM

Answers

  • KB2492386

    KB2515325

    KB2522422

    KB982018

     

    I installed them 1 by 1 in the above order and it worked.  The first one is the only one that didn't make me reboot.  I've found that KB982018 might be the culprit and you can install the other 3 in one try, then do KB982018 last.

     

    I've read trying to download manually, but I didn't try that either.  I just unchecked stuff off from windows update.

    • Proposed as answer by pSimonh Thursday, April 28, 2011 8:02 AM
    • Marked as answer by linuts01 Thursday, April 28, 2011 10:42 AM
    Thursday, April 28, 2011 4:10 AM

All replies

  • Hello,

    proceed like that:

    • Download them and try to install them manually
    • Disable all security softwares and try again
    • run chkdsk /r /f and sfc /scannow
    • Download and install the System Update Readiness tool: http://support.microsoft.com/kb/947821
    • Reset Windows Update Components

    If this does not solve your problem, perform a repair install of your OS.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Wednesday, April 27, 2011 2:16 PM
  • I have the same problem.  I tried your suggestion but am unable to run chkdsk because I do not have the proper "authority"....in DOS
    Wednesday, April 27, 2011 4:31 PM
  • I have the same problem.  I tried your suggestion but am unable to run chkdsk because I do not have the proper "authority"....in DOS


    What do you mean by authority?

    Run CMD using an elevated prompt means use run as an administrator option.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Wednesday, April 27, 2011 5:24 PM
  • Since these are just released updates, I suggest just waiting for Microsoft to repair the problem.  This problem appears to be happening to everyone. 
    Wednesday, April 27, 2011 8:32 PM
  • Hello,

    how many users have the same problem in this thread?

    Have you tried the steps I mentioned?


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Wednesday, April 27, 2011 9:29 PM
  • I had the same problem too and resolved it by installing each update separately. I noticed KB2515325 and KB982018 requires a reboot after installation since it's using system resources currently in use. So you might be able to successfully install them in less steps by mix & match.
    • Proposed as answer by Trev Vu Thursday, April 28, 2011 3:10 AM
    • Unproposed as answer by Trev Vu Thursday, April 28, 2011 3:10 AM
    • Proposed as answer by pSimonh Thursday, April 28, 2011 8:01 AM
    Thursday, April 28, 2011 12:35 AM
  • KB2492386

    KB2515325

    KB2522422

    KB982018

     

    I installed them 1 by 1 in the above order and it worked.  The first one is the only one that didn't make me reboot.  I've found that KB982018 might be the culprit and you can install the other 3 in one try, then do KB982018 last.

     

    I've read trying to download manually, but I didn't try that either.  I just unchecked stuff off from windows update.

    • Proposed as answer by pSimonh Thursday, April 28, 2011 8:02 AM
    • Marked as answer by linuts01 Thursday, April 28, 2011 10:42 AM
    Thursday, April 28, 2011 4:10 AM
  • I would just like to add that it is happening to many of our PCs on our network (all W7 Enterprise Ed.) and this is also happening on my own PCs at home! 1 Home Premium and 1 Ultimate.

    Same four update fails from nowhere.

    I'm about to try the manual install option  on one PC but this is hardly a solution when I'm faced with 100+ PCs (and now the usual blathering on about WSUS and why is it not in use?)

    Terrible series of updates, not good shortly after the SP1 debacle. MS falls back into pit of complacency...

     

    EDIT:

    linh.nguyen & Trev Vu - thanks, the manual update and the sequence suggested works. Now to work out a method for all the other PCs...

    Thursday, April 28, 2011 7:42 AM
  • I am having the same issue right now.

    4 updates are installed, then Windows reboots, there is a long wait on system startup with 0% progress, then there is a message that updates are reverted and I go to normal logon screen.

    Trying to install updates one by one.

     

    Thursday, April 28, 2011 7:45 AM
  • O.K. The manual install did it...bit of a PITA  though. any ideas as to why we had to do a manual install of these updates..?

    cheers


    Who cares who wins
    Thursday, April 28, 2011 10:44 AM
  • Seriously Microsoft?

    Here's the thing, I received a call from my dear mom about this issue. She's not computer expert and never will be. She has no idea how to turn anything off from computer. But she's annoyed that she has to start up computer every single time now twice because some one of Q&A fucked up. Your given solution is Invalid! Please come to solution what even 50 year old can do with out some sort understanding how to go ms config and disable startup programs and run disk checks. 

    This update confusion makes me want go and buy my mom Apple, and then you guys have meetings on MS wondering why apple does so good. This is the reason. Everyone aren't computer wizards and rather overpay things on first day than pay to some long haired WoW player every single time when MS Q&A fuck's up. This is second time in 30 days when I have to travel to my moms house ( 140 miles ) fix something what you guys fucked up. 

    Next time I send you a bill and you can debate abut it in EU highest court. 

    Thursday, April 28, 2011 2:09 PM
  • Seriously Microsoft?

    Here's the thing, I received a call from my dear mom about this issue. She's not computer expert and never will be. She has no idea how to turn anything off from computer. But she's annoyed that she has to start up computer every single time now twice because some one of Q&A fucked up. Your given solution is Invalid! Please come to solution what even 50 year old can do with out some sort understanding how to go ms config and disable startup programs and run disk checks. 

    This update confusion makes me want go and buy my mom Apple, and then you guys have meetings on MS wondering why apple does so good. This is the reason. Everyone aren't computer wizards and rather overpay things on first day than pay to some long haired WoW player every single time when MS Q&A fuck's up. This is second time in 30 days when I have to travel to my moms house ( 140 miles ) fix something what you guys fucked up. 

    Next time I send you a bill and you can debate abut it in EU highest court. 


    Wow, that's pretty harsh, Taavi.  You seem to have a pretty narrow-minded idea of how many hundred of thousands of different configurations Microsoft has to support with a single, unified update system.  Go get your mom an Apple - see how that works out for you.  Something tells me you haven't bitched or moaned about the hundreds of other updates that DID seamlessly, automatically and silently install - but now you're all venom and hate towards Microsoft for missing a small detail somewhere in in a massive list of possible configurations. 

    You might try using RDP or some other readily available tool to allow remote access to the box without having to drive 140 miles to dear mom's house.  That's how I take care of my parent's machines, and it's worked well for me.  Then again, I like seeing my parents - any chance I get, and I generally get a home cooked meal out of the deal.

    If you can stop acting like a douche bag long enough to actually try and troubleshoot the problem, you likely would have figured out of to solve this issue yourself.  You're one of those kinds of people who LOVE to Bandwagon-bash Microsoft when it's convenient for you, but the rest of the time you silently LOVE to use their products.  Whatever you do, don't give Microsoft any credit for their successes - that bitter pill just might drive you over the edge.

    Flames aside, here's what I did to get these particular updates to install.  It seems that KB2515325 is the hinge that's making or breaking these installs from working one-after-another.  I installed all the updates I could, did a reboot, and was left with the 4 KB's mentioned.  I didn't download the standalone updates, either - I used Windows Update.  Here's what I did to get them all to install on my 64-Bit system:

    1. Install KB2492386 by itself - unselect all other updates
    2. Reboot
    3. Install KB2515325 by itself - unselect all other updates
    4. Reboot
    5. Install KB2522422 by itself - unselect all other updates.  I was not asked to reboot after this update.
    6. Check for updates again, and you should only have KB982018 left.  Install KB982018.
    7. Reboot one last time, then everything will hopefully have taken.

    If that works for you, Taavi, be sure and give me your address so I can send you a bill for providing you step-by-step instructions.

    SonarTech

     


    Thursday, April 28, 2011 5:12 PM
  • SonarTech,

    I followed your instruction several times and kb982018 still won't install. The other 3 updates installed when I manually installed each separately, but not kb982018. After  I hit install update it gets to 8% and then restarts itself and then when it comes back up in configures to 8% and then say the install failed and it will now restart and go back to original configuration, then it does that. Everthing seems to work fine except if I run manual windows update it wants me to update with kb982018 all over again. Egads, this is frustrating! I am running Win7 sp1 x64 with ie9 installed. I have tried turning off Norton 360 firewall and antivirus software...same darn thing happens. Ran scannow and tried again...same darn thing happens. Anyone got any more ideas?

    Friday, April 29, 2011 1:05 AM
  • Yikes - those symptoms are considerably different than the ones I experienced (or have heard about).  The fact that the other ones installed OK using the one-at-a-time drill seems to indicate something's particularly squirlly with KB982018.  Have you tried downloading the update package directly?

    The link for that partcular KB is http://www.microsoft.com/downloads/details.aspx?FamilyId=a8cd6aa3-948e-46e6-8125-7a8b3cf24a3f

    Try installing the update using the standalone installer.  That should at least remove some possibility of this being related to Windows Update.

    SonarTech

    Friday, April 29, 2011 3:27 AM
  • Sonar Tech

     

    Thanks for the suggestion but it again did exactly as I described above. I am sure stumped. Checking the web it appears others are having similar/same problem just with the "squirlly" kb982018 update after installing the other 3 updates separately and  manually. Some report kb982018 installing after proceeding this way but for others it does pretty much what mine is doing. I am hoping MS is able to figure it out. I'll check back tomorrow to see if anyone else has any suggestions.

    Friday, April 29, 2011 7:05 AM
  • Sonar Tech

     

    Thanks for the suggestion but it again did exactly as I described above. I am sure stumped. Checking the web it appears others are having similar/same problem just with the "squirlly" kb982018 update after installing the other 3 updates separately and  manually. Some report kb982018 installing after proceeding this way but for others it does pretty much what mine is doing. I am hoping MS is able to figure it out. I'll check back tomorrow to see if anyone else has any suggestions.


    So you did try the standalone installer, and the exact same thing happened when you tried to install it using Windows Update?

    What error code are you getting for this update?  Please go into the Windows Update history, find one of the kb982018 failures and let us know what the error code is. 

    Thanks.

    SonarTech

    Friday, April 29, 2011 4:04 PM
  • Wow, that was really annoying. Manual install worked. Hope that gets patched soon because even with a decent idea of how to fix a problem like that I still got all aggravated for about 3 days every time I'd reboot and had to wait. I kept thinking it was different new installs, nothing obvious told me that they had failed.

     

    --Derek

     

    Friday, April 29, 2011 11:59 PM
  • I agree Taavi,

     

    i love the way the windows community is so acustom to putting up with crap. 


    This should just work.   I don't wanna do a chkdisk or anything.   This is microsofts problem and not mine.

     

    Microsoft doesn't think that way. 

    Saturday, April 30, 2011 12:34 PM
  • "This should just work".  Yeah, it probably should - and the majority of the time, it does.  Thousands of people labor daily to make sure that the vast majority of possible hardware and software configurations are covered by these updates, and I for one appreciate their efforts.  Go look in your Windows update log - you'll clearly see that the number of "Successful" installs easily outweighs the number of "Failed" installs.  What's YOUR percentage of fails versus successes?

    Since you and Taavi are being so indignant about this, let me ask you something:  Has your car ever died?  What did you do about it?  Did you sit in the driver's seat moaning "This should just work - I don't wanna take it in for service" over and over again until someone came to your rescue and fixed it for you for free?  Did you tell the service center "This is Honda's problem and not mine"?

    What did that get you, exactly?  Did your car miraculously heal itself for free and take you to work, or did you have to do SOMETHING to fix the problem yourself?

    Grow up and stop acting like a indignant baby.  Things break - GET OVER IT.  You think these kinds of problems don't happen to Apple customers as well?  HAHAHAHAHA!  Then you truly are delusional and ignorant, and there's probably no help for you, regardless of what Microsoft does for you.  Have you and Taavi ever bothered to do a search for "Apple cheetah won't install updates"?  Probably not, because you're too busy bitching about a single pain-in-the-ass software update that probably doesn't even apply to your particular setup anyway. 

    What's even more curious about this is that both of you DID apparently try to solve the problem, or you wouldn't have ended up here reading this particular forum trying to find an answer.  What are you doing here, Jimerb?  My guess is that you're just trolling the waters and stirring the pot since you don't seem to want to actually fix this problem that you may or may not have.  Instead, you just want to sit in the driver's seat whining "This should just work! Wahhhhhh! I don't wanna have to fix it!!! WahhhhhhHHHHH!"

    If you guys hate Microsoft products so much, then why the hell are you using them?  Man-up and load a Linux Distro.  I dare you to see how long you can tolerate that before you run whining and screaming back to Windows because all of your precious keygens stop working.

    FEEL FREE TO GIVE US THE DATA WE REQUIRE TO HELP YOU HELP YOURSELF.  My system's working swimmingly well, thanks in part to the people in this forum.  The people here gain absolutely nothing by reading about your miserable Windows Update experience, and if you really want this issue solved and you want our help, then give us the data we require to figure it out.  If you're not interested in doing anything other than bitching about this problem, I heartily recommend that run right over to Apple and pay $2500 for $700 worth of hardware so that you can bitch and moan about your empty bank account instead.

    But hey, look at the positive side:  At least iTunes will come pre-loaded on your new Apple system and your precious iPhone, iPad, iPod, iBroke and iCrap will all work together in peace and harmony.

    I'm very sorry that the Trauma of having to actually fix something is taking such a heavy toll on you both.  You have my pity.  Good luck getting that Honda to start, Killer.

    SonarTech

    • Proposed as answer by bilko01290 Saturday, April 30, 2011 8:08 PM
    • Unproposed as answer by bilko01290 Saturday, April 30, 2011 8:08 PM
    Saturday, April 30, 2011 7:51 PM
  • THE FOLLOWING WORKED FOR ME I RESET AND REREGISTERED WINDOWS UPDATE COMPONENTS http://www.sevenforums.com/tutorials/91738-windows-update-reset.html ALL UPDATES WORKED AFTER THIS RESET

     

    bilko01290

    Saturday, April 30, 2011 8:14 PM
  • Sonar Tech,

    The error code is 8007051A.

    Saturday, April 30, 2011 8:41 PM
  • Thanks, your solution worked great!!!!!!!!!!
    Sunday, May 01, 2011 2:09 AM
  • Hi, Harmil -

    That error definitely seems to point more towards a Windows Update problem.  What happened when you tried to download and run the installer for KB982018 available here:

    http://www.microsoft.com/downloads/details.aspx?FamilyId=a8cd6aa3-948e-46e6-8125-7a8b3cf24a3f

    You only mentioned that you "tried everything exactly as shown above" but you didn't tell us what exactly happened when you tried to run KB982018 directly outside of Windows Update.  Did it return an error?  What happened?

    As for the potential problem with Windows Update - try resetting the Windows Update components.  Please visit: http://support.microsoft.com/kb/971058 for more information on how to do that.

    Sorry this update's being such a pain in the butt.  Hopefully we'll get it sorted out soon.

    SonarTech

     

    Sunday, May 01, 2011 6:15 AM
  • Before doing my solution in my earlier post above the 3 updates wouldnt install no matter what i did was a different error code from harmil was getting must have been corrupt somehow ?
    Sunday, May 01, 2011 9:54 AM
  • It's worked for me. Thanks!
    Sunday, May 01, 2011 1:40 PM
  • Hello,

    Can someone please provide logs for this issue?

    If you could do the following, and then upload the logs to a publicly accessible location (skydrive, etc.), it would be appreciated.

     

    Please include the following:

    C:\windows\inf\setupapi.dev.log

    C:\windows\logs\cbs\cbs.log

    Event viewer logs -

    Run eventvwr.msc (hold the windows key + r, then type eventvwr.msc)

    On the left, expand Windows Logs, and select System.  On the right, you should see "Save All Events As"  - click this and save it, no display information is fine.

     

    Please share a link to where the logs are uploaded, thanks!

     

    -Z

     

    Wednesday, May 04, 2011 9:10 PM
  • The advice to install the failed updates in the correct order worked for me. I have a generic x86 Win7 Ultimate. The troublesome ones for me were:

    KB2506928

    KB2492386

    KB982018

    Since I don't play here often, I missed the implied step "Go and start Windows Update, then view the list of available updates and uncheck all but one."

    I did KB982018 last and this one needs a reboot. All the updates installed properly and after the reboot there was a "Configuring updates" phase which also completed.

    I am now downloading the SP1 file manually as I have four machines in the house that will need it.

    Friday, May 06, 2011 11:34 PM
  • Logs: http://cl.ly/3Z28071r0T25201C3k2B

    Screenshot of the update history: http://cl.ly/3K2i0C1Z1O0z2n083f1J

    For me, installing them one-by-one let me install all, but KB982018.

    Sorry about the irrelevant updates in the end... I got frustrated and started installing other stuff hoping that it would magically fix the stuck update.

    Sunday, May 08, 2011 7:08 PM
  • Please come to solution what even 50 year old can do with out some sort understanding how to go ms config and disable startup programs and run disk checks.

    What an insensitive clod!

    Look, dude. I'm 55 and have worked literally inside of Windows since Win95 and NT 3.51. I've probably forgotten more about how Windows works than you'll ever begin to know. How about YOU try writing an operating system that tries to make everybody happy? Win7 is well over 50 million lines of source code. How do you propose to be sure it has zero bugs? And how do you propose to be sure that every patch to that code always works 100% for the millions of different configurations that are out there? The forums represent a very small percentage of users who have problems, compared to the millions for whom it just works.

    Before you sing the praises of Apple's reliability, just try fixing one when the "Sad Mac" icon shows up. Equivalent to the Windows Blue Screen of Death, but with zero information. The investment just to own the software tools required to work on Macs is well over 2 grand. That's about 1400 EU to you.

    And consider that "old" people, and other people in general, are each experts in their own areas, understanding things you may never begin to know. Wake up before you find yourself as that "50 year old" that is "with out [sic] some sort of understanding."

    Now buck up, Buttercup, and go visit your mother.

    For those who want to fix it:
    Installing the upgrade manually will work for many cases, but it is just a workaround. It does not solve the problem, so it could come up again later with another upgrade. The FIX is to reset Windows Update. It is likely not a problem with WU itself, as SonarTech suggests. More likely it's that something became corrupted with an earlier update.

    The easiest way to do the reset is to run this little batch file that someone else has written. Just copy this address into your browser, download it to your desktop, and run it as Administrator.
    http://www.sevenforums.com/attachments/tutorials/121652d1291785217-windows-update-reset-reset_windows_update_history.bat

     




    Monday, May 09, 2011 1:31 PM
  • Kalmi - did you run the SUR tool?  (http://support.microsoft.com/kb/947821)

     

    You're hitting a permissions problem during a file copy.  Make sure you're running as admin, as well.

    Monday, May 09, 2011 10:52 PM
  • Interesting banter on this post, but let's get down to business

    I've managed to manually install the following (in order of install)

    KB2492386

    KB2502285

    KB2506928

    KB2425227

    I then proceeded to install KB982018. This failed.

    I've tried running the bat file mentioned, didn't make a difference.

    I am now installing KB947821 (SUR tool), it's taking it's time to install. But I will let you know if this works

    Really need to find a solution here. Quite a lot of users are having this problem in my enterprise

    Tuesday, May 10, 2011 4:23 PM
  • See if this is the reason that KB982018 fails to install. 
    From -  Microsoft patch KB982018 (Solution)

    Solution: KB982018 is updating the usbstor.inf and the usbstor.PNF.

    If you locking down USB devices then these 2 files are explicitly denied access for the following groups:


    Everyone
    Administrators
    User
    System

    If you change all of these to Full control then the patch will install.

    The best solution is to apply a GPO to reverse the explicitly deny security and give full control back to the above groups. Then apply the patch then re-apply the original GPO to lock things back down.


    MowGreen
    Windows Expert IT Pro - Consumer Security

    *-343-* FDNY
    NEVER FORGOTTEN

     

    • Proposed as answer by ZeniTimes Thursday, May 12, 2011 12:19 PM
    Tuesday, May 10, 2011 5:58 PM
    Answerer
  • Thank MowGreen, I have applied a GPO to lock these files down.

    Does KB982018 only apply to Windows 7 machines? or Windows XP as well?

    Wednesday, May 11, 2011 8:30 AM
  • I agree 100% brother my mom is 66 and I have the exact same problem lol.  As for the other person replying about this post keep in mind it was Microsoft that agressively monopolized the market and they should make it easier for support. They certainly have the money to do so.

     

    Talerian

    Wednesday, May 11, 2011 3:03 PM
  • Thank MowGreen, I have applied a GPO to lock these files down.

    Does KB982018 only apply to Windows 7 machines? or Windows XP as well?


    You're welcome, ZeniTimes. KB982108 applies to Win 7 and WS2008R2, not XP.

    MowGreen
    Windows Expert IT Pro - Consumer Security

    *-343-* FDNY
    NEVER FORGOTTEN

     

    Wednesday, May 11, 2011 4:18 PM
    Answerer
  • Once again i have had to do a manual install of the latest Windows Updates...KB2533552....KB2534366....KB2529073....This is becoming a real pain, having to reboot after each manual update...what is going on with Microsoft Windows Update...? Have just browsed thru the forum and apparently KB 2534366 is to blame. surely if there is a problem with installing this update Automatically Microsoft should not release it until its fixed.

    It seems like a waste of time setting the Updates to Download and Install Automatically if its not going to work.

    cheers

     


    Who cares who wins
    Thursday, May 12, 2011 1:39 AM
  • Once again i have had to do a manual install of the latest Windows Updates...KB2533552....KB2534366....KB2529073....This is becoming a real pain, having to reboot after each manual update...what is going on with Microsoft Windows Update...? Have just browsed thru the forum and apparently KB 2534366 is to blame. surely if there is a problem with installing this update Automatically Microsoft should not release it until its fixed.

    It seems like a waste of time setting the Updates to Download and Install Automatically if its not going to work.

    cheers

     


    Who cares who wins


    I'm curious - how many times has this kind of problem happened to you in the past?  I mean, obviously Windows Update usually requires a reboot once updates are finished installing, but how often in the past, say three years, have you had to go through the manual process that we're currently dealing with?  My answer is once in the past three years.  I'm not saying that makes it OK, I'm just trying to get a handle on what's got you so bummed out about this.  Are you the kind of person that just expects your car to work 100% of the time and never fail?  Does your dealership come to your house each month and provide maintainance on your car at no additional charge to you? (Notice I did not say it was free)...

    Microsoft does, and considering the massive list of configurations they need to support, I'd say they do a pretty darn good job. 

    So, Linuts01, what's your answer?  How many times has this kind of problem happened to you in the past?

    SonarTech

    Thursday, May 12, 2011 4:10 AM
  • I agree 100% brother my mom is 66 and I have the exact same problem lol.  As for the other person replying about this post keep in mind it was Microsoft that agressively monopolized the market and they should make it easier for support. They certainly have the money to do so.

     

    Talerian


    My Mom's 75 and she's got a good handle on how to update her computer.  You say that Microsoft aggressively monopolized the market...  Do you have an Easynews account?  If so, do me a favor and do a quick search for activators and keygens for Windows and Office.  Rampant, unchecked piracy made Microsoft products famous.  That ugly truth seldom gets brought out into the light, but the fact remains PIRACY is largely responsible for making Microsoft products as pervasive as they are.  You got used to using that "free" copy of Windows 98 you got back in the day, and it was easier to move onto the next version of Windows than it was to learn a brand new OS.  The piracy rate for Microsoft products is a hideous number that would make your face melt off if you saw the data.  It truly is shocking.

    What suggestion(s) do you have for Microsoft to provide "easier support" in addition to the no-charge updates you get each month?  I'd would LOVE to see your ideas... No, really, I would.

    SonarTech

    Thursday, May 12, 2011 4:20 AM
  • Once again i have had to do a manual install of the latest Windows Updates...KB2533552....KB2534366....KB2529073....This is becoming a real pain, having to reboot after each manual update...what is going on with Microsoft Windows Update...? Have just browsed thru the forum and apparently KB 2534366 is to blame. surely if there is a problem with installing this update Automatically Microsoft should not release it until its fixed.

    It seems like a waste of time setting the Updates to Download and Install Automatically if its not going to work.

    cheers

     


    Who cares who wins


    I'm curious - how many times has this kind of problem happened to you in the past?  I mean, obviously Windows Update usually requires a reboot once updates are finished installing, but how often in the past, say three years, have you had to go through the manual process that we're currently dealing with?  My answer is once in the past three years.  I'm not saying that makes it OK, I'm just trying to get a handle on what's got you so bummed out about this.  Are you the kind of person that just expects your car to work 100% of the time and never fail?  Does your dealership come to your house each month and provide maintainance on your car at no additional charge to you? (Notice I did not say it was free)...

    Microsoft does, and considering the massive list of configurations they need to support, I'd say they do a pretty darn good job. 

    So, Linuts01, what's your answer?  How many times has this kind of problem happened to you in the past?

    SonarTech


    Actually its 4 times i have had to manually install updates...I am not saying Microsoft are not doing a good job, i am saying it is becoming a PITA to have to do these updates manually...as for the car analogy  that is a load of rubbish...Microsoft Updates have worked flawlessly in the past, So people would like to know why this is happening now...surely if there is an Update that will not install Automatically..then users should be notified when the updates are downloaded, so they can then install that update manually when the rest have finished installing,instead of going through the process of seeing which of the updates is causing the problem and then installing them one by one. at least Microsoft could either "colour" the update or mark it with an asterisk.

    Who cares who wins
    Thursday, May 12, 2011 4:48 AM
  • 4 times in three years?  Wow.  So, not including rare-case daily updates or emergency updates, there are 12 "Patch Tuesday's" in a year, so 36 in 3 years.  You said that you had to manually intervene 4 times, so I'll assume you mean different patch Tuesdays (since that's the worst-case scenario, and I'm certain that's what you're hoping for).  That's 11% for you (4 manual interventions over 36 patch Tuesdays), and 2.7% for me (1 manual intervention).  That's odd.  Stranger still, you said "Microsoft Updates have worked flawlessly in the past", yet you said you've had 11% failures that required your manual intervention in the past 3 years.  Now I'm confused.  They worked "flawlessly in the past" - so what does "in the past" mean to you exactly?

    If you're going to try to tell me that you've had this same kind of problem that this thread is about in recent history (i.e., the past 6 months), then I say you're not being very honest with us or you've got some serious corruption happening on your machine.  Between my family and the huge base of machines I manage on multiple sites, this is the first set of updates that has tripped-up like this, and the first one I've seen with Windows 7.  Vista was far more turdy, but even that didn't trip over itself more than 10% of the time - unless there were other contributing factors on the failing machine, which typically included MalWare, disk corruption, or faulty hardware.  It's been interesting to note over my 20 year-career in IT how many BSOD's and OS crashes were blamed on Windows that were actually caused by bad hardware - particularly failing hard drives, but that didn't keep nearly every one of those victims from blaming Microsoft for making a "crappy OS that crashes all the time" - all because their Hitachi Deathstar Hard Drive was slowly eating itself alive.

    Whatever.  I can agree agree with you that it is a PITA, but from my perspective, it's no worse than any other peice of technology that occasionally trips up.  I don't think I have one piece of modern technology in my home that hasn't done something to piss me off, regardless of how simple it seems.  My toaster burned the hell out of my toast this morning, but it's worked just fine for the past 2 years and I didn't change a thing this morning - what the hell??!

    What I do know is that starting in 2005, Windows Update was being hit by about 150 million people, with about 110 million of those using Automatic Updates.  According to the Microsoft News Center and Wikipedia, as of 2008 Windows Update had about 500 million clients, processed about 350 million unique scans per day, and maintained an average of 1.5 million simultaneous connections to client machines.  On Patch Tuesday, outbound traffic easily exceeded 500 gigabits per second.  Approximately 90% of all clients used automatic updates to initiate software updates, with the remaining 10% using the Windows Update web site.

    Personally, I'm amazed that Windows Update works as well as it does, given the completely unknown conditions on your computer that it's expected to reliably and automagically traverse each and every time an update is available.

    For the rest of you still hitting this issue, know that Microsoft knows about it and is working very hard to try and sort it out.

    SonarTech

     

    Thursday, May 12, 2011 6:40 AM
  • You're welcome, ZeniTimes. KB982108 applies to Win 7 and WS2008R2, not XP.


    To fix this what I've done is split this policy into two, one XP and one Vista/ 7, using WMI filters.

    The XP policy still restricts SYSTEM access to USBSTOR.inf and USBSTOR.pnf

    The vista/ 7 policy removes the restriction

    I've tested this out and the policy works a treat.

    If anyone need them, the WMI filters I used are:

    Windows XP Only

    select * from Win32_OperatingSystem where Version like "5.1%" and ProductType = "1"

    Windows Vista/ 7

    Select * from Win32_OperatingSystem where Version like "6.%" and ProductType = "1"

     

    Thursday, May 12, 2011 12:18 PM
  • Hey guys,

     

    I am unable to install updates for windows 7 and the list of the updates are as follows - 

    KB2446710

    KB2478662

    KB2507938

    KB2532531

    KB2555917

    KB2533623

    KB2647666

     

    All of these updates are recommended and I cant seem to install them as I get an error stating: error code 80070308

    Can someone help me out on this?

     

    Friday, July 15, 2011 12:47 AM
  • After reading some of these posts, I have to wonder; how much does microsoft pay you, SonarTech, that you defend them so?

    You tell Jimerb to go buy an apple because he (or she) is pissed that the update didn't correctly install? What the hell? He (or she) has already bought microsoft...why in the world would he be even be thinking of buying a mac if microsoft  had done their jobs correctly?

    You said, " Things break - GET OVER IT." Yes, you're right...things do break. But in your car scenario, the manufacturer didn't come out and pour sugar in the gas tank. For all intents and purposes, microsoft did and does.

    You yourself are ranting about people bitching about a problem that SHOULD NEVER EXIST! Bravo...your mother MUST be proud.

    The real issue here isn't how to get a stubborn update to install, its WHY DID MICROSOFT RELEASE SAID UPDATE(S) IF THERE WERE ANY CONCEIVABLE PROBLEMS GETTING THEM TO INSTALL CORRECTLY? Any other point is moot.

    I paid good money for Windows (more than I should have since I've had almost every version of windows in the past since 2.1) and I expect their product to work as advertised. That includes the updates! That also includes NOT sending out updates that need to be patched, and then patch their patches, ect. If an update doesn't work, they have no business releasing it until it does. PERIOD!

    If you know how to correct an issue, that's great, but when you start insulting people for being upset, that's NOT.

    Bottom line, microsoft needs to show a little bit more accountablility.

    <Gets down off his soapbox>

    Thursday, July 21, 2011 10:49 PM
  • After reading some of these posts, I have to wonder; how much does microsoft pay you, SonarTech, that you defend them so?

    You tell Jimerb to go buy an apple because he (or she) is pissed that the update didn't correctly install? What the hell? He (or she) has already bought microsoft...why in the world would he be even be thinking of buying a mac if microsoft  had done their jobs correctly?

    You said, " Things break - GET OVER IT." Yes, you're right...things do break. But in your car scenario, the manufacturer didn't come out and pour sugar in the gas tank. For all intents and purposes, microsoft did and does.

    You yourself are ranting about people bitching about a problem that SHOULD NEVER EXIST! Bravo...your mother MUST be proud.

    The real issue here isn't how to get a stubborn update to install, its WHY DID MICROSOFT RELEASE SAID UPDATE(S) IF THERE WERE ANY CONCEIVABLE PROBLEMS GETTING THEM TO INSTALL CORRECTLY? Any other point is moot.

    I paid good money for Windows (more than I should have since I've had almost every version of windows in the past since 2.1) and I expect their product to work as advertised. That includes the updates! That also includes NOT sending out updates that need to be patched, and then patch their patches, ect. If an update doesn't work, they have no business releasing it until it does. PERIOD!

    If you know how to correct an issue, that's great, but when you start insulting people for being upset, that's NOT.

    Bottom line, microsoft needs to show a little bit more accountablility.

    <Gets down off his soapbox>


    This install issue had nothing to do with the patches themselves, it's a timing issue that can crop up in the Plug and Play stack that prevented the update process from initializing.  We resolved this with KB2552343 last month.  The patches that failed to install are unchanged.

    http://support.microsoft.com/kb/2552343

    -Z

    Thursday, July 21, 2011 11:18 PM
  • Same goes for you, DHag. Its wonderful that you are so knowledgable and that you have such an illustrious career. Not everyone knows that much about computers or OS's. You were new to computers once. What would you have done or said if, in your early computing days, something that should have worked perfectly slowed your computer down?

    Yeah, that's what I thought. Cut these people a little slack, huh?

    You mentioned that win7 has, "well over 50 million lines of source code. How do you propose to be sure it has zero bugs?" In answer, I have no idea, but then, I don't work for microsoft and didn't write any of those 50 million lines of code. What I DO know is that if there is ANY possiblity that an update will negatively impact ANYONE'S computer, then microsoft had no business releasing it.

    Let me ask you this. If you hired me to remodel your house...lets say add a room on...and I did the job to everyone's satisfaction, then came back a week or a month later and tore out one of the walls to fix some minor little thing while you were at work, how would you react? On top of having to tear out the wall, oh damn, forgot, need a special order item that's going to take 3 weeks to get here, and you're just going to have live with a 3-walled room until then. Wouldn't you be a little upset? Wouldn't you bitch at me and ask why in God's green earth I didn't wait until AFTER I had the item in hand to tear out your wall? Most likely, you would be on the phone to the Better Business Bureau! Admittedly, that's a pretty far-fetched example, but please tell me how that differs from microsoft releasing a faulty update. Both cases the product appears finished and working. Both cases the owner is inconvenienced for something that wasn't even asked for. The only difference is we can't call the BBB on microsoft.

    I think its great that you're knowledgable and can help people fix these types of problems, but where do you get off talking to people like that? I'm not a violent man, but if I was having a problem and you came off to me like you did to Taavi, and you were in the same room, I think I'd break your nose before I regained my composure. When people are having problems, the LAST thing they need is some greater-than-thou asshole talking down at them. You need to temper your knowledge with a little compassion...try seeing the problem through their eyes.

    Free life lesson for you, even though I have little doubt that you'll blow it off. That's OK...it's your loss.

     

    Thursday, July 21, 2011 11:26 PM
  • Sorry, "MNM419", but I sprayed a whole can of TROLL-B-GONE on this thread 2 months ago.  Microsoft's already fixed this problem and you're about 60 days LATE TO THE FLAME GAME, so feel free to STFU and B-GONE.  Beyond that, I'm sure Microsoft will be accepting apologies from you, JimErb, LiNUTS and the rest of your troll clan until at least 6PM tonight.

    SonarTech

    Thursday, July 21, 2011 11:32 PM
  • To sum this up is very simple.  Microsoft did not find a major regression and released it to everyone.  Mistakes at this level should never reach the public, they are to be found in-house and the schedule delayed so that a proper fix can be verified working without the public ever even knowing about it.
    Thursday, May 10, 2012 8:26 AM
  • Since these are just released updates, I suggest just waiting for Microsoft to repair the problem.  This problem appears to be happening to everyone. 

    Why would we want to wait. These updates are suppose to placed for security purposes. What your suggesting is outrageous. I would like to see an answer. For, i have for the last five days been attempting to install updates, and  supposedly a clean install. Every time i install updates one, maybe two might succeed, the other forty failed. Unlike a week ago, everything I was installing, was being installed. I have something/someone in my system, preventing these updates from installing, for a reason. I want to see what excuse Microsoft has. My problem has to do with networking, today my networking involves RIPE (overseas). I have been trying to fix my problem since last year, recently I tried again, except this time, Microsoft wants to charge $99.00 for what they could not fix over a half year ago. They think by charging me $99.00 this year, their going to be able to fix what they couldn't last year. So. i am looking for solutions, what their encountering is what i am encountering when attempting to update the system. So please, do not encourage Microsoft Techs from giving a proper response.


    Thursday, May 10, 2012 4:58 PM
  • http://support.microsoft.com/kb/2552343

    This KB should resolve many issues related to updates installing.

    Thursday, May 10, 2012 7:09 PM
  • While the post you are responding to is a little harsh the "Things break - GET OVER IT" is the exact attitude that gets this guy and others so upset.  Truly they don't happen to Apple customers as much, however OSX does not allow me to do as much as Windows.  When my kids went off to college I got them all Macs because I couldn't travel 1,000 miles to fix them.  But that is neither here nor there, both platforms are viable and your and everyone else's help is very much appreciated.  However the "get over it" comment isn't!!!

    I just spent 3 hours tracking down a similar error on my WHS 2011 that I will never get back, and all I did was run update...

    Tuesday, May 22, 2012 2:39 PM