Detection Logic fixed for KB937061 (MS07-052)

Detection Logic fixed for KB937061 (MS07-052)

  • Comments 28

Customers have been offered KB937061 for Visual Studio 2005 Service Pack 1 from Microsoft Update when they have already installed it. The Microsoft Security Response Center blog has more information about the problem and what they have done to fix it.

I wanted to add that because patches are cached according to their package code, you do not have multiple copies installed for each time you successfully installed the patch.

The updated detection logic has been pushed to Microsoft Update, but if you are still being offered KB937061 follow the instructions below.

  1. net stop wuauserv
  2. rmdir /q /s %WINDIR%\SoftwareDistribution
  3. net start wuauserv
Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
  • PingBack from http://msdnrss.thecoderblogs.com/2007/09/14/detection-logic-fixed-for-kb937061-ms07-052/

  • Thanks, the fix worked! I don't know how many times my computer decided to install the patch! :-)

  • When will the detection logic for 932471 be fixed?

  • jmurphy, it already was by the time I posted this. If you're still having problems, follow the steps I posted.

  • You posted about 937061. I asked about 932471.

    Despite following the instructions, 932471 is still being offered, and fails to install every time.

    http://blogs.msdn.com/astebner/archive/2007/08/30/4658114.aspx

  • jmurphy, if the patch fails to install it will, of course, be offered again. It will be offered until it gets installed correctly or a superseding patch is offered.

    Look in your %TEMP% directory for a sub-directory with the same name as the patch (it will have the KB number in it). Post the verbose logs somewhere (http://folders.live.com work if you don't have any other means) and send me the URL.

  • Have you read Aaron Stebner's post?

    http://blogs.msdn.com/astebner/archive/2007/08/30/4658114.aspx

    It keeps trying to install a patch on a machine that does not require that patch. This is a known problem that I thought you were aware of, sorry for the confusion.

  • jmurphy, I do read his blog but many others and don't remember the details. I did review it, but if you have questions about that patch I recommend you reply on his post about the patch in question. I'm not involved with that issue currently.

  • I keep getting prompted to install this update.

    It has downloaded, but fails to install.

    It is a constant issue.

    Now, I am here at this blog trying to fix it myself.

    I saw the 1.2.3 instructions.

    Where exactly do I put them?

    In run? Command prompt?

    VB?

    I apologize ahead of time for seeming to be "computer dumb".

  • WTyson, if the patch fails to install it will be offered again. Even after the detection fix on Microsoft Update, the patch will be reoffered until it is installed successfully.

    You can generate a verbose log and email me the patch to the file posted online using the email link on this site. See http://blogs.msdn.com/heaths/archive/2005/10/20/logging-for-the-new-patch-wrapper.aspx for information on logging for the patch.

  • Just wanted to say that the visual studio 2005 sp1 installer is one of the biggest shame for microsoft. I had to install it on several machines with different specs and all of them gave me this bloody 1305 error. Seriously, you are not an open source developer, microsoft pays you, probably some good money, what is your excuse then?

  • This worked perfectly for me - awesome. I can now sleep at night...lol

    Thanks

  • Hi Heath.

    We are trying to use WSUS to deploy this update and it appears KB937060 is being detected as needed as opposed to KB937061(SP1). I came to this conclusion as if I run the updates manually, the KB937060 update tells me that the product is required and KB937061 installs correctly. Is this issue going to be addressed? How does the update tell whether SP1 is installed or not? A reg key or ....?

  • Jai, the patch targets SP1 based on the ProductVersion of the product. VS 2005 RTM has the ProductVersion in the MSI of 8.0.50727 while SP1 changes it to 8.0.50728. You must have SP1 to install SP1-level patches. There are no reg hacks that change that. If you need a fix for RTM and don't want to take SP1 yet, you need to contact Microsoft Customer Support Services and request an N-1 hotfix for the same issue.

  • Hi Heath.

    Well we have packaged SP1 with VS2005 so it may be a packaging issue, however according to automatic updates 937060 is being detected where 937061 should be. This will then fail to install with:

    "Product: Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU - Update '{78DD9A0A-4AE1-46D0-B9A6-578EFCA47A3C}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINDOWS\TEMP\MSI3199b.LOG"

    and

    "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an

    d that you have the correct upgrade patch."

    If I run the 937061 update manually (dld from the MS site) then it installs fine, however 937060 is still being detected as needed and subsequently fails with the same error as above. I've cleared the softwareDistribution folder and done a redetect and it's still getting evaluated as needed. Can you tell me what it looks for to determine if an update is needed?

Page 1 of 2 (28 items) 12