Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart's Blog : Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart's Blog : Known Issues with Visual Studio 2005 Service Pack 1 — Fri, 12 Jan 2007 00:21:20 GMT

PingBack from http://blogs.msdn.com/heaths/archive/2007/01/11/known-issues-with-visual-studio-2005-service-pack-1.aspx

re: Known Issues with Visual Studio 2005 Service Pack 1

Dan Vanderboom — Fri, 12 Jan 2007 01:22:33 GMT

There's also a problem with Web Application Projects. I've seen quite a few posts out there of people writing about the same problem. I uninstalled the Web Application Project add-in, then I installed SP1 (which is supposed to have WAP built-in), and now when I try to open a solution with a WAP-type project in it, I get the error message "the project type is not supported by this installation".

Haven't seen a solution for it yet.

re: Known Issues with Visual Studio 2005 Service Pack 1

Gerard van der Land — Fri, 12 Jan 2007 03:24:35 GMT

Heath,

When I run VS80sp1-KB926601-X86-ENU.exe with /extract I get a 477 MB .msp file. Can I put that file on a distribution file share for others to install to save them the time of extracting, or is this file specific for the product(s) I have installed on my system?

Also, is this the file that Windows Installer tries to load in to memory to check the digital signature? If not, how big the file that causes this problem.

The "Installation Requirements" for SP1 mentions: "192MB of RAM required. 256MB or greater is recommended." How can this be sufficient if Windows Installer needs to read a big file in to memory to be able to verify the digital signature?

Can you explain why it needs to read the entire file in to memory, and why the memory needs to be unfragmented? As far as I know SAFER on Windows XP and Windows Server 2003 uses an MD5 or SHA1 hash, both of which operate on 512-bit blocks and can thus be calculated while reading a file in small blocks rather than having to load the entire file in to memory.

On my Windows Server 2003 SP1 system with 1 GB and without the policy workaround I have not been able to install SP1. Yesterday I added an extra 1 GB and had 1.6 GB of physical memory available after rebooting (which I did to minimize the chance that memory would be fragmented too much). You would think there should be enough unfragmented memory, but apparently this was not the case, as the installation failed once again with this error!

I have some suggestions:

- fix the digital signature check so that it doesn't need to read the entire file in to memory

If that is not possible:

- add a command line switch to disable the digital signature check for the current installation, rather than having to modify the Local Security Policy (which people may forget to reset after installing)

- make sure that Windows Installer reports that it does not have enough contiguous memory to verify the digital signature, rather than saying that the file was rejected by digital signature policy, which would suggest to most people that the file is corrupt. It caused me to re-download the file several times to make sure it wasn't.

My next attempt will be to slipstream an administrative image (from an XP machine) using your explaination in a previous blog posting, even though I don't like that this will cause all files to be unpacked. Hopefully there will be ISO images of slipstreamed builds on MSDN subscriber downloads soon (which Scott Guthrie mentioned in a comment on his blog: http://weblogs.asp.net/scottgu/archive/2006/12/15/visual-studio-2005-service-pack-1-sp1-released.aspx#1255232)

Can you please elaborate on the issue with rollback? Especially since Windows Installer does transactional installations, I would think that a rollback restores the system to the previous state, but you're saying that rollback causes manifest files in the WinSxS directory that existed before the installation to be deleted afterwards? That doesn't sound right..

Gerard.

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Fri, 12 Jan 2007 03:36:43 GMT

Gerard, you should generally not install the extracted MSP. As documented in http://blogs.msdn.com/heaths/archive/2006/10/06/VS-2005-SP1-Tries-to-Install-Multiple-Times.aspx, the patch may apply to multiple products and needs to apply to each. The wrapper makes sure it does. You can put the EXE on a network share, but it will still make local copies as documented in http://blogs.msdn.com/heaths/archive/2006/10/06/VS-2005-SP1-Requires-a-lot-of-Disk-Space.aspx.

We've tested on systems with less than the recommended memory and it works because of virtual memory. On Windows Server 2003 there is often more fragmented memory so there is not enough contiguous memory for SAFER to work as designed and implemented on XP and 2003. Even though hash algorithms like SHA1 and MD5 are block algorithms, XP and 2003 read the whole file into memory while Vista streams it. This is also mentioned in several posts, including http://blogs.msdn.com/heaths/archive/2006/08/23/715558.aspx when I first mentioned this problem.

