Установка пакета Windows SDK 7,1 в автоматическом режиме

В этой статье описывается установка Microsoft Windows SDK для Windows 7 и .NET Framework 4 (Windows SDK 1.1 7.1) в автоматическом режиме.

Исходная версия продукта: Пакет SDK для Windows
Исходный номер статьи базы знаний: 2498225

Аннотация

Пакет Windows SDK для Windows 7 и .NET Framework 4 (Windows SDK версии 7.1) можно установить в автоматическом режиме.

Пакет обновления Windows SDK 1.1 должен быть установлен до установки Visual Studio 2010 SP1 (с пакетом обновления 1), если процесс установки выполняется в автоматическом режиме.

Платформы x86 и x64 Поддерживаемые операционные системы:

Windows XP с пакетом обновлений (SP3)

Windows 2003 Server

Windows 2003 Server R2

Windows 2008 R2

Другие необходимые компоненты: .NET Framework 2,0.

ЛИЦЕНЗИОНное соглашение (лицензионное соглашение) доступно в заметках о выпуске. Использование автоматической установки не инвертирует данное соглашение. Проверка для обеспечения соответствия требованиям.

Для автоматической установки Скачайте пакет SDK для ISO и извлеките файлы. Использование программы установки через Интернет не поддерживается для установки в автоматическом режиме.

Команда для выполнения автоматической установки: setup.exe -q -params:ADDLOCAL=ALL .

Платформа .NET Framework 4 необходима для установки всех компонентов в пакете SDK. Если платформа .NET Framework 4 не установлена, следующие компоненты не будут установлены:

Ссылки на сборки & IntelliSense

Средство разработки .NET

Справочная система Майкрософт

Все остальные компоненты будут по-прежнему устанавливаться до тех пор, пока платформа .NET Framework 2,0 установлена до установки пакета SDK.

Если в системе установлен Visual Studio 2010 с пакетом обновления 1 (SP1), установка завершится с ошибками. Во время установки не отображается сообщение об ошибке. Можно определить, что установка не удалась, либо просмотреть файл журнала установки пакета SDK или с помощью функции сбоя. Чтобы устранить эту проблемы, перед установкой пакета SDK необходимо удалить Visual Studio 2010 с пакетом обновления 1 (SP1).

How to: Use the Windows 10 SDK in a Windows Desktop application

When you create a new classic Windows desktop project in Visual Studio, it targets the Windows 10 SDK by default. Visual Studio installs a version of this SDK when you install the C++ Desktop workload. The Windows 10 SDK supports writing code for Windows 7 SP1 and later. For more information about targeting specific versions of Windows, see Using the Windows Headers and Update WINVER and _WIN32_WINNT.

When you upgrade an existing project, you have a choice: You can keep using the target Windows SDK specified in your project. Or, you can retarget your project to use the Windows 10 SDK. With the Windows 10 SDK, you get the advantages of support for the latest operating systems and language standards.

Use the right Windows SDK for your project

Starting with Visual Studio 2015, the C Runtime (CRT) library was separated into two parts: One part, ucrtbase, contains the Standard C and Microsoft-specific CRT functions that you can use in Universal Windows Apps. This library is now known as the Universal CRT, or UCRT, and has moved into the Windows 10 SDK. The UCRT contains many new functions, such as C99 functions, needed to support the latest C++ language standards. The other part of the original CRT is vcruntime. It contains the C runtime support, startup, and termination code, and everything else that didn’t go into the UCRT. The vcruntime library gets installed along with the C++ compiler and toolset in Visual Studio. For more information, see CRT library features.

The UCRT is now a system component that’s installed on every version of Windows 10. It’s also available as an installable component for all earlier supported versions of Windows. You can use the Windows 10 SDK to target all the supported versions of Windows. For a complete list of supported operating systems, see Windows 10 SDK.

