Problem with installing Visual Studio on Vista

[David]

I have Visual Studio Professional (from MSDN subscription) running on my XP
Professional well.

I bought a machine with Vista Business. I tried many time to install Visual
Studio Professional, it always fails, the following is the error message:
Error 1935. An error occurred during the installation of assembly
'Microsoft.VC80.ATL,
type="win32",version='8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processArchitecture="amd64"'.
Please refer to Help and Support for more information. HRESULT: 0x80070020

Any help is most appreciated.

Thanks

 

[Mr. Arnold]

I have Visual Studio Professional (from MSDN subscription) running on my XP
Professional well.

I bought a machine with Vista Business. I tried many time to install
Visual Studio Professional, it always fails, the following is the error
message:
Error 1935. An error occurred during the installation of assembly
'Microsoft.VC80.ATL,
type="win32",version='8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processArchitecture="amd64"'.
Please refer to Help and Support for more information. HRESULT: 0x80070020

You shouldn't have a problem with the installing of VS 2005 Professional on
Vista, nromally. I had no problems installing VS 2005 Express for Web, VB
and C#.net downloads.

The 'Microsoft.VC80.ATL looks to be part of the C++ install if you check
Google.

Here is some info about that 1935 error code. Maybe, you have some kind of
conflict.

http://www.google.com/search?hl=en&q=Error+1935&btnG=Search

 

[David]

I manage to install VS2005 Express (VB) on Vista. But not VS 2005
Professional.

 

[Andrew McLaren]

Hi David,

I haven't seen this error before (haivng installed VS2005 on 20 or 30 Vista
machines, so far). Obviously something is playing up on your system but it
seems like a pretty isolated case - there are a handful of references to the
error in Google, but nothing really conclusive.

But as with *any* problem installing Visual Studio, your best bet is to look
in teh lge file whch VS2005 setup creates - verbose logging is enabled, by
default. See this KB article for details:
http://support.microsoft.com/kb/904732

The other thing I would suggest is to tun off any anti-virus, database or
other extraneous services and applications, before you start. 0x80070020 is
the standard ERROR_SHARING_VIOLATION error - meaning that some other
process has a handle to the file, so it cannot be deleted or over-written.
Presumably, something else is already usng the Microsoft.VC80.ATL assembley,
when Visual Studio tries to instal it as part of setup.

Likewise, 1935 is a fairly common setup error; Aaron Stebner from Microsoft
has some good tips on troubleshootin 1935 errors in his blog:
http://blogs.msdn.com/astebner/archive/2004/11/10/255346.aspx

Hoe this helps a bit,
Andrew

PS remember to apply VS2005 SP1 after you get Visual Studio installed; the
Service Pack includes important compatibility fixes for VS 2005 on Vista.

 

[Mr. Arnold]

I manage to install VS2005 Express (VB) on Vista. But not VS 2005
Professional.

So, was Express there when you were trying to install Professional or did
you unisnatll Express first and then tried to install Professional?

 

[David]

Thanks Andrew. The log does say something about the access right, I think
you are right. I do have symantec anti virus running. Will turn it off and
try again.

 

[David]

I tried it separately, i.e. after not able to install VS Professional, I
tried VS Express. It work for Express. Then uninstall express, and tried
again with VS 2005 Professional. It still didn't work.

 

[Mr. Arnold]

Thanks Andrew. The log does say something about the access right, I think
you are right. I do have symantec anti virus running. Will turn it off and
try again.

Yes, you should shutdown all applications AV's etc, etc background processes
and anything in the job trey when doing the install. I think it may have
made mention of that on an install screen somewhere.

 

[Peter Foldes]

Is NET framework 1.0 and 2.0 installed ? You can have this error message (error1935) installing VS 2005. If installed they can be damaged. Suggest that you install both versions again and then reboot and try your install of VS again.

 

[David]

Hi Arnold, it didn't work. I shutdown everything, firewall, anti-virus and
everything, the error still happened.

 

[David]

Hi Peter, I read from Aaron Stebner's blog that I need to rename the
mscoree.dll and re-install .Net 1 and 2. I tried renaming the file, it is
protected, I can't change the name. What is the way to uninstall .Net 1.x
and 2.0 on Windows Vista?

Is NET framework 1.0 and 2.0 installed ? You can have this error message
(error1935) installing VS 2005. If installed they can be damaged. Suggest
that you install both versions again and then reboot and try your install of
VS again.

 

[David]

Hi Peter, I read in Aaron's blog that to reinstall .Net 1.0 or 2.0, I need
to rename mscoree.dll. In Vista, I can't rename this file.

I tried to uninstall .Net 1.0 or repair .Net 2.0 installation, I can't find
way to uninstall or repair it.

Any help is most appreciated.

Is NET framework 1.0 and 2.0 installed ? You can have this error message
(error1935) installing VS 2005. If installed they can be damaged. Suggest
that you install both versions again and then reboot and try your install of
VS again.

 

[Andrew McLaren]

Hi Peter, I read from Aaron Stebner's blog that I need to rename the
mscoree.dll and re-install .Net 1 and 2. I tried renaming the file, it is
protected, I can't change the name. What is the way to uninstall .Net 1.x
and 2.0 on Windows Vista?

You can't uninstall .NET Framework 2.0 from Vista - it is part of the core
OS and is installed by Vista during the initial setup.

There is an option to uninstall .NET 3.0 in Control Panel Programs, Turn
Windows Features On/Off; but this only removes the 3.0 extensions, it
doesn't remove any of the core 2.0 files (Mscoree.dll being the most "core"
of them all!). The only way to repair .NET Framework 2.0 is by doing a Vista
Repair - ie, boot from the Vista DVD and select the option to Repair,
instead of Install. This will then check the integrity of all the Vista
files and replace any which are missing or damaged.

Did you examine the Visual Studio setup logs, as described in the 904732 KB
article? What did they report for the point of failure? These logs will give
you a LOT more precise information, about what actually went wrong.

(BTW a quick trawl in Google and the KB doesn't show many hits for this
particular error. So while your problem is genuine, it may be a little bit,
uh, idiosyncratic)

Andrew