Adding physical memory won't necessarily help. How processes allocate memory matters.

We are working on getting a fix on XP and 2003 as mentioned in this post under the "error 1718" heading but risk is always a factor.

re: Known Issues with Visual Studio 2005 Service Pack 1

IDisposable — Fri, 12 Jan 2007 08:28:03 GMT

Any chance you can give us some guidance as to how and when we can dump the patch cache... I'm a little annoyed by the enormity of my cache for a while.

re: Known Issues with Visual Studio 2005 Service Pack 1

Todd Derscheid — Fri, 12 Jan 2007 18:16:22 GMT

Regarding error 1718:

"Starting with Windows XP, a software restriction policy known as SAFER was introduced as a preventative measure to help avoid running unsafe files. Both Windows XP and Windows Server 2003 require enough contiguous memory to check files, and Windows Server 2003 seems to fragment memory more heavily leading to this error message. "

In other words, it would be better to reboot the machine with fewer programs/services running, especially W3P services or other activities likely to cause high virtual memory use, right? The longer the server runs, the more fragmented the virtual memory becomes, correct?

Would setting any of the HeapDeCommit-related registry keys on Windows Server 2003 to higher values help this? How high would be recommended?

re: Known Issues with Visual Studio 2005 Service Pack 1

Chris W — Fri, 12 Jan 2007 19:12:56 GMT