To retarget your projects to use the Windows 10 SDK when you upgrade from a project version before Visual Studio 2015, follow these steps:

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 projects. (In earlier versions of Visual Studio, 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. Generally speaking, we recommend you choose the latest installed version. Choose the OK button to apply the change.

The 8.1 in this context refers to the Windows 8.1 SDK.

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 dialog. 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. For more information, 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, open the Visual C++ Directories section of the Project Properties dialog. Select one of the properties, such as Include Directories. Then, open the property value’s dropdown list, and choose . 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 the retargeting procedure for other solution projects, as needed, and rebuild the solution.

To target the Windows 8.1 SDK

Open the shortcut menu for the project node in Solution Explorer, and choose Retarget projects. (In earlier versions of Visual Studio, choose Retarget SDK Version.)

In the Target Platform Version dropdown list, choose 8.1.

Windows 10 SDK

The Windows 10 SDK (10.0.19041.0) for Windows 10, version 2004 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 20H2 and previous Windows releases.

Windows 10, version 20H2 is a scoped set of features for select performance improvements and quality enhancements. Developers should be aware of this release, but no action is necessary at this time.

A new Windows SDK will not be issued to accompany this version of Windows because this release doesn’t introduce new APIs. That means there’s no need to modify your project files or target a new version of Windows, and you should continue to use the Windows 10 SDK for Windows 10, version 2004. When setting the target version for your Windows app, Windows 10 build 19041 is still the most recent target version.

Getting started

You can get the Windows 10 SDK in two ways: install it from this page by selecting the download link or by selecting “Windows 10 SDK (10.0.19041.0)” in the optional components of the Visual Studio 2019 Installer.

Before you install this SDK:

System requirements

The Windows SDK has the following minimum system requirements:

Supported operating systems

• Universal Windows Platform (UWP) app development
  • Windows 10 version 1507 or higher: Home, Professional, Education, and Enterprise (LTSB and S are not supported)
  • Windows Server 2019, Windows Server 2016 and Windows Server 2012 R2 (Command line only)

• Win32 app development
  • Windows 10 version 1507 or higher
  • Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2 (Command line only)
  • Windows 8.1
  • Windows 7 SP1

(Not all tools are supported on earlier operating systems)

Hardware requirements

• 1.6 GHz or faster processor
• 1 GB of RAM
• 4 GB of available hard disk space

Additional SDK requirements

Installation on Windows 8.1 and earlier operating systems requires KB2999226. To install through Windows Update, make sure you install the latest recommended updates and patches from Microsoft Update before you install the Windows SDK.

What’s new

The Windows 10 SDK for Windows 10, version 2004 offers exciting new APIs and updated tools for developing your Windows applications. Learn more about the new features in Windows 10, version 2004.

To see the new APIs introduced with Windows 10, version 2004, see: What’s new in Windows 10 for developers, build 19041.

Removal of api-ms-win-net-isolation-l1-1-0.lib

In this release api-ms-win-net-isolation-l1-1-0.lib has been removed from the Windows SDK. Apps that were linking against api-ms-win-net-isolation-l1-1-0.lib can switch t OneCoreUAP.lib as a replacement.

Removal of irprops.lib

In this release irprops.lib has been removed from the Windows SDK. Apps that were linking against irprops.lib can switch to bthprops.lib as a drop-in replacement.

Removal of wuapicommon.h and wuapicommon.idl

In this release we have moved ENUM tagServerSelection from wuapicommon.h to wupai.h and removed the header. If you would like to use the ENUM tagServerSelection, you will need to include wuapi.h or wuapi.idl.

Windows 10 WinRT API Pack

The Windows 10 WinRT API Pack lets you add the latest Windows Runtime APIs support to your .NET Framework 4.5+ and .NET Core 3.0+ libraries and apps. To access the Windows 10 WinRT API Pack, see the Microsoft.Windows.SDK.Contracts nuget package.

Universal C Runtime (UCRT)

The printf family of functions now conforms with the IEEE 754 rounding rules when printing exactly representable floating-point numbers and will honor the rounding mode requested via calls to fesetround. Legacy behavior is available when linking with legacy_stdio_float_rounding.obj.

Tools

Windows App Certification Kit

In this release of the Windows SDK, several new APIs were added to the Supported APIs list in the App Certification Kit and Windows Store. If there are APIs in the supported list that appear greyed out or disabled in Visual Studio, you can make a small change to your source file, to access them. For more details, see this known issue.

In addition to adding APIs, the following changes have been made to the tests:

Updated tests:

• ValidateContentUriRules will be informational only. Test failures will be presented as warnings.

Removed tests

• WebView WinRT access test for web app
• PackageSizeCheck test for UWP apps
• SupportedApi test for Desktop Bridge apps
• AppContainerCheck test from BinScope for UWP apps
• ServiceWorker check for all app types

New tests

• High-DPI test. A new test for Desktop Bridge apps checks if the app uses DPI aware feature and warns if not specified. This test will encourage you to make your app per-monitor DPI aware. For details on DPI see High DPI Desktop Application Development on Windows.

Message Compiler (mc.exe)

Updates include:

• Now detects the Unicode byte order mark (BOM) in .mc files. If the .mc file starts with a UTF-8 BOM, it will be read as a UTF-8 file. Otherwise, if it starts with a UTF-16LE BOM, it will be read as a UTF-16LE file. If the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, it will be read using the current code page (CP_ACP).
• Now avoids one-definition-rule (ODR) problems in MC-generated C/C++ ETW helpers caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers will now respect the definition of MCGEN_EVENTWRITETRANSFER in each .cpp file instead of arbitrarily picking one or the other).

