VS2017安装程序 - 程序包清单签名验证失败

时间:2017-05-24 13:39:38

标签: visual-studio visual-studio-2017

我安装了VS2015,之前在这台机器上安装了VS2017。在VS2017上添加扩展似乎完全破坏了我的安装,所以我认为接下来要做的就是重新安装VS2017。

哦,我希望自己没有。

安装程序失败了“包清单失败签名验证”我尝试了以下步骤:

运行安装程序时,我看到:

enter image description here

甚至在选择要安装的产品之前。

尝试按https://www.hanselman.com/blog/HowToMakeAnOfflineInstallerForVS2017.aspx

处的“离线安装程序”步骤时

在我跑步的步骤:

vs_community.exe --layout e:\vs2017offline --lang en-US

我最终获得了一个控制台窗口:

enter image description here

安装的日志文件。

dd_setup _ *日志:

[0df4:000c][2017-05-24T08:37:22] Setup Engine v1.10.101, Microsoft Windows NT 10.0.10586.0
[0df4:000c][2017-05-24T08:37:22] Command line: "C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Hosts\Microsoft.ServiceHub.Host.CLR\vs_installerservice.exe" desktopClr$C94B8CFE-E3FD-4BAF-A941-2866DBB566FE 18a10ed3a2b52a1e605bf4679dbe1364
[0df4:000c][2017-05-24T08:37:24] ManifestVerifier verification: Exception has been thrown by the target of an invocation. Stack:    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
   at Microsoft.VisualStudio.Setup.Security.ManifestMethods.CalculateHashValue(String dataBlob, String hashMethod)
   at Microsoft.VisualStudio.Setup.Security.ManifestVerifier.CheckSign(ManifestDoc manifestDoc, Signature signature, String layoutCertPath)
   at Microsoft.VisualStudio.Setup.Security.ManifestVerifier.Verify(FileStream fileStream, String path, String layoutCertPath)
[0df4:000c][2017-05-24T08:37:24] ManifestVerifier Result: Exception

dd_client _ *。日志

2017-05-24T08:37:01 : Verbose : Visual Studio Installer (1.10.30637.0 : update2) ["C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installershell.exe","/finalizeInstall","install","--in","C:\\ProgramData\\Microsoft\\VisualStudio\\Packages\\_bootstrapper\\vs_setup_bootstrapper.json","--locale","en-US","--activityId","78239d59-bc71-44e1-b8c6-e67d586fbba5","--campaign","1601306246.1493817089"]
2017-05-24T08:37:02 : Verbose : Creating VS Telemetry Survey
2017-05-24T08:37:03 : Verbose : Received the application ready notification
2017-05-24T08:37:03 : Verbose : Starting ServiceHub Experimentation client.
2017-05-24T08:37:09 : Verbose : Calling ExperimentationProviderService.Initialize()
2017-05-24T08:37:09 : Verbose : ServiceHub Experimentation client started.
2017-05-24T08:37:09 : Verbose : ExperimentsIpcRpcService listening to ipc channel: ExperimentsProxy
2017-05-24T08:37:09 : Verbose : Experiments Ipc Service started.
2017-05-24T08:37:09 : Verbose : Telemetry Session ID: 2b7ca8c1-aa76-4fe1-81eb-36936b1e32d7
2017-05-24T08:37:09 : Verbose : Connected to Hub Controller's client watch 'net.pipe://1140e3f8da9d1a14f42763f0648c14f4'
2017-05-24T08:37:09 : Verbose : ServiceHubExperimentationClient.setSharedProperty(name, value) called,
 [name: VS.ABExp.Flights] [value: lazytoolboxinit;fwlargebuffer;refactoring;spmoretempsbtn1;c32bca7948ab42c;tn-none-15b;vswlaunchbcf]
2017-05-24T08:37:10 : Verbose : Calling ExperimentationProviderService.IsFlightEnabledAsync(flightId). [flightId: VSWLaunchBanner]
2017-05-24T08:37:10 : Verbose : ServiceHubExperimentationClient.postEvent(name, properties) called.
 [name: VS/ABExp/FlightRequest] [properties: {"VS.ABExp.Flight":"vswlaunchbanner","VS.ABExp.Result":"False"}]
2017-05-24T08:37:10 : Verbose : Resolved ExperimentationProviderService.IsFlightEnabledAsync(flightId).
 [flightId: VSWLaunchBanner] [result: false]
