I fresh install windows 10 home edition and then start to install Visual Studio 2017 Community Edition.
I only select universal windows platform development, .net desktop development and asp.net web development but "setup completed with warnings".
I want to share the log file above.
Do you have any ideas for this issue ?
I also asked this question to Microsoft Community but no one answered.
The product failed to install the listed workloads and components due to one or more package failures.
Incomplete workloads
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.26206.0)
Incomplete components
Universal Windows Platform tools (2.0) (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26206.0)
Universal Windows Platform tools for Cordova (2.0) (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.26206.0)
Universal Windows Platform tools for Xamarin (2.0) (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.26206.0)
Windows 10 SDK (10.0.14393.0) (Microsoft.VisualStudio.Component.Windows10SDK.14393,version=15.0.26127.0)
You can search for solutions using the information below, modify your selections for the above workloads and components and retry the installation, or remove the product from your machine.
Following is a collection of individual package failures that led to the incomplete workloads and components above. To search for existing reports of these specific problems, please copy and paste the URL from each package failure into a web browser. If the issue has already been reported, you can find solutions or workarounds there. If the issue has not been reported, you can create a new issue where other people will be able to find solutions or workarounds.
Package 'Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install.
Search URL: https://aka.ms/VSSetupErrorReports?q=PackageId=Win10SDK_10.0.14393.795;PackageAction=Install;ReturnCode=-2146889721
Impacted workloads
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.26206.0)
Impacted components
Universal Windows Platform tools (2.0) (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26206.0)
Universal Windows Platform tools for Cordova (2.0) (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.26206.0)
Universal Windows Platform tools for Xamarin (2.0) (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.26206.0)
Windows 10 SDK (10.0.14393.0) (Microsoft.VisualStudio.Component.Windows10SDK.14393,version=15.0.26127.0)
Log
C:\Users\emrek\AppData\Local\Temp\dd_setup_20170307010944_177_Win10SDK_10.0.14393.795.log
Details
Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NoLogo -NoProfile -ExecutionPolicy Unrestricted -InputFormat None -Command "& """C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.795,version=10.0.14393.79501\WinSdkInstall.ps1""" -SetupExe sdksetup.exe -SetupLogFolder standalonesdk -PackageId Win10SDK_10.0.14393.795 -LogFile """C:\Users\emrek\AppData\Local\Temp\dd_setup_20170307010944_177_Win10SDK_10.0.14393.795.log""" -SetupParameters """/features OptionId.AvrfExternal OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart"""; exit $LastExitCode"
Return code: -2146889721
Return code details: The hash value is not correct.
I solved this problem by vpn connection.
If you have any problem installing visual studio 2017 or windows 10 sdk try to connect vpn and continue process.
I do not know why this kind of situation we have but you can fix this issue connecting to the net via vpn.
in my case the corrupted files caused that error. I manually deleted C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.19041,version=10.0.19041.1 (or your version of windowsSDK)
folder and then in Visual Studio 2022 installer picked up modify option and install after download (or so) from dropdown next to modify button .
It won't work without delete.
Also For sure temporarily turn off Defender . Then if its all settled turn it on again.There are possible troubls with folder acceses. Seems.
Related
I cannot install the above mentioned package, which is requied to proceed the Visual Studio install. I checked on Microsoft's forums for solution but no luck.
I unchecked read-only checkbox in the root of the directory, also manually recreated x64 and x86 folders. The permissions on the users are as they should be also the cleaner app didn't help. I am using the 1809 Windows edition. The current VS version is 15.9.4.
The log is the following:
Something went wrong with the install.
You can troubleshoot the package failures by:
1. Search for solutions using the search URL below for each package failure
2. Modify your selections for the affected workloads or components and then retry the installation
3. Remove the product from your machine and then install again
If the issue has already been reported on the Developer Community, you can find solutions or workarounds there. If the issue has not been reported, we encourage you to create a new issue so that other developers will be able to find solutions or workarounds. You can create a new issue from within the Visual Studio Installer in the upper-right hand corner using the "Provide feedback" button.
================================================================================
Package 'Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.Setup.Configuration;PackageAction=Install;ReturnCode=1317
Details
MSI: C:\TempTmp\Nova mapa\Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008\Microsoft.VisualStudio.Setup.Configuration.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 ALLUSERS="1" MSIFASTINSTALL="7"
Return code: 1603
Return code details: Fatal error during installation.
Message Id: 1317
Message Details: An error occurred while attempting to create the directory: C:\ProgramData\Microsoft\VisualStudio\Setup
Log
C:\TempTmp\dd_setup_20181215215511_001_Microsoft.VisualStudio.Setup.Configuration.log
Impacted workloads
Game development with Unity (Microsoft.VisualStudio.Workload.ManagedGame,version=15.0.27005.2)
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Workload.CoreEditor,version=15.0.27205.0)
Impacted components
.NET Native (Microsoft.Component.NetFX.Native,version=15.0.26208.0)
.NET Native and .NET Standard (Microsoft.VisualStudio.ComponentGroup.UWP.NetCoreAndStandard,version=15.8.27906.1)
.NET Portable Library targeting pack (Microsoft.VisualStudio.Component.PortableLibrary,version=15.6.27309.0)
.NET profiling tools (Microsoft.VisualStudio.Component.DiagnosticTools,version=15.8.27729.1)
ASP.NET and web development (Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions,version=15.8.27825.0)
Blend for Visual Studio (Microsoft.ComponentGroup.Blend,version=15.6.27406.0)
C# and Visual Basic (Microsoft.VisualStudio.Component.Roslyn.LanguageServices,version=15.8.27729.1)
ClickOnce Publishing (Microsoft.Component.ClickOnce,version=15.8.27825.0)
Data sources and service references (Microsoft.VisualStudio.Component.VisualStudioData,version=15.6.27406.0)
Developer Analytics tools (Microsoft.VisualStudio.Component.AppInsights.Tools,version=15.8.27825.0)
Image and 3D model editors (Microsoft.VisualStudio.Component.Graphics,version=15.6.27406.0)
JavaScript and TypeScript language support (Microsoft.VisualStudio.Component.JavaScript.TypeScript,version=15.9.28125.51)
JavaScript diagnostics (Microsoft.VisualStudio.Component.JavaScript.Diagnostics,version=15.8.27729.1)
NuGet package manager (Microsoft.VisualStudio.Component.NuGet,version=15.9.28016.0)
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.9.28119.51)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.9.28307.102)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Component.CoreEditor,version=15.8.27729.1)
Visual Studio Tools for Unity (Microsoft.VisualStudio.Component.Unity,version=15.7.27617.1)
WebSocket4Net (Component.WebSocket,version=15.0.26606.0)
Update 1.1.2019
I contacted the Microsoft support over chat, but didn't get any further. I was told to try to install an earlier release. I ended up formatting my SSD and installing all the software all over. It luckily succeeded. I am providing a vslogs overview of the error, before the format.
I can compile my UWP app built with Xamarin in Debug-mode, but when I try to compile it using Release->ARM mode, these errors occurs
ILT0005: 'C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\ARM\ilc\tools\Gatekeeper.exe #"C:\Users\Source\app\project.UWP\obj\ARM\Release\ilc\intermediate\gkargs.rsp"' returned exit code 1
Error: Windows Runtime metadata is invalid in Windows SDK, follow the steps in http://go.microsoft.com/fwlink/?LinkId=733341 to repair your installation.
I tried to reinstall using the Windows Software Development Kit - Windows 10.0.10586.212 and Windows Software Development Kit - Windows 10.0.26624.
Shall I have both Development Kits?
Or which one do I have to remove?
Or what can cause the problem?
And how shall I fix it?
I am running Microsoft Visual Studio 2015 Enterprise Update 2 and Windows 10 Pro version 1511.
I have tried this, but without success, as I am running Visual Studio in English.
My target and min. version is set to Windows 10 (10.0; Build 10240)
If you remove all Windows SDK's, you can let Visual Studio download them, which worked for me.
Otherwise you can download the Windows SDK's and install it.
Long time reader first time poster here.
I'm a Linux developer trying to get started on Windows development in my new job. I knew it would not be trivial but the first thing I'm trying to do is complete and integrate a netvmini port driver (started by a co-op student) into one of their C++ apps. I am struggling to get the build environment going...
The project was started in Visual Studio 2013 with a Windows 7 target. When I now open it in Visual Studio 2015 and try to build the solution I get:
"Unknown or unsupported property value Win7 for TargetVersion"
for each project. This also happens if I set the configuration to Win8 (both release and debug). If I set it to Win 8.1 I get:
"An SDK corresponding to WDK version '8.1' was not found. Please install the SDK before building"
I have installed every WDK and SDK I can lay my hands on from Windows 7 to Windows 10 using both the web and the VS2015 installer. I have even installed Visual Studio 2013 again but I can't even seem to get the WDK to integrate with that.
The end goal here is to be able to build this (and hopefully debug remotely in kernel mode) from my Windows 10/VS2015 workstation for targets from Windows 7-10. Any advice or documentation that details how to integrate new build platforms into VS would be helpful (all the MS documentation just tells me what I can do if I install this or that, but not HOW to do it)
I also had the same problem after running the Project Upgrade tool.
I discovered when making new configurations that "Win7" and "Win8" TargetVersion are now "Windows7" and "Windows8".
The upgrade tool does not make that change for you but I was able to manually edit my upgraded project with those changes and got it to build for all targets.
I discovered that the installer doesn't install the windows 10 SDK by default. So all the installing of other SDK's was useless. I Also found out that by installing the Win 10 SDK through the VS 2015 installer it integrates and allows me to build for targets back to windows 7 in VS 2015.
I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1
I'm having a problem on my TeamCity CI build server where during compilation I get the following error:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2342, 9): error MSB3086: Task could not find "AL.exe" using the SdkToolsPath "" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed
I've found similar reports from a year ago when people were upgrading to .NET 3.5, for example this one. In that case, installing the latest SDK solved the issue, however I have already installed the latest SDK (Microsoft Windows SDK for Windows 7 and .NET Framework 4) on my build server. The MSBuild tools are all there on the server, in a folder called
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
and AL.exe exists in
C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools
However the registry key mentioned in the error message does not exist. So, it seems like there is something wrong with the installation/configuration of MSBuild. This error only happens for projects that have embedded resources, which require AL.exe.
As you have install the latest SDK (I'm assuming that's v7.1)
Go to "Microsoft Windows SDK v7.1" from the Start menu
Select "Windows SDK 7.1 Command Prompt" and enter
cd Setup
WindowsSdkVer -version:v7.1
This will tell msbuild to use that version of the tools without needing to do any scary registry editing.
Even though the question is quite old but it still appears in the top of google search results so I decided to post my solution as well. I have trapped into same issue while during TeamCity setup on Windows Server 2016 and Windows 10 Pro.
I have installed Microsoft Build Tools 2015 and Windows 10 SDK (Only tools for .NET 4.6.2) and got the error from question.
The missing puzzle was to set environment variable: TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools.
After setting environment variable MSBuild was able to resolve all needed tools including AL.exe and build succeeded.
Please let me know if same can be achieved by setting values in registry, but otherwise environment variables also works very well in this case and no installation of VS is needed.
You also need to apply the following registry fix to update msbuild to point to the V7.1 sdk values.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0]
"MSBuildToolsPath"="C:\\WINDOWS\\Microsoft.NET\\Framework\\v4.0.30319\\"
"MSBuildToolsRoot"="C:\\WINDOWS\\Microsoft.NET\\Framework\\"
"FrameworkSDKRoot"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1#InstallationFolder)"
"MSBuildRuntimeVersion"="4.0.30319"
"SDK40ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1\\WinSDK-NetFx40Tools-x86#InstallationFolder)"
"SDK35ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1\\WinSDKNetFx35Tools#InstallationFolder)"
"MSBuildToolsPath32"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSBuild\\ToolsVersions\\4.0#MSBuildToolsPath)"
I had the same problem there, here's my simple answer to this.
After you have installed the Microsoft Windows SDK 7.1 on the TeamCity Server.
In Regedit Change this key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0\SDK40ToolsPath
to
$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.1\WinSDK-NetFx40Tools-x86#InstallationFolder)
Follow the below steps. This worked perfectly to me. Saved my time.
1- Right-click the My Computer icon and choose Properties, or in Windows Control Panel, choose System.
2- Choose Advanced system settings.
3- On the Advanced tab, click Environment Variables.
4- Click New to create a new environment variable under User variable section.
5- Variable name: TargetFrameworkSDKToolsDirectory
6- Variable value: TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools
Variable value depends on your SDK installation path.
7- Click OK and Save all windows.
8- Restart Visual Studio.
I have a simple, effective fix.
The problem seems to be that the tools version delivered with Visual Studio is version 7.0A, while the version delivered with the Windows SDK is version 7.1. That's all very well, but MSBuild.exe is still looking for the version 7.0A registry keys, which don't exist. This has to be a bug!
Looking in my registry, all the information for V6.0 and V7.1 is present and correct. So my solution is simple. I created a registry link that makes an alias of the 7.1 keys.
It's not possible to create registry links using the built-in tools, so I downloaded a little utility called 'regln' from here.
C:>regln-x86.exe "\Registry\Machine\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A" "\Registry
\Machine\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.1"
Job done. MSBuild now works perfectly on the TeamCity server.
Add a system env variable TargetFrameworkSDKToolsDirectory
like this:
TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools
restart VS
Ran into the same issue setting up a new build server on Windows 10.
Found and installed the latest (at the time) Microsoft Windows SDK for Windows 7 and .NET Framework 4 and that solved the problem.
We recently had this problem trying to get our .Net 4.0 builds working. We found that the location of al.exe had changed between where the original MSBuild that came with .Net 4.0 looks, and the Visual Studio SDK for .Net 4.0 (which was released later).
Since the only standalone installation of the SDK tools available is the one we had already installed without success (the one you mentioned), the only solution we could think of was to install Visual Studio on the build agents. We put Visual Studio 2010 Express (to keep the installation as lightweight as possible) on there and the problem went away. Not a pretty solution, but it did work - installing VS2010 also installs the SDK tools of the specific version that MSBuild appears to be looking for.
This is a problem that really shouldn't happen, but there didn't seem to be a way of making MSBuild look in the correct place for the tools, even hacking around in the registry.