Windows Trace Preprocessor (tracewpp.exe)

Updates include:

• Now supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Input files that do not start with a BOM will be read using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty.
• Now supports Unicode output (.tmh) files. By default, output files will be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files.
• Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding. Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. This may lead to behavior changes in cases where the input files do not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-8 (with BOM) and/or using the -cp:UTF-8 command-line parameter to avoid encoding ambiguity.

TraceLoggingProvider.h

Updates include:

• Now avoids one-definition-rule (ODR) problems caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of TLG_EVENT_WRITE_TRANSFER are linked into the same binary, the TraceLoggingProvider.h helpers will now respect the definition of TLG_EVENT_WRITE_TRANSFER in each .cpp file instead of arbitrarily picking one or the other).
• In C++ code, the TraceLoggingWrite macro has been updated to enable better code sharing between similar events using variadic templates.

Signing your apps with Device Guard Signing

We are making it easier for you to sign your app. Device Guard signing is a Device Guard feature that is available in Microsoft Store for Business and Education. Signing allows enterprises to guarantee every app comes from a trusted source. Our goal is to make signing your MSIX package easier. See the documentation about Device Guard Signing.

Samples

Windows 10 app samples are now available through GitHub. You can browse the code on GitHub, clone a personal copy of the repository from Git, or download a zipped archive of all the samples. We welcome feedback, so feel free to open an issue within the repository if you have a problem or question. These samples are designed to run on desktop, mobile, and future devices that support the Universal Windows Platform (UWP).

Previous SDK versions

Previously released SDKs and emulators, including update details, can be found on the archive page.

API Light Up

When you use new APIs, consider writing your app to be adaptive so that it runs correctly on the widest array of Windows 10 devices. An adapative app «lights up» with new features wherever the devices and Windows version supports them, but otherwise offers only the functionality available on the detected platform version. For implementation details, see the Version adaptive code article.

Release notes & Known Issues

The Windows 10 SDK, Version 2004 SDK servicing update (released 12/16/2020) contains the following fixes. If you encounter these issues, we recommend that you update your version of the SDK as soon as possible to avoid them:

• Resolved unpredictable and hard to diagnose crashes when linking both umbrella libraries and native OS libraries (for example, onecoreuap.lib and kernel32.lib)
• Resolved issue that prevented AppVerifier from working
• Resolved issue that caused WACK to fail with “Task failed to enable HighVersionLie”

For known issues, see the winapi-sdk Q&A.

For new developer feature requests, submit through the Feedback Hub app under the category “Developer Platform/API.”

More resources

Downloads and tools

Get the latest editions of Visual Studio and Windows 10 development tools.

SDK archive

Find previous releases of the Window SDK and other tools.

Windows blog

Stay in touch with the latest SDK flights by subscribing to our blog.

Windows lifecycle fact sheet

Find the key dates for Windows release updates and end of support.