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.
- net stop wuauserv
- rmdir /q /s %WINDIR%SoftwareDistribution
- net start wuauserv
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:WINDOWSTEMPMSI3199b.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?
Jai, someone is looking into the detection logic, but can you clarify how you "packaged" the RTM and SP1 together?
Well we utilise a software distribution system to distribute VS and so it is packaged so as to avoid any prompts etc. I’m not part of the packaging team so I’m not exactly sure of the details of the package but it may be the reason the update is being detected incorrectly. If I can found out how the patches evaluate if they are needed (for instance if it’s a regkey) then I can check that key and see if it’s the package and then get it repackaged.
Thanks for your help, I look forward to seeing the detection logic :p
Jai, what I mainly need to know is if you’re still applying the patch using Windows Installer, or just updating the bits. It’s important that the patch is applied as intended or the SP1-level patches will not work because the ProductVersion of the product wouldn’t have been updated.
Well thats the thing the patches aren’t being installed. We have packaged Vs2005 SP1 and have distributed it to a few machines. Automatic Updates detects 937060 as needed and not 937061 and subsequently fails with the errors above as I assume it detects it is not pre-sp1 and fails. As part of my investigations I manually tried the 937060 and it fails with the error above as it obviously detects that the installation is sp1. If I try the 937061 update it works as it should. Basically, it appears automatic updates is not detecting VS2005 SP1 is installed but it is detecting VS2005 is. Thus it downloads 937060 and attempts to install it and then fails as SP1 is installed. I am just interested in how Automatic Updates determines if VS2005 or VS2005 SP1 is installed as if it detects if VS2005 SP1 is installed it should dl the 937061 update.
We distribute VS2005 SP1 via our Software Distribution system and are attempting to update it via WSUS. We’re not packaging the update with the VS2005 SP1 install
Jai, I meant how are you installing the SP1 patch when you mention "packaging"? Did you install the VS 2005 RTM MSI then the VS 2005 SP1 MSP, or even do an admin installation then install the admin image on a client machine? If KB937061 is installing correctly – which does target VS 2005 SP1 – it seems so but I want to confirm.
Hello Jai,
I work on the team which released this security update for Visual Studo and we would like to try and resolve your issue for you. Can you please get in touch with me by using the <a href="http://blogs.msdn.com/heaths/contact.aspx">contact form</a> on this blog and providing us an email id where you can be reached ? Heath should be able to redirect your mail to myself.
Regards,
Jamshed Damkewala
Security Program Manager, DevDiv
I just downloaded the 937061 executable from the Microsoft site. We currently have only two packages – Vs2005 and VS2005 with SP1 integrated. I will ask our packagers how they have packaged SP1 with VS2005.
>> Basically, it appears automatic updates is not detecting VS2005 SP1 is installed but it is detecting VS2005 is. Thus it downloads 937060 and attempts to install it and then fails as SP1 is installed.
I am having this same problem.
>> I am just interested in how Automatic Updates determines if VS2005 or VS2005 SP1 is installed as if it detects if VS2005 SP1 is installed it should dl the 937061 update.
I too would like to disable Automatic Update’s insistence on downloading, running and failing 937060. (i.e. a registry hack?)
I can’t be as helpful as Jai in tracking this down; I just mindlessly went out to some MSDN copies on our network and started installing away, and I don’t have a deep comprehension of the installation/packaging technology. OTOH I didn’t have to work very hard to stumble across this same problem, so… probably worth looking into on your end. I wish you luck.
— Chris
I’m having nearly the same problem as posted by Jai.
Microsoft Update detects the need for patch KB937060, but it repeatedly fails to install with error code 0x66a. I’ve tried downloading and applying the patch and it will not take.
I tried applying patch KB937061, also with no joy. Fails with the Installer error "The upgrade patch cannot be installed…because the program may be missing…"
If it helps, here’s the contents of the "Installed Products" box from "About Microsoft Visual Studio:"
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41664
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41664
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41664
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41664
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0000007-41664
Microsoft Visual Web Developer 2005
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
Security Update for Microsoft Visual Studio 2005 Professional Edition – ENU (KB925674)
This Security Update is for Microsoft Visual Studio 2005 Professional Edition – ENU. n
If you later install a more recent service pack, this Security Update will be uninstalled automatically. n
For more information, visit http://support.microsoft.com/kb/925674
Registry detection is currently used for VS 2005 but if you hack the registry detection you will likely see other patches that you don’t need, or not see future patches you do need. For now, please install the correct update manually. Microsoft Update will continue to offer the fix and Automatic Updates will try to install it again and again, but it won’t harm your system.
After the automatic updates failed, I tried manually installing first patch KB937060 and then KB937061. Both failed with the errors described in my post above.
Dave, can you try to install both patches again passing "/L*vx+ patch.log" to each, ZIP them up, and send me an email via the Contact link on my blog? I can reply and then you can attach the ZIP file.