The Windows 10 SDK (10.0.18362.0) for Windows 10, version 1903 provides the latest headers, libraries, metadata, and tools for building Windows 10 apps. Use this SDK to build Universal Windows Platform (UWP) and Win32 applications for Windows 10, version 1903 and previous Windows releases.
LabWindows/CVI 2015 and Windows 8.1 SDK are already compatible with Windows 7. What OS would you suggest I select in comparability mode?
I don't think this is a compatibility issue. Looking over similar issues, I think the problem is that one of the files on my computer has become corrupted is in no longer bears a signature. I'm attaching the error statements from the setup log in order to reduce clarity.
I don't think this is a compatibility issue. Looking over similar issues, I think the problem is that one of the files on my computer has become corrupted is in no longer bears a signature. I'm attaching the error statements from the setup log in order to reduce clarity.
![Windows Windows](/uploads/1/2/5/0/125038338/186375105.jpg)
Windows Sdk 8.1 For Windows 7
[1118:10C8][2016-03-18T15:37:12]: Registering dependency: {ed3a6e6d-9661-4357-abe4-fcc03dc57a07} on package provider: Microsoft.Windows.WindowsSoftwareDevelopmentKit.x86.8.1, package: package_WindowsSoftwareDevelopmentKitx86_en_us
[1390:1464][2016-03-18T15:37:20]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_MSP_PACKAGE message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to configure per-machine MSP package.
[1390:1464][2016-03-18T15:37:20]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0x800700E8
[1390:1464][2016-03-18T15:37:20]: RetryManager: Not an execute error to retry: 0x800700E8
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to execute MSP package.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to register the dependency on per-machine package.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to end session in per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_MSP_PACKAGE message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to configure per-machine MSP package.
[1390:1464][2016-03-18T15:37:20]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0x800700E8
[1390:1464][2016-03-18T15:37:20]: RetryManager: Not an execute error to retry: 0x800700E8
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to execute MSP package.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to register the dependency on per-machine package.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send message to per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to end session in per-machine process.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to write send message to pipe.
[1390:1464][2016-03-18T15:37:20]: Error 0x800700e8: Failed to send message to per-machine process.
- Aug 09, 2013 Tags Visual Studio 2013 Visual Studio 2013 Games VS 2013 VS 2013 Game Development Windows 8.1 Windows 8.1 Game Design Windows 8.1 SDK Comments (1) Jack Nolan says.
- Jul 12, 2018 How to: Use the Windows 10 SDK in a Windows Desktop Application.; 2 minutes to read +2; In this article. When you create a classic Windows desktop project in Visual Studio 2017, it is set up by default to build with the version of the Windows 10 SDK that was installed when the C Desktop workload was installed or last updated.
- Discussion for the Microsoft Windows SDK for Windows 8 and.NET Framework 4.5 Package. Ground rules: This discussion is only about Microsoft Windows SDK for Windows 8 and.NET Framework 4.5 and the Microsoft Windows SDK for Windows 8 and.NET Framework 4.5 package.
- Windows Phone SDK 8.0 Update for Windows Phone 8.0.10322: Adds four new emulator images to an existing installation of Windows Phone SDK 8.0. This update requires either Visual Studio 2012 with Windows Phone SDK 8.0 and Update 4 or later, or Visual Studio 2013 with the optional Windows Phone SDK 8.0 option selected during setup. INSTALL EMULATORS.
[1390:1464][2016-03-18T15:54:02]: Variable: WixBundleTag =
[1390:1464][2016-03-18T15:54:02]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:54:02]: Error 0x800700e8: Failed to post terminate message to child process cache thread.
[1390:1464][2016-03-18T15:54:02]: Exit code: 0x800700e8, restarting: No
[1390:1464][2016-03-18T15:54:02]: Error 0x800700e8: Failed to write message type to pipe.
[1390:1464][2016-03-18T15:54:02]: Error 0x800700e8: Failed to post terminate message to child process cache thread.
[1390:1464][2016-03-18T15:54:02]: Exit code: 0x800700e8, restarting: No
[1214:1210][2016-03-21T07:46:51]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_MSP_PACKAGE message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to configure per-machine MSP package.
[1214:1210][2016-03-21T07:46:51]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0x800700E8
[1214:1210][2016-03-21T07:46:51]: RetryManager: Not an execute error to retry: 0x800700E8
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to execute MSP package.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to register the dependency on per-machine package.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to end session in per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send message to per-machine process.
-->[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_MSP_PACKAGE message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to configure per-machine MSP package.
[1214:1210][2016-03-21T07:46:51]: Applied patch_WindowsSoftwareDevelopmentKitx86_en_us with status 0x800700E8
[1214:1210][2016-03-21T07:46:51]: RetryManager: Not an execute error to retry: 0x800700E8
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to execute MSP package.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to register the dependency on per-machine package.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send message to per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to end session in per-machine process.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write message type to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to write send message to pipe.
[1214:1210][2016-03-21T07:46:51]: Error 0x800700e8: Failed to send message to per-machine process.
When you create a classic Windows desktop project in Visual Studio 2017, it is set up by default to build with the version of the Windows 10 SDK that was installed when the C++ Desktop workload was installed or last updated. This version of the Windows SDK is compatible with Windows 7 and later. See Using the Windows Headers for more information about targeting specific versions of Windows.
If you want to target an earlier version of the SDK, you can open Project | Properties and choose from the other SDK versions available in the Windows SDK Version dropdown.
Starting with Visual Studio 2015 and the Windows 10 SDK, the CRT library was separated into two parts, one (ucrtbase) that contains the functions that are acceptable to be used in Universal Windows Apps, and one that contains everything else (vcruntime140). Since the Windows 10 SDK contains new functions, such as many C99 functions, you need to follow these steps in order to use those functions. See CRT Library Features.
To target the Windows 10 SDK
- Make sure the Windows 10 SDK is installed. The Windows 10 SDK is installed as part of the Desktop development with C++ workload. A standalone version is available at Downloads and tools for Windows 10.
- Open the shortcut menu for the project node, and choose Retarget SDK Version.The Review Solution Actions dialog appears.
- In the Target Platform Version dropdown list, choose the version of the Windows 10 SDK you want to target. Choose the OK button to apply the change.Note that 8.1 in this context refers to the Windows SDK version, which is also backwardly compatible with Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, and Windows Vista.If this step is successful, the following text appears in the Output window:
Retargeting End: 1 completed, 0 failed, 0 skipped
- Open the project properties, and in the Configuration Properties, General section, notice the values of Windows Target Platform Version. Changing the value here has the same effect as following this procedure. See General Property Page (Project).This action changes the values of project macros that include paths to header files and library files. To see what changed, in the Visual C++ Directories section of the Project Properties dialog, choose one of the properties such as the Include Directories, choose to open the dropdown list, and choose <Edit>. The Include Directories dialog appears.Choose the Macros >> button, and scroll down the list of macros to the Windows SDK macros to see all the new values.
- Repeat for other projects, as needed, and rebuild the solution.
To target the Windows 8.1 SDK
- Open the shortcut menu for the project node, and choose Retarget SDK Version.
- In the Target Platform Version dropdown list, choose 8.1.
![Windows Sdk For Windows 8 Windows Sdk For Windows 8](/uploads/1/2/5/0/125038338/797506970.png)