How to Workaround Error 1330 During Visual Studio 2008 Installation

klaudek » How to Workaround Error 1330 During Visual Studio 2008 Installation

klaudek » How to Workaround Error 1330 During Visual Studio 2008 Installation — Sat, 15 Dec 2007 07:24:34 GMT

PingBack from http://klaudek.adoption23.info/2007/12/14/how-to-workaround-error-1330-during-visual-studio-2008-installation/

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Bryan — Mon, 14 Jan 2008 12:05:44 GMT

I downloaded VS2008 using Microsoft's download manager. The install worked perfectly n two of my machines and doesn't work at all on the third, returning error 1330. I've tried replacing the specified cab file in the install folder. Then it returns with error 1330 with the next cab file. What I fail to understand is why the instal doesn't work on a particular machine.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Tue, 15 Jan 2008 03:40:34 GMT

Bryan, did you copy these from machine to machine or just download them again?

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Morgan Gardiner — Wed, 30 Jan 2008 20:17:04 GMT

I have the same Problem as Bryan.

I have installed the Visual Studio 2008 fine on 2 machines. the MSDN however installed fine on one machine and not on another. How do I get this installed?

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Thu, 31 Jan 2008 02:13:51 GMT

Morgan, did you try copying the files manually? MSDN in particular has a very large CAB - around 200MB. Moving this to local media should typically help.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Tim McCurdy — Wed, 13 Feb 2008 23:56:38 GMT

Same for me. I have downloaded every single ISO from MS and none of them will install. I've extracted all files to the local HD for installing and still the same. Mine all bomb out on cab1.cab during the installation of VS 2008.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Thu, 14 Feb 2008 01:01:29 GMT

It might help to close down all running processes that you can. A similar issue with VS 2005 SP1 was exhausted memory or not enough contiguous virtual memory. The latter can be worked around by changing optimization from background services to running apps in your System configuration panel.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Wed, 20 Feb 2008 11:22:30 GMT

I have an ISO which when mounted with Daemon Tools allows me to install fine on one machine (XP SP2), however on another (XP SP2 as well) it fails consistently with 1330 on cab1.cab during installation of the VS2008 component. Note that the CAB files for this component are at most 50Mb, and cab1.cab in particular is only 16Mb. The larger cab files talked about above are only for the MSDN installation.

I've tried:

a) Copying ISO to HDD, mounting with daemon tools - same problem.

b) Extracting ISO to same HDD as I'm installing to and a secondary HDD in the same machine - both result in the error.

c) Burning ISO to DVD and installing off the disk - same problem.

d) Copying ISO to a network server, mounting using daemon tools - same problem.

e) Extracting ISO to HDD and burning the files directly to DVD and installing off the disk (effectively the same as (c)) - same problem.

If you ask me, in the year 2008, we should NOT be seeing issues like "files not being fully read", especially of this size (Mb not Gb), and when they are stored on a local HDD. Clearly there is a weakness in the code that is reading these CAB files.

Is there anything else I can try?

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Wed, 20 Feb 2008 21:19:16 GMT

Mr. Bungle - or anyone running into this problem - can you try to run the following on the file that fails and let me know if it also fails. If you don't have signtool.exe, you can download it as part of the Windows Installer SDK. That installs by default with Visual Studio so on the machine where it installed you can grab it.

signtool verify /pa /v <path to cab>

The last line should say whether it succeeded or failed, and the verbose spew should contian more information.

If we can isolate the problem we can more easily track it down.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

TechnoDex — Thu, 21 Feb 2008 06:03:44 GMT

Downloaded via MSDN Download Manager then burned ISO to DVD.

C:\Program Files\Microsoft Visual Studio 8\VC>signtool verify /pa /v "d:\cab11.cab"

Verifying: d:\cab11.cab

SignTool Error: WinVerifyTrust returned error: 0x80096010

The digital signature of the object did not verify.

Signing Certificate Chain:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 12/31/2020 1:00:00 AM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Code Signing PCA

Issued by: Microsoft Root Authority

Expires: 8/25/2012 1:00:00 AM

SHA1 hash: 3036E3B25B88A55B86FC90E6E9EAAD5081445166

Issued to: Microsoft Corporation

Issued by: Microsoft Code Signing PCA

Expires: 2/22/2009 6:33:13 PM

SHA1 hash: D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1

The signature is timestamped: 11/8/2007 3:21:03 PM

Timestamp Verified by:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 12/31/2020 1:00:00 AM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Timestamping PCA

Issued by: Microsoft Root Authority

Expires: 9/15/2019 1:00:00 AM

SHA1 hash: 3EA99A60058275E0ED83B892A909449F8C33B245

Issued to: Microsoft Timestamping Service

Issued by: Microsoft Timestamping PCA

Expires: 6/12/2012 6:04:51 PM

SHA1 hash: F9B6EB0ACFFB8DC1B836EE16711BFF423CA1D573

SignTool Error: File not valid: d:\cab11.cab

Number of files successfully Verified: 0

Number of warnings: 0

Number of errors: 1

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Thu, 21 Feb 2008 14:08:04 GMT

Thanks Heath. I put signtool.exe v6.0.6000.16384 and cab50.cab (the smallest cab file - 3Mb) on a USB key and tried that command on the two PCs. As expected, it was verified on one, but not the other. So it is not a problem with the installation media. I'm betting it's a windows update thing - I must be missing an update that is needed for WinVerifyTrust to work. Here's the output I got:

Windows version: 5.1 (Build 2600.xpsp_sp2_qfe.070227-2300 : Service Pack 2)

E:\Windows SDK 6.0A>signtool verify /pa /v cab50.cab

Verifying: cab50.cab

SHA1 hash of file: 5FF0953EE89C5C8ACDB90D72B8F52B0B3F79EFED

Signing Certificate Chain:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Code Signing PCA

Issued by: Microsoft Root Authority

Expires: 25/08/2012 6:00:00 PM

SHA1 hash: 3036E3B25B88A55B86FC90E6E9EAAD5081445166

Issued to: Microsoft Corporation

Issued by: Microsoft Code Signing PCA

Expires: 23/02/2009 11:33:13 AM

SHA1 hash: D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1

The signature is timestamped: 9/11/2007 8:33:02 AM

Timestamp Verified by:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Timestamping PCA

Issued by: Microsoft Root Authority

Expires: 15/09/2019 6:00:00 PM

SHA1 hash: 3EA99A60058275E0ED83B892A909449F8C33B245

Issued to: Microsoft Timestamping Service

Issued by: Microsoft Timestamping PCA

Expires: 16/09/2011 1:05:22 PM

SHA1 hash: A2D57D63CF331B177BE147088FEABEC7388BE01D

Successfully verified: cab50.cab

Number of files successfully Verified: 1

Number of warnings: 0

Number of errors: 0

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Windows version: 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158 : Service Pack 2)

I:\Windows SDK 6.0A>signtool verify /pa /v cab50.cab

Verifying: cab50.cab

SHA1 hash of file: 5FF0953EE89C5C8ACDB90D72B8F52B0B3F79EFED

SignTool Error: WinVerifyTrust returned error: 0x800B010E

The revocation process could not continue - the certificate(s) could not be checked.

Signing Certificate Chain:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Code Signing PCA

Issued by: Microsoft Root Authority

Expires: 25/08/2012 6:00:00 PM

SHA1 hash: 3036E3B25B88A55B86FC90E6E9EAAD5081445166

Issued to: Microsoft Corporation

Issued by: Microsoft Code Signing PCA

Expires: 23/02/2009 11:33:13 AM

SHA1 hash: D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1

The signature is timestamped: 9/11/2007 8:33:02 AM

Timestamp Verified by:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Timestamping PCA

Issued by: Microsoft Root Authority

Expires: 15/09/2019 6:00:00 PM

SHA1 hash: 3EA99A60058275E0ED83B892A909449F8C33B245

Issued to: Microsoft Timestamping Service

Issued by: Microsoft Timestamping PCA

Expires: 16/09/2011 1:05:22 PM

SHA1 hash: A2D57D63CF331B177BE147088FEABEC7388BE01D

SignTool Error: File not valid: cab50.cab

Number of files successfully Verified: 0

Number of warnings: 0

Number of errors: 1

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

TechnoDex — Thu, 21 Feb 2008 18:43:07 GMT