Heath, I notice issues with Reporting Services in VS2005 (using ver: 8.0.50727.42) when using date parameters - when I click view report in the preview pane having entered 12/01/2007 (I'm all set up for UK date format), it changes the parameter to 01/12/2007 and the report shows 1st Dec instead of 12th Jan. If I click view report again, it swaps it around again and shows 12th Jan on the report. The Language settings on the report are set to English (United Kingdom), and if I actually deploy the report rather than previewing it, it works fine.

I have tried this on a number of machines and other people also seem to be experiencing the same problem. Is this something that is being fixed in VS 2005 SP1 or is it something being looked at if it isn't in SP1???

Many thanks

Contradicatory statements

Unbelievable — Fri, 12 Jan 2007 19:31:15 GMT

"Windows Installer is a robust, transaction installation"

"because of the rollback, products that depend on VC may be broken"

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Fri, 12 Jan 2007 19:57:22 GMT

Todd, we have not explored options for dictating how and how much memory is allocated for processes. Rebooting with fewer services running may help, but is not absolutely going to fix the problem.

Chris, any problems related to how the products works (or doesn't) should be address in the appropriate MSDN forum (http://forums.microsoft.com/msdn) or via Microsoft Connect (http://connect.microsoft.com). I deal with the setup and servicing of the product.

Unbelievable, Windows Installer is a robust transactional installation engine - but like all things - custom code or wacky implementations can break that. Just as P/Invoke and certain types of faults can break managed apps, custom actions in Windows Installer or violating rules that ICEs would usually catch (they can't catch everything, especially in the case of custom actions) will break such features of Windows Installer. This is the case for the VC WinSxS assemblies in Whidbey.

re: Known Issues with Visual Studio 2005 Service Pack 1

MSIrable — Fri, 12 Jan 2007 21:13:50 GMT

"Windows Installer is a robust transactional installation engine - but like all things - custom code or wacky implementations can break that"

Made my day... So what's the wacky implementation? The original installation or SP1? :) Just teasing. I installed it in 3 machines without a problem.

re: Known Issues with Visual Studio 2005 Service Pack 1

mikeb — Fri, 12 Jan 2007 23:27:19 GMT

>> In other words, it would be better to reboot the machine with fewer programs/services running, especially W3P services or other activities likely to cause high virtual memory use, right? <<

Since each process has its own virtual memory address space, reducing the number of processes should not have an effect on this (except that you may have performance improvement due to to less frequent swapping).

It seems to me that setting the boot.ini /3GB option might help, since it would increase the address space available to the process that performs the SAFER check, although that process would have to be be flagged as a /LARGEADDRESSAWARE application. Unfortunately, msiexec.exe does not have that flag set (WinXP SP2), and I assume that that's the process context that the SAFER check is happening in.

I wonder if using "editbin /largeaddressaware msiexec.exe" might help? Of course there would be System File Protection to deal with, not to mention venturing into completely unsupported and untested territory for MSI...

Probably best just to leave VS 2005 SP1 alone.

>> We've tested on systems with less than the recommended memory and it works because of virtual memory. On Windows Server 2003 there is often more fragmented memory so there is not enough contiguous memory for SAFER to work as designed and implemented on XP and 2003 <<

Problemi nell'installazione del Service Pack 1 di Visual Studio 2005

Around and About .NET World — Sun, 14 Jan 2007 22:11:03 GMT

Ah the joys of Installing Visual Studio 2005 Service Pack 1

Chris Wojahn's Blog — Sat, 20 Jan 2007 00:54:02 GMT

With the start of the New Year comes new updates and features in Visual Studio 2005 and Visual Studio

安裝 Visual Studio 2005 Sp1 Known Issues

Refines.Info["Polo Lee"] — Sun, 21 Jan 2007 09:49:58 GMT

安裝 SP1. 有時候並沒有想像中的順利... Known Issues with Visual Studio 2005 Service Pack 1 Make sure u have read this

re: Known Issues with Visual Studio 2005 Service Pack 1

John Dougrez-Lewis — Fri, 26 Jan 2007 09:21:58 GMT

To misquote Juvenal' Satires:

"Who fixes the bugs in the bug fix install?"

re: Known Issues with Visual Studio 2005 Service Pack 1

Toby Kraft — Fri, 26 Jan 2007 19:29:40 GMT

Well FWIW I'm giving up on installing SP1 on our W2K3/SP1 systems. I think we'll convert these to XP.

I followed kb925336 and login as local admin.

I had 2.4GB free space on C: to start.

I keep getting error 2908 and drive C: still has 1GB free.

By the way, windows\installer still has the 466MB msp file left over after a failed install - this is way 500MB or so vanishes after every failed attempt.

Toby

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Sat, 27 Jan 2007 05:41:19 GMT

Toby, KB925336 doesn't work for all systems. Please see http://blogs.msdn.com/heaths/archive/2007/01/11/workaround-for-error-1718.aspx for a workaround that will work for all systems and why the KB didn't always work.

re: Known Issues with Visual Studio 2005 Service Pack 1

Toby — Wed, 31 Jan 2007 17:51:08 GMT

Heath, thanks for the reply. The many attempts on SP1 left the system unstable (2908 errors, .net 2.0/3.0 unstable, unable to do repair, etc). What we ended up doing was deleting the \system32\WinSxS directory contents and reinstalling the .net 2.0 framework and apps. The system is now running okay again and we're regrouping on how to proceed.

Is vs2005/SP1 really supported on W2k3 server or do you recommend running on XP?

Thanks,

Toby

tkraft-<-at->-ksainc.com

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Thu, 01 Feb 2007 07:25:28 GMT

Toby, it is supported on Win2K3. Plenty of people have installed it and we did test it, but the only error specific to Win2K3 that we know of is the common occurance of Windows Installer error 1718, for which I have published a couple of different workarounds.

Glad you got things going again.

How to Safely Delete Orphaned Patches

Heath Stewart's Blog — Thu, 01 Feb 2007 08:16:38 GMT

If Visual Studio 2005 Service Pack 1 fails to install, you might find additional .msp files under %WINDIR%\Installer

Visual Studio 2005 Service Pack 1 Rollback Breaks Some Applications

Heath Stewart's Blog — Tue, 06 Feb 2007 04:55:27 GMT

When installing Visual Studio 2005 Service Pack 1 , there are a number of errors that might occur due

Visual Studio 2005 SP1 failures can break existing applications

Aaron Stebner's WebLog — Tue, 06 Feb 2007 07:36:31 GMT

I have heard from a couple of customers who tried to install Visual Studio 2005 SP1 , only to have it

re: Known Issues with Visual Studio 2005 Service Pack 1

Prakash — Tue, 06 Feb 2007 08:06:14 GMT

The only thing I fail to understand is what does VS SP1 do? It takes much more time (at least 5 and it is still running) than installing VS itself. It is simply insane where it takes more time than installing Windows XP itself! May be it's sub-standard patch - the quality seems to deteriorate these days.

re: Known Issues with Visual Studio 2005 Service Pack 1

ABM — Tue, 06 Feb 2007 20:37:12 GMT

Almost a month later, and still no SAFER fix? I'm also shocked after reading about the .NET2.0 destruction that is left behind for some people after this patch tries to uninstall itself. I definately agree with the previous poster regarding patches. On top of that, I wonder whether it was a good idea to keep this patch out in public with these bugs still unfixed (and undocumented in the error messages). I wonder how many people there are who have wasted hours trying to deal with this? I love Visual Studio 2005 and believe it is light-years above Visual Studio 2003 and competitors. That is the one reason why I am so frustrated (so no disrespect to the developers).

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Wed, 07 Feb 2007 01:02:00 GMT

ABM, I had updated this article to address the application issues because of some problems installing and rolling back VC8 assemblies. Read http://blogs.msdn.com/heaths/archive/2007/02/05/visual-studio-2005-service-pack-1-rollback-breaks-some-applications.aspx for details and workarounds.

re: Known Issues with Visual Studio 2005 Service Pack 1

ABM — Thu, 08 Feb 2007 00:29:03 GMT

I never expected a response this quickly, so for that I am very appreciative. Though I am still unable to get the patch to install (I don't have permission to rejoin domains), I still appreciate the enormous amount of information and analysis you have provided on your blog. Also, after reading some technical articles about how these patches work, I can see that this process is rather high-tech and therefore non-trivial to troubleshoot. I therefore apologize for my frustrations and will wait patiently for a fix to this specific issue.

re: Known Issues with Visual Studio 2005 Service Pack 1

Dmitri — Thu, 15 Feb 2007 00:52:53 GMT

ABM, I don’t think you should disconnect from domain. I change SAFER registry setting and adjust Software Restriction Policies. After that I unplug my network cable, reboot my Win2003 R2 server and login as local administrator. After that I was able to install SP1. Hope this will help.

Visual Studio 2005 and .NET Framework 2.0 Setup Troubleshooting Guide

Aaron Stebner's WebLog — Sat, 17 Feb 2007 05:35:33 GMT

Where to get Visual Studio 2005 and the .NET Framework 2.0 Where to download the .NET Framework 2.0 redistributable

re: Known Issues with Visual Studio 2005 Service Pack 1

coach007 — Wed, 21 Feb 2007 00:01:49 GMT

Don't you know where to get VS 2005 and .net framework.

You are a disgrace and disaster

re: Known Issues with Visual Studio 2005 Service Pack 1

Rich — Fri, 23 Feb 2007 20:09:50 GMT

I haven't got anywhere near enough space on my 'system' partition but I have loads free in other paritions, can I force the installer to use them ?

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Sat, 24 Feb 2007 01:01:26 GMT

Rich, no you cannot but you can try to clean-up orphaned files under %WINDIR%\Installer if you have any. Read http://blogs.msdn.com/heaths/archive/2007/01/31/how-to-safely-delete-orphaned-patches.aspx.

re: Known Issues with Visual Studio 2005 Service Pack 1

Rich — Mon, 26 Feb 2007 16:08:11 GMT

Heath, thanks for the quick response, I'll try but I fear this may not be enough - the partition is only 10Gb total and since the SP needs 6Gb+ it's going to be tight!

re: Known Issues with Visual Studio 2005 Service Pack 1

Rich — Tue, 27 Feb 2007 14:44:42 GMT

ok, finally managed to install it with <2Gb of space ! This (http://blogs.msdn.com/heaths/archive/2006/11/28/save-time-and-space-for-vs-2005-sp1-by-disabling-the-patch-cache.aspx) was extremely helpful, thanks :-)))

Visual Studio 2005 Service Pack 1 Update for Windows Vista 開放下載

Refines.Info["Polo Lee"] — Wed, 07 Mar 2007 05:11:56 GMT

針對 Vista 上的 VS 2005 開發工具相容性套件終於推出了，算一算 VS 2005 自上市以來已經有了幾個不同版本的 update 套件在這裡整理一下，同時也建議一下安裝的順序與相關的資訊

Visual Studio 2005 Service Pack 1 is Hot – Maybe too Hot

Heath Stewart's Blog — Wed, 07 Mar 2007 05:22:55 GMT

Visual Studio 2005 Service Pack 1 is a big release with many fixes and lots of new features. But with

Visual Studio 2005 Service Pack 1 Update for Windows Vista Available

Heath Stewart's Blog — Wed, 07 Mar 2007 16:09:10 GMT

As Aaron notes , the Visual Studio 2005 Service Pack 1 Update for Windows Vista is available on the download

Visual Studio 2005 Service Pack 1 Bug with Typed Datasets

Craig Miles — Tue, 13 Mar 2007 17:31:15 GMT

I am having the same problem as the one described in http://forums.asp.net/thread/1587696.aspx

I can't believe that VS 2005 SP1 can have completely broken typed datasets (.XSDs) for all development sites!?

So what is the solution to the problem for the few people reporting it?

Either that or there really are a very small number of sites who are:

a) Using VS 2005 SP1

b) Using typed datasets

c) Have needed to make a change post install of SP1

Any assistance on this would be gratefully received.

re: Known Issues with Visual Studio 2005 Service Pack 1

Vivek — Wed, 14 Mar 2007 04:34:20 GMT

I get error message

"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 and that you have the correct upgrade patch."

What I have done is, install VS2005 professionsl on a fresh Vista machine and then try to install SP1.

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Thu, 15 Mar 2007 03:37:11 GMT

Vivek, make sure you have downloaded the correct Service Pack package for the right language of Visual Studio 2005 that you have installed. You can also extract the MSP from the EXE by using the /extract switch, then use my Patch Applicability Browser at http://blogs.msdn.com/heaths/articles/pab.aspx to see what products it applies to, and which of those are installed.

re: WAP Known Issues with Visual Studio 2005 Service Pack 1

Christopher Rannow — Thu, 29 Mar 2007 21:51:12 GMT

Heath,

Someone earlier in your blog mentioned a problem with WAP. I have several projects built originally using the WAP pre SP1. Now after un-installing WAP so that I could install SP1 to fix other issues, dragging controls of any kind onto a page in either source mode or designer mode the control isn't being declared in the designer.vb Any thoughts?

re: Known Issues with Visual Studio 2005 Service Pack 1

seada — Thu, 05 Apr 2007 17:06:03 GMT

when installing visual studio 2005

having the operating system windows xp sp2

i get error saying suite integration toolkit excutable has encountered a problem and needs to close. what shall i do?

re: Known Issues with Visual Studio 2005 Service Pack 1

Heath Stewart — Fri, 06 Apr 2007 01:20:34 GMT

Sorry seada, but I can't really provide much help with application issues. I recommend visiting http://forums.microsoft.com/msdn and post your question there. The product groups typically monitor the threads. You could also file a bug in http://connect.microsoft.com. If you go that route, I recommend you generate a verbose log by passing "/L*vx+ logname.log" (without quotes), ZIP, and attach that to the bug.

If you've tried to install this patch before and it failed, it's possible the VC runtime is broken. Read http://blogs.msdn.com/heaths/archive/2007/02/05/visual-studio-2005-service-pack-1-rollback-breaks-some-applications.aspx for details on that.

Hotfix Published for KB925336

Heath Stewart's Blog — Tue, 24 Apr 2007 23:42:45 GMT

When installing Visual Studio 2005 Service Pack 1 , users may see an error that reads, Error 1718.File

How to Install TFC without PPE

Heath Stewart's Blog — Tue, 20 Nov 2007 20:07:29 GMT

Microsoft Visual Studio 2008 , now available for MSDN subscribers and Express editions freely available

How to Install TFC without PPE

Noticias externas — Tue, 20 Nov 2007 20:43:57 GMT

Microsoft Visual Studio 2008 , now available for MSDN subscribers and Express editions freely available

【日本語版】 Visual Studio 2005 SP1 の既知の問題

Microsoft Japan Forum Operators Blog — Mon, 20 Oct 2008 09:46:44 GMT

こんにちは！フォーラムオペレーターの服部清次です。ここ最近、 MSDN フォーラムの「よくある質問」へのアクセスがだんだん増えてきています。 (^_^)v これからも、皆さんにとって有益な情報をドシドシ載せていきたいと思います！