When I download and run windowsdesktop-runtime-6.0.1-win-x64.exe to install the .NET 6 Desktop Runtime on Windows, then it is not installed to C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\6.0.1 as expected.
This does not match the official documentation here: Check for install folders
Where are the files installed to and how can I detect if this package is already installed?
Problem occurred only on a machine where the .NET SDK (and VS2022) was already installed. It cannot be reproduced on a plain, naked Windows installation.
The runtime files I have located in the C:\Program Files\dotnet\shared\Microsoft.NETCore.App{version} folder.
Using a 3rd party IL disassembler, it asked me for the location of a .NET 6.0 System.Runtime.dll location.
Related
I try to flash old version of Windows IoT 10 Core to Raspberry Pi 3.
I downloaded from here the .iso with .msi installer in.
As mentioned here the .ffu need appears in C:\Program Files (x86)\Microsoft IoT\FFU\RaspberryPi2, however there is a new .ffu file, of Latest Windows 10 IoT Core builds.
I searched with Total Commander and found one more file in this place: C:\Users\olga\AppData\Local\Temp\RPi2\msi\msicontent\Microsoft IoT\FFU\RaspberryPi2
Is there some convintional place for .ffu, or what the conventional way of downgrade the Windows IoT Core image?
Yes the default path that FFU install is C:\Program Files (x86)\Microsoft IoT\FFU.
If you want to install an old version please check if there is already a version installed on your machine at first. You can check the default path to see if there is a flash.ffu in RaspberryPi2 folder, if it is uninstall it via control panel:
Then install the old version. You will see the flash.ffu under C:\Program Files (x86)\Microsoft IoT\FFU\RaspberryPi2 if install successfully.
I searched with Total Commander and found one more file in this place:
C:\Users\olga\AppData\Local\Temp\RPi2\msi\msicontent\Microsoft
IoT\FFU\RaspberryPi2
For this issue, please check the path in the setup operation:
According to various web pages, orca.msi/orca.exe is primarily distributed as part of the Windows SDK.
I have Visual Studio 2015 Professional Update 3 installed. I have installed all the "Universal Windows App Development Tools" components, which includes three different versions of the Windows 10 SDK (10.0.14393, 10.0.10586, 10.0.10240).
But I can't find orca.msi or orca.exe anywhere on my machine. Is this tool no longer packaged with the Windows SDKs? Do I need to install one of the older Windows SDKs as well? Is there an optional Visual Studio 2015 component that I can install to get Orca?
An MSDN page for orca.exe eventually leads me to a download page for Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1. Is this the most recent SDK which includes orca.msi, or can it be found in newer SDKs such as the Win7/.NET4.0 or Windows 8 or Windows 8.1 SDKs?
Thanks to the confirmation from #pnp0a03 that Orca is still present in modern Windows SDK ISOs, I was able to figure out an install process which does not require re-downloading the full ISO.
It turns out that the Windows 10 SDK can install orca (though the file is now named orca-x86_en-us.msi) but it is not installed by default when you install the SDK via the Visual Studio installer. It is an optional component of the SDK, and the Visual Studio 2015 installer does not offer any control over which SDK components are installed. You have to separately run the SDK installer to install the component which contains Orca.
To do so, go to "Apps and Features", select the most recent Windows Software Development Kit from the installed apps list, and click "Modify".
This starts the installation wizard for the SDK itself.
Now you can edit which SDK features are installed. Select "MSI Tools" and click Change:
After the wizard completes, the Orca installer can now be found in the SDK's install path. On my machine, that's located at C:\Program Files (x86)\Windows Kits\10\bin\x86\Orca-x86_en-us.msi. Running that MSI package installs the latest version of Orca itself.
You can pick it from Windows SDK ISO.
Download the latest SDK ISO Image. Current one is 16299.15.
Mount it with Explorer and open the directory Installers. You can find the Orca-x86_en-us.msi.
Downloads Windows 10 SDK
We can download the latest Windows 10 SDK from here
When installing the SDK installer, select below feature alone and proceed installation
"MSI Tools"
Check below folder and look for Orca-x86_en-us.msi
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86
NOTE: In my C:\Program Files (x86)\Windows Kits\10\bin folder, I see multiple versions of windows 10 and one can see the orca MSI under the latest version number folder (under x86)
I was able to successfully download and install it the following way:
Download the Windows SDK as ISO file
Right-click on the ISO file (*_release_WindowsSDK.iso) and select "Mount"
Go to folder "Installers", find and extract "Orca-x86_en-us.msi" (drag and drop it to a local folder outside of the ISO)
Do the same with the 3 cab files listed below:
Double click the file "Orca-x86_en-us.msi", and Orca will be added to the Windows start menu.
NOTE: In the link provided above, you can find an archive of older, as well as newer Windows versions too - if required.
How to get orca installed without downloading the entire ISO
Go here: https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/
Click to download the installer (not the .iso)
Follow the prompts until you get this screen, where you uncheck everything but MSI stuff.
After the install completes, search the install folder for Orca.msi and
install it. It is usually in:
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.22000.0\x86\Orca-x86_en-us.msi"
I am trying to build a WebRTC library. It has a bunch of build python scripts one of which is trying to access
C:\Program Files (x86)\Windows Kits\10\Redist\ucrt\DLLs\x64
And copy ucrt Dlls into build directory.It fails there because my Redist directory doesn't have ucrt folder. I tried to uninstall my Windows SDK 10 and reinstall it.But Redist is still empty. Based on this doc by Microsoft:
To obtain the binaries for app-local deployment, install the Windows
Software Development Kit (SDK) for Windows 10. The binaries will be
installed to C:\Program Files (x86)\Windows Kits\10\Redist\ucrt.
But it simply doesn't happen.I also tried to reinstall all the Windows tools and SDK via my VS2015 (Community) installer.
Did Microsoft deprecate the redistributable part of the installation?
How can I solve this?
I installed Windows SDK 10.0.16299.0 . My system is Windows 10 64bit.
It happened to me. Both the visual studio installer and the standalone install incomplete/corrupt versions of the sdk.
Solution: Install the sdk in a windows VM (you can use the Microsoft provided vm: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) and install the SDK there, then copy the complete folder (named 10 in my case) to the appropriate route. In Windows 10 would be: *C:\Program Files (x86)\Windows Kits*
(Commenting 4 year later because I came here looking for the same answer :) )
I've been trying to get Visual Studio and the Windows 10 SDK to work for over a week now. First I couldn't install Visual Studio. That problem was resolved by uninstalling EVERYTHING vaguely related to VS2015, thanks to manually going through everything, but also the Visual Studio "TotalUninstaller".
Plot twist: Now that I've managed to get VS2015 installed and running, I can't get the SDK to install. I've selected it with the installation process, tried to modify VS after, tried to install it with the Standalone installer, but none of it works. Every time, the installer doesn't notice anything wrong, all the tools appear in the start menu, a new "Program Files (x86)/WindowsKits/10.0" folder appears, with all the correct files, but VS can't open any UWP projects, can't create new any, and the SDK doesn't appear in the Extensions list.
When I uninstalled everything, there was only one thing I couldn't get rid of: "Windows 10 for Mobile Image - 10.0.10240.0". It just opens, runs for a second, and closes, achieving nothing in the process. As I couldn't get rid of this, I manually deleted any "Windows Kits" related folder in Program Files, Program Files (x86), ProgramData, and anything in the AppData folder. But this piece of fluffy garbage didn't leave my installed programs list. Could this have something to do with not being able to install the Windows 10 SDK correctly?
I looked in the install logs, and this is the only error I saw:
[371C:398C][2016-08-08T21:13:35]i301: Applying execute package: {7a68448b-9cf2-4049-bd73-5875f1aa7ba2}, action: Install, path: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe, arguments: '"C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe" -quiet -burn.related.patch -burn.ignoredependencies={248fcd1e-5ee1-421d-893f-ec0a94dd7b01} -burn.ancestors={248fcd1e-5ee1-421d-893f-ec0a94dd7b01}'
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to create embedded process atpath: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to run embedded bundle.
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to run bundle as embedded from path: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to execute EXE package.
[287C:137C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to configure per-machine EXE package.
It appears in every log when I try to install vs2015 with the right option ticked, or when I use the standalone installer. I've looked in C:\ProgramData\Package Cache and there is no {7a68448b-9cf2-4049-bd73-5875f1aa7ba2} folder, and none of the other folders contain "vsupdate_KB3022398.exe". It looks like this is the root of the problem.
EDIT: I've created the folder that was missing and added "vsupdate_KB3022398.exe" to it (found it online, hosted on a Microsoft server), and there are no more errors left. However, the problem still isn't fixed. The SDK simply refuses to show up. I think I'm going to have to do a clean install.
I had the issue of Windows 10 SDK 14393 failing to install on Windows 7 OS. This problem occurred when installing as part of Visual Studio 2015 and also running the Standalone Installer for the Windows 10 SDK 14393. According to the logs, the Windows Desktop Extension SDK failed to install.
As a work-around I installed Windows 10 SDK 10586 (Installed successfully)
Then I installed Windows 10 SDK 14393 (Installed successfully)
Both versions of the Windows 10 SDK appear as choices under Target Platform Version in Visual Studio 2015 for me.
Apparently the Windows 10 SDK 14393 installer is missing something which it requires to run successfully on Windows 7. (Something that must be present in the previous version)
Sorry for the difficulty. There are 2 known issues that are causing 'Fatal Error' in the Windows SDK install.
See the Windows SDK Tools Issues Forum.
You probably have (had) a pre-release of the SDK and one of the contracts installed is causing MDMerge to fail during setup. Uninstalling the prerelease version of the SDK should avoid this issue.
Thanks,
kevin
I had the MDMerge problem, after uninstalling all previous Windows 10 SDK toolkits, still couldn't install. Fixed it by moving the contents of: "C:\Program Files (x86)\Windows Kits\10", ran the installer again and it installed fine.
This is what I did and it kind of worked for me. Remove everything in the linker ( PROJECT -> LINKER -> Input -> Additional Dependencies, as can be seen in this screenshot
I have an InstallShield project (InstallShield 2011 Limited Edition) for Visual Studio 2010. The project is created on a machine running Windows XP (32-bit). It builds an installation package for a C# solution targeted to .NET 4.0 Full profile. However, the same project configuration fails to build installation packages on windows 7. It turns out that the installation of InstallShield itself is different in Windows 7 compared to Windows XP.
When building the installation package on WIndows 7, I get several errors like the following:
ISEXP : error : -1007: Cannot copy source 'C:\Program Files\InstallShield\2011LE\SetupPrerequisites\Windows Installer\3.1\x86\WindowsInstaller-KB893803-v2-x86.exe' to target ...
On Windows XP, there are 3 subdirectory structures in C:\Program Files\InstallShield\2011LE\SetupPrerequisites:
Windows Installer
3.1
Microsoft .net
4.0
WindowsImagingComponent
x64
x86
These directories and there files are missing after installation of InstallShield on Windows 7.
If I add the files manually, the Windows 7 machine can build the InstallShield project without problem.
Is this a bug in InstallShield or have I missed some features? I would like to be able to build installation packages both on Windows 7 and Windows XP without having to patch the InstallShield installation itself.
Typically you right click | download the files from the redist screen. Only the .PRQ (XML) files are in the InstallShield installer. The rest are pulled down once as you need them.