Same thing occurs on the MSDN Library disk downloaded the same way.

C:\Program Files\Microsoft Visual Studio 8\VC>signtool verify /pa /v "d:\cab8.cab"

Verifying: d:\cab8.cab

SignTool Error: WinVerifyTrust returned error: 0x80096010

The digital signature of the object did not verify.

Signing Certificate Chain:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 12/31/2020 1:00:00 AM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Code Signing PCA

Issued by: Microsoft Root Authority

Expires: 8/25/2012 1:00:00 AM

SHA1 hash: 3036E3B25B88A55B86FC90E6E9EAAD5081445166

Issued to: Microsoft Corporation

Issued by: Microsoft Code Signing PCA

Expires: 2/22/2009 6:33:13 PM

SHA1 hash: D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1

The signature is timestamped: 11/8/2007 12:04:46 AM

Timestamp Verified by:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 12/31/2020 1:00:00 AM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Timestamping PCA

Issued by: Microsoft Root Authority

Expires: 9/15/2019 1:00:00 AM

SHA1 hash: 3EA99A60058275E0ED83B892A909449F8C33B245

Issued to: Microsoft Timestamping Service

Issued by: Microsoft Timestamping PCA

Expires: 9/15/2011 8:05:22 PM

SHA1 hash: A2D57D63CF331B177BE147088FEABEC7388BE01D

SignTool Error: File not valid: d:\cab8.cab

Number of files successfully Verified: 0

Number of warnings: 0

Number of errors: 1

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Fri, 22 Feb 2008 00:30:14 GMT

Can any of you check your performance settings, to see if the failed machines are set for Background Service Optimization? Also, are these Win2K3 machines or what platform are they?

On Vista: "Start"->Right click on Computer, select Properties. On the left, select "Advanced System Properties", click "Settings" under "Performance", then click the "Advanced" tab. Is "Programs" or "Background services" checked.

Prior to Vista: basically same instructions as above, but in System Properties click on the "Advanced" tab.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Fri, 22 Feb 2008 14:37:51 GMT

As above:

Windows version: 5.1 (Build 2600.xpsp_sp2_qfe.070227-2300 : Service Pack 2) - Works

Windows version: 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158 : Service Pack 2) - Fails

Both machines have 'Programs' checked under 'Processor scheduling'.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Fri, 22 Feb 2008 15:06:16 GMT

Probably worth noting that in your original post, you refer to error code 0x80092003 being returned from WinVerifyTrust. However in my case it's 0x800B010E and in TechnoDex's it's 0x80096010.

0x80092003 = CRYPT_E_FILE_ERROR

0x800B010E = CERT_E_REVOCATION_FAILURE

0x80096010 = TRUST_E_BAD_DIGEST

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Sun, 24 Feb 2008 06:01:44 GMT

While this doesn't have the same symptoms as what was causing error 1718 for VS 2005 SP1 it's possible the underlying cause is the same. Also was recommended the second KB article below. Please try to apply one or both of these hotfixes and try again.

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

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

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Sun, 24 Feb 2008 23:29:12 GMT

KB 925336: A supported fix is available for Windows Server 2003. There is no fix available for Windows XP. I already tried the manual workaround (both PolicyScope = 1, and then changing the local security policy) and the problem still occurred.

KB 938759: Again this hotfix only applies to Windows 2003 Server. Also, this problem typically occurs when the signed file is larger than 500 megabytes. I don't think 3Mb qualifies as a 'large file'.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Heath Stewart — Thu, 28 Feb 2008 04:09:36 GMT

Mr. Bungle, thanks for your help in diagnosing this. Could you export your registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0', and use http://blogs.msdn.com/heaths/contact.aspx to contact me. I'll reply and you'll have my address that way.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mark — Thu, 28 Feb 2008 19:21:51 GMT

Here is what I figured out..

I tried the things suggested here and it did not work. I ran scan disk and defrag and that seemed to do it. The installation has no problems now.

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Mr. Bungle — Sun, 02 Mar 2008 13:46:18 GMT

Not sure what error code you were getting from WinVerifyTrust Mark (because it looks like there are potentially different causes for 1330), but I just did a defrag and scandisk on all my hdds and unfortunately I still can't install :(

