安裝Visual Studio 2005,2008都三年了，從來(lái)都沒(méi)遇到過(guò)什么問(wèn)題，安裝過(guò)程都很順利。今天給公司的新電腦裝系統(tǒng)，自帶了一個(gè)正版的Win XP家庭版，安裝VS的時(shí)候出錯(cuò)，1330錯(cuò)誤：某個(gè)文件數(shù)字簽名不可用。于是換了張光盤，結(jié)果還是同樣的結(jié)果。。。于是換系統(tǒng)，先裝Win2003，最 后到Win2008，都逃不過(guò)這個(gè)問(wèn)題，而且數(shù)字簽名不可用的文件每次都是隨機(jī)的，有時(shí)是第2個(gè)文件，有時(shí)是第60個(gè)文件。找來(lái)師哥們幫忙，他們也沒(méi)遇到 過(guò)這么怪的問(wèn)題。后來(lái)在Google上搜索"Visual Studio 1330"，找了很久，微軟MSDN版主的解釋是文件損壞，重新下載安裝。（PS：公司里的Visual Studio光盤是MSDN寄來(lái)的光盤，有20多張DVD，包括所有語(yǔ)言的版本）。還有的是讓把光盤里的文件復(fù)制到硬盤安裝。。。。測(cè)試無(wú)效。

Finally,通過(guò)Google在一個(gè)老外的博客上找到了解決方法：在注冊(cè)表中，把原HKCU\Software\Microsoft\Windows \CurrentVersion\WinTrust\Trust
Providers\Software Publishing\State 的值由 0x23c00 改為 0x22800。關(guān)閉文件數(shù)字簽名驗(yàn)證。VS順利安裝！

下面附原博客內(nèi)容：

FIX: Error 1330 - Installing Visual Studio 2008 on Windows Server 2008 VPC
OK, I have run into SO many bloody 1330 errors while installing Visual Studio 2008 on a Windows Server 2008 VPC. Here is the fix I ran across on Heath Stewart's blog.

On my host, I installed the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

I then copied SetReg to my VPC image from my host's C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin.

I then updated my SetReg settings on the VPC as is mentioned in Heath's article.

Software Publishing State Key Values (0x22800):
   1) Trust the Test Root........................... FALSE
   2) Use expiration date on certificates........... TRUE
   3) Check the revocation list..................... TRUE
   4) Offline revocation server OK (Individual)..... FALSE
   5) Offline revocation server OK (Commercial)..... TRUE
   6) Java offline revocation server OK (Individual) FALSE
   7) Java offline revocation server OK (Commercial) TRUE
   8) Invalidate version 1 signed objects........... FALSE
   9) Check the revocation list on Time Stamp Signer FALSE
10) Only trust items found in the Trust DB........ FALSE

Reran the VS2008 install and PRESTO! it worked w/ no Error 1330s.

FWIW, I am writing this down here on my blog so I have it semi-permanently for future such mishaps. :-)