2017-05-24T08:37:11 : Verbose : Getting installed product summaries. [installerId: SetupEngine]
2017-05-24T08:37:11 : Verbose : Starting the installed products provider service.
2017-05-24T08:37:11 : Verbose : Starting the products provider service.
2017-05-24T08:37:11 : Verbose : Getting product summaries. [installerId: SetupEngine]
2017-05-24T08:37:11 : Verbose : Starting the installer service.
2017-05-24T08:37:11 : Verbose : Calling SetupEngine.Installer.Initialize. [locale: en-US]
2017-05-24T08:37:11 : Verbose : SetupEngine.Installer.Initialize succeeded. [locale: en-US]
2017-05-24T08:37:11 : Verbose : Started the installer service.
2017-05-24T08:37:11 : Verbose : Calling SetupEngine.Installer.IsElevated.
2017-05-24T08:37:11 : Verbose : SetupEngine.Installer.IsElevated succeeded.
2017-05-24T08:37:22 : Verbose : Started the products provider service.
2017-05-24T08:37:22 : Verbose : Started the installed products provider service.
2017-05-24T08:37:22 : Verbose : Getting product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Professional].
2017-05-24T08:37:24 : Error : Failed to get product. [installerId: SetupEngine, productId: Microsoft.VisualStudio.Product.Professional, error: The installer manifest failed signature validation. at    at Microsoft.VisualStudio.Setup.Engine.Load(String path, Boolean skipVerify)
   at Microsoft.VisualStudio.Setup.Engine.Load(Uri manifestUri, Uri channelUri, Uri installChannelUri, CancellationToken token, Boolean skipVerify)
   at Microsoft.VisualStudio.Setup.Engine.Load(ChannelNode`1 channelProduct, CancellationToken token, Boolean skipVerify)
   at Microsoft.VisualStudio.Setup.ProductInstaller.CreateEngine(IEngineFactory engineFactory, IServiceProvider engineServiceProvider, IProgressReporter progressReporter, IMessageBus messageBus, IRestartManager restartManager, String instanceId, ChannelNode`1 channelProductSummary)
   at Microsoft.VisualStudio.Setup.ProductInstaller.GetEngine()
   at Microsoft.VisualStudio.Setup.ProductInstaller..ctor(ILogger logger, String language, LocalizedResourceFallback languageFallback, IEngineFactory engineFactory, IRestartManager restartManager, IInstance instance, ChannelNode`1 channelProductSummary, VersionBundle latestVersion, IServiceProvider setupServiceProvider)
   at Microsoft.VisualStudio.Setup.ProductInstallerFactory.Create(ChannelNode`1 channelProductSummary, IInstance instance, VersionBundle latestVersion)
   at Microsoft.VisualStudio.Setup.ProductInstallerCache.GetInstaller(String installerId, Func`2 func)
   at Microsoft.VisualStudio.Setup.ProductsProviderService.GetProduct(String channelId, String productId)]
2017-05-24T08:38:09 : Verbose : Closing installer. Return code: 0.
2017-05-24T08:38:09 : Verbose : [ProductsProviderImpl]: Rpc connection was closed.
2017-05-24T08:38:09 : Verbose : [InstalledProductsProviderImpl]: Rpc connection was closed.
2017-05-24T08:38:09 : Verbose : [InstallerImpl]: Rpc connection was closed.

我不确定还有什么可以尝试,微软直播支持没有提供我在上述链接中尚未尝试过的任何新内容。

有没有其他人经历过这个并知道如何提供帮助?

哦,我忘了提及,安装程序似乎处于无法使用的状态,我无法登录以报告问题。此外,developercommunity.visualstudio.com网站似乎也有问题使用我的微软帐户登录。

[click sign in immediately get presented with error (where is the credential window? can't do anything on the screen without signing in

4 个答案:

答案 0 :(得分:1)

来自:https://developercommunity.visualstudio.com/content/problem/3983/when-the-setup-start-i-receive-the-message-the-pac.html

  

我发现通过运行gpedit.msc进行设置,然后运行计算机配置 - > Windows设置 - >安全设置 - >本地政策 - >安全选项 - >系统加密:使用符合FIPS标准的算法进行加密,散列和签名

基本上关闭“使用符合FIPS标准的算法进行加密,散列和签名”。解决了这个问题。

我之前不知道它是如何工作的,因为我从未关闭过这个GP设置。除非它是我们GP的新设置,或者MS不再使用符合FIPS的算法......等等......

答案 1 :(得分:0)

您至少需要从证书文件夹安装:

  1. manifestCounterSignCertificates.p12;
  2. manifestSignCertificates.p12;
  3. vs_installer_opc.SignCertificates.p12。
  4. 您可以尝试从证书文件夹中删除这些文件,然后再次运行安装程序以接收新证书。

    还可以使用Microsoft的rootsupd工具更新证书http://download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/rootsupd.exe

    然后解压缩文件:

    rootsupd.exe /c /t:C:\temp\newroot
    

    从c:\ temp \ newroot从提升的提示符运行(以管理员身份运行cmd.exe):

    updroots.exe authroots.sst
    updroots.exe updroots.sst
    updroots.exe -l roots.sst
    updroots.exe -d delroots.sst
    

答案 2 :(得分:0)

我在干净的Win7 Professional机器上遇到此问题。我在here所示的脱机安装程序上创建,然后将证书从“证书”文件夹安装到“受信任的根证书颁发机构”,然后就可以了

答案 3 :(得分:0)

请按照以下步骤摆脱此“程序包清单签名验证失败” 问题:

  1. 搜索“ certmgr.msc”

    enter image description here

  2. 点击导入

    enter image description here

  3. 从安装程序 certificates 文件夹中一个接一个地导入所有证书。

    enter image description here

  4. 再次运行安装程序