2017-05-24 977 views
0

我已经安装了VS2015,并且以前在此机器上安装了VS2017。在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. 

我不知道什么尝试,微软Live的支持也没有提供任何新的,我还没有已经在上面的链接中试过了。

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

哦,我忘了提及,安装程序似乎处于这种无法使用的状态,我无法登录报告问题。此外,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

回答

0

来源: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兼容的算法...等...

0

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

  1. manifestCounterSignCertificates.p12 ;
  2. manifestSignCertificates.p12;
  3. vs_installer_opc.SignCertificates.p12。

您可以尝试从证书文件夹中删除这些文件,然后再次运行安装程序以接收新证书。

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

然后将解压后的文件:

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

从C:从提升的提示符(cmd.exe的运行作为管理员)\ TEMP \ newroot运行:

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