• Grumpy Wookie

  • Archives

  • Top Posts

  • Recent Visitors

  • Blog Stats

    • 349,223 hits

Too big to install

When attempting to install the recently released Visual Studio 2005 Service Pack 1, there is a problem with the “digital signature” (policy).

Well – that’s what the error message says !   It even provides you with a “see this URL for more information” – no hyperlink though – re-type :

go.microsoft.com/fwlink/?linkid=73863

This jumps across to a KB article :

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

Seems that the file is “too big” – being 430 MB – and can’t be verified by the digital signature policy – can’t check the entire file (!)

Error message when you try to install a large Windows Installer package or a large Windows Installer patch package in Windows Server 2003 or in Windows XP :

When you try to install a large Microsoft Windows Installer (.msi) package or a large Microsoft Windows Installer patch (.msp) package on a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP, you receive the following error message:

Error 1718. File [FileName] was rejected by digital signature policy.

CAUSE

This problem occurs when the computer has insufficient contiguous memory for Windows Server 2003 or Windows XP to verify that the .msi package or the .msp package is correctly signed.

OK – so now what ?!?

Well – have to do a quick little registry hack (yep – that’s what Microsoft say !) – effectively turning off the Software Restriction Policy.

HKEY_LOCAL_MACHINE \ Software \ Policies \ Microsoft \ Windows \ Safer \ CodeIdentifiers

PolicyScope – change from 0 to 1

Yep – fair enough – BUT – there was no PolicyScope setting on my server – so couldn’t do [option 1] – move onto [plan B].

If the previous steps do not resolve the issue, follow these steps:

   1. Click Start, click Run, type control admintools, and then click OK.

   2. Double-click Local Security Policy.         (was “Domain Security Policy” for my stand-alone VM)

   3. Click Software Restriction Policies.    Right-click Software Restriction Policies, and then click Create New Policy.

   4. Under Object Type, double-click Enforcement.

   5. Click All users except local administrators, and then click OK.

So – that’s all there is to it.   Of course, I’ll have to remember to go and “reverse” these steps once the SP1 is complete.

Quickest & easiest is to try [option 1] first – and then [plan B] if that doesn’t work.

Don’t forget to re-boot afterwards – of course, I thought I’d try without a re-boot – and didn’t work.   *doh*

Full Article

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: