Error 1330 Java Windows 2008

Setup & Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual java windows server 2008 Studio Team Services All Languages Visual C++ Visual F# JavaScript TypeScript

Java For Windows 2008 R2 64 Bit

Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform Development

Java Windows 7

Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows

Java Windows 2003

Installer, the .NET Framework, and Visual Studio. Another Possible Workaround for Error 1330 ★★★★★★★★★★★★★★★ December 11, 2008 by Heath Stewart (MSFT) // 12 Comments 0 0 0 When installing Visual Studio 2008, you might run into an error dialog that reads, Error 1330.A file that is required cannot be installed because the cabinet file D:\cab1.cab java windows vista has an invalid digital signature. This may indicate that the cabinet file is corrupt. The path and name of the cabinet may be different, but might often be D:\cab1.cab, where D: refers to your DVD drive. How to workaround this issue Some time ago I blogged that you should try copying the installation locally as in some cases this is related to brief network disconnects or disc read lag, or even a bad burn of an ISO image. You should still try that and other methods in some of the comments on that post first since those are for more likely problems. If you do not have Internet access, or have a restrictive firewall or proxy, setup may be failing to verify the signature because it cannot access the online certificate revocation list (CRL). This is most likely if you encounter the error on cab1.cab for VS2008 or MSDN. You’ll need a copy of setreg.exe which is available in the .NET Framework

(Error1330) For security reasons, our network is completely disconnected from the Internet.  And I mean completely… we are not allowed to connect, ever.  In this situation, you quickly realize almost every vendor assumes you have java windows 2000 Internet access (really? people still assume) and management of your network becomes harder by an windows install java order of magnitude. As an example, earlier this week, I was trying to create an install package for the latest JRE, error 1330 invalid digital signature version 6 update 21.  I ended up getting an error 1330, invalid digital signature in data1.cab during the installation process.  After some research, I came across the following forum posts: http://forums.sun.com/thread.jspa?threadID=5403715 and http://forums.sun.com/thread.jspa?threadID=5380073 EDIT: Sorry, https://blogs.msdn.microsoft.com/heaths/2008/12/11/another-possible-workaround-for-error-1330/ I know these links are broken, but Oracle changed the forum structure when Sun got gobbled by them and I haven't had the time, or patience, to find where they went.  Personally, I consider this an HFE failure (the fact that the links broke when the site was migrated).  Shame on you Oracle. Based on our connectivity (or lack of it), I realized this was due to the fact https://windowshell.wordpress.com/2010/09/10/java-runtime-installation-failure-error-1330/ that JRE has a CAB file that uses a VeriSign code signing certificate that is NOT part of the Microsoft Root CA list.  To make matters worse, the CAB wants to run a CRL check that goes back to VeriSign.  After fiddling around trying different security options to bypass the CRL check, I finally gave up and went another way. It turns out, that this issue only affects the JRE installer that is available for general consumer download.  The JDK, on the other hand, has a copy of the JRE as part of the package that doesn't have this issue.  The bad part, is that the JDK makes you install, well, JDK stuff in addition to the JRE (which is an option).  Of course, I took this on as a challenge to split out the JRE as a standalone installer. Most installers work the same way.  You download a single file and the file extracts all of the actual installation files into a temporary directory.  Since we only want the JRE from the JDK package, we will begin the install process.  Do not continue with the installer, or exit it.  Doing either action will cause the temporary files to be deleted. At this point, the files are extr

accidentally Active Directory Blog Certification PVS Web Interface Receiver Secure Gateway Presentations PowerShell XenApp XenApp 5 for Windows Server 2003 XenApp 5 for Windows Server 2008 XenApp 6 for Windows Server 2008 http://carlwebster.com/java-runtime-installation-failure-updated-for-jre-update-26/ R2 XenApp 6.5 for Windows Server 2008 R2 XenDesktop XenServer Java Runtime Installation http://support.sas.com/kb/44/155.html failure - Updated for JRE Update 26 June 30, 2011 XenApp Java Runtime Installation Failure (Error 1330) Update:  June 30, 2011.  Oracle has changed some of the screens for JRE Update 26.  This article has been updated at the bottom of the original article. When trying to install the Java Runtime Environment (JRE) java windows 6 Update 24 at a client site recently, I kept getting the error below (Figure 1): Figure 1 This is recorded in the Application Event Log as: Product: Java(TM) 6 Update 24 -- Error 1330.A file that is required cannot be installed because the cabinet file M:\Documents and Settings\_cwebster\Application Data\Sun\Java\jre1.6.0_24\Data1.cab has an invalid digital signature.  This may indicate that the cabinet file is corrupt.  error 1330 java Error 24581 was returned by WinVerifyTrust. My first thought was that the certificate revocation check might be causing the problem, but, as you will see below, the servers are configured not to check for certificate revocation (Figure 2). Figure 2 I found a discussion of this error at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6887806 .  The problem is that Data1.cab is digitally signed and the servers I am trying to update are secured servers that do not have Internet access.  Because these servers have no Internet access, they cannot verify the digital signature of Data1.cab with VeriSign.  Following the instructions in the Work Around section, I went to https://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=SO26896&pmv=print&actp=PRINT&viewlocale=en_US and created the two .cer certificate files.  I then followed the link “If you enrolled for your certificate between May 17, 2009 and October 10th, 2010 Click here for your Intermediate CA.”  This gave me a total of three .cer certificate files.  I right-clicked each file and selected Install Certificate.  Even after all this, JRE 6 Update 24 refused to install. In a past life, I was a software developer who dabbled in Java.  I remembered that the Java Development Kit includes a public version of the

Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic Program SAS OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Problem Note 44155: An invalid digital signature error occurs when you are installing the JRE 1.6.0_24 on Windows 2008 R2 Server When you are installing the Java Runtime Environment (JRE) 1.6.0_24 on a Windows 2008 R2 Server operating system, the following error might occur. The message can be from the SAS Deployment Wizard or from the Oracle website if you download the JRE from there. Error 1330. A file that is required cannot be installed because the cabinet file %temp%\Sun\Java\jre1.6.0_24\Data1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. To fix this issue, follow these steps: If you are not connected to the Internet, connect to the Internet and then try the installation again. Change two registry keys: Click Start ► Run and type regedit to open the Registry Editor window. Temporarily change the following registry key value from DisableRootAutoUpdate to DisableRootAutoUpdateX. For example: Change it from this: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\SystemCertificates\AuthRoot\ Value Name: DisableRootAutoUpdate Type: REG_DWORD Value: 1 To this: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\SystemCertificates\AuthRoot\ Value Name: DisableRootAutoUpdateX Type: REG_DWORD Value: 1 Note: After completing the installation of the JRE, restore the value back to DisableRootAutoUpdate. Disable the User Account Control (UAC) settings on your operating system. For instructions, see this Microsoft User Account Control Step-by-Step Guide. Download the Java Development Kit (JDK) 1.6.0_24 32-