re: How to Workaround Error 1330 During Visual Studio 2008 Installation

Gordon — Wed, 12 Mar 2008 03:39:40 GMT

I'm experiencing the same problem but with MSDN Library for VS2008, it keeps complaining about the digital signature for cab2.cab.

This is the output I'm getting from signtool.exe:

Verifying: cab2.cab

SignTool Error: WinVerifyTrust returned error: 0x80096010

The digital signature of the object did not verify.

Signing Certificate Chain:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Code Signing PCA

Issued by: Microsoft Root Authority

Expires: 25/08/2012 6:00:00 PM

SHA1 hash: 3036E3B25B88A55B86FC90E6E9EAAD5081445166

Issued to: Microsoft Corporation

Issued by: Microsoft Code Signing PCA

Expires: 23/02/2009 11:33:13 AM

SHA1 hash: D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1

The signature is timestamped: 8/11/2007 5:05:16 PM

Timestamp Verified by:

Issued to: Microsoft Root Authority

Issued by: Microsoft Root Authority

Expires: 31/12/2020 6:00:00 PM

SHA1 hash: A43489159A520F0D93D032CCAF37E7FE20A8B419

Issued to: Microsoft Timestamping PCA

Issued by: Microsoft Root Authority

Expires: 15/09/2019 6:00:00 PM

SHA1 hash: 3EA99A60058275E0ED83B892A909449F8C33B245

Issued to: Microsoft Timestamping Service

Issued by: Microsoft Timestamping PCA

Expires: 16/09/2011 1:05:22 PM

SHA1 hash: A2D57D63CF331B177BE147088FEABEC7388BE01D

SignTool Error: File not valid: cab2.cab

Number of files successfully Verified: 0

Number of warnings: 0

Number of errors: 1

I got the MSDN Library for VS 2008 from Microsoft Downloads and burnt the ISO image to DVD. I've tried copying all the files to the local HDD and running setup from there but still the same issue. Also tried defragmenting my HDD but still not working. I also tried the workaround published in Q925336 but no joy there either.

Maybe I need to try downloading the ISO again.

Installing Visual Studio 2008 on Windows Server 2008

Hartmut's Box — Tue, 25 Mar 2008 00:07:43 GMT

Today I’ve had a hard time installing Visual Studio 2008 on Windows Server 2008. I finally wanted to test WCF hosting within WAS. The installation broke several times with Error 1330: "… d:\cab11.cab has an invalid digital signature …"

Another Possible Workaround for Error 1330

Heath Stewart's Blog — Fri, 12 Dec 2008 01:11:18 GMT

When installing Visual Studio 2008, you might run into an error dialog that reads, Error 1330.A file

Visual Studio 2008: instalación y primeros pasos

Un informático en construcción — Mon, 05 Jan 2009 03:22:22 GMT

Nivel: Inicial Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub A pesar de

Visual Studio 2008: instalación y primeros pasos

Coordinator's Speak Point — Mon, 05 Jan 2009 03:33:14 GMT

Nivel: Básico Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub   A pesar

Visual Studio 2008: instalación y primeros pasos

Miemblogs — Mon, 05 Jan 2009 03:55:12 GMT

Nivel: Básico Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub A pesar de llevar

Visual Studio 2008: instalación y primeros pasos

Coordinator's Speak Point — Mon, 05 Jan 2009 04:06:18 GMT

Nivel: Básico Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub   A pesar

Visual Studio 2008: Σφάλμα κατά την εγκατάσταση - “Error 1330: cabinet file has invalid digital signature”

Καπνιάς Γιώργος — Thu, 12 Mar 2009 03:52:17 GMT

Μια από τις συνήθειες που έχω αποκτήσει με τον καιρό - από την μία λόγω του εύκολου και φτηνού Virtualization που υπάρχει για τα Windows, και από την άλλη η χαρά να μην καταστρέφω τον προσωπικό μου υπολογιστή κάθε φορά που θέλω να ξεκινήσω ένα καινούργιο

Error 1330 Installing Visual Studio 2010

Omar Villarreal's Blog — Wed, 20 May 2009 10:10:56 GMT

This is apparently a known issue and I seem to remember I saw this issue a long time ago. I was installing