Windows 10: Windows 10 SDK Preview Build 18990 available now - October 1

Brink · Oct 2, 2019

Today, we released a new Windows 10 Preview Build of the SDK to be used in conjunction with Windows 10 Insider Preview (Build 18990 or greater). The Preview SDK Build 18990 contains bug fixes and under development changes to the API surface area.

The Preview SDK can be downloaded from developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum. For new developer feature requests, head over to our Windows Platform UserVoice.

Things to note:

This build works in conjunction with previously released SDKs and Visual Studio 2017 and 2019. You can install this SDK and still also continue to submit your apps that target Windows 10 build 1903 or earlier to the Microsoft Store.

The Windows SDK will now formally only be supported by Visual Studio 2017 and greater. You can download the Visual Studio 2019 here.

This build of the Windows SDK will install on only on Windows 10 Insider Preview builds.

In order to assist with script access to the SDK, the ISO will also be able to be accessed through the following static URL: https://software-download.microsoft....us_18990_1.iso.

Tools Updates

Message Compiler (mc.exe)

Now detects the Unicode byte order mark (BOM) in .mc files. If the 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)

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

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. Documentation on Device Guard Signing can be found here: https://docs.microsoft.com/en-us/win...-guard-signing

Breaking Changes

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 to 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.

API Updates, Additions and Removals

The following APIs have been added to the platform since the release of Windows 10 SDK, version 1903, build 18362.
Click to expand...

Read more: Windows 10 SDK Preview Build 18990 available now! - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

:)

Brink · Oct 2, 2019

Windows 10 SDK Preview Build 14965 Released

Today, we released a new Windows 10 Anniversary SDK Preview to be used in conjunction with Windows 10 Insider Preview (Build 14965 or greater). The Preview SDK is a pre-release and cannot be used in a production environment. Please only install the SDK on your test machine. The Preview SDK Build 14965 contains bug fixes and under development changes to the API surface area. If you are working on an application that you need to submit to the store, you should not install the preview.

The Preview SDK can be downloaded from the developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum. For new feature requests, head over to our Windows Platform UserVoice.

Things to note:

The SDK will require Visual Studio 2017 Preview. You can download the Visual Studio 2017 Release Candidate here.

What’s New

This Windows SDK includes updates and additions to the Windows namespace. See section API Updates and Additions below for the list.

Debugging Tools for Windows has been updated with a few new features, including JavaScript scripting and extensibility. See the blogpost at https://blogs.msdn.microsoft.com/win...extensibility/ for more information.

Known Issues Windows SDK

Wrong GenXBF.DLL
If you installed a previous Windows SDK flight, either version 14951 or 14931, you may have an incorrect GenXBF.dll installed. Please follow the following steps after installing the Windows 10 SDK Preview build 14965.

Exit Visual Studio

Open an Administrative command prompt

Type the following: DEL “c:\Program Files (x86)\Windows Kits\10\bin\x86\genxbf.dll”
DEL “c:\Program Files (x86)\Windows Kits\10\bin\x64\genxbf.dll”

Run Control Panel

Select Uninstall a Program

Highlight Windows Software Development Kit – Windows 10.0.14965.1000

Click Change

Select Repair

Click Next

Windows SDK setup will restore the missing GenXBF.dlls with the appropriate version.

Visual Studio 2017 fails with HRESULT: 0x80041FE2 when trying to create C++ UWP apps targeting build 14965 SDK

This is a known problem. Here are steps to address this issue in your project file:

Close the project

Open up the project file in notepad or your favorite editor

Add the following to the project file:

[table][tr][td]1[/td] [td]<PropertyGroup><DoBundleInstallationChecks>false</DoBundleInstallationChecks></PropertyGroup>[/td] [/tr] [/table]

Reopen the project in Visual Studio

Known Issues Microsoft Emulator

Microsoft Emulator Preview for Windows 10 Mobile (10.0.14965.0) crashes when launching
Impact:
Please note that there is a bug impacting the usage of hardware accelerated graphics in the latest release of the Mobile Emulator. Follow the instructions below to temporarily disable hardware accelerated graphics in the emulator and use the emulator with software rendered graphics (WARP).

NOTE: The following registry setting will impact any and all Microsoft Emulators installed on your machine. You will need to remove this registry setting in order to re-enable hardware accelerated graphics in the emulator.

Create the following registry subkey if it doesn’t exist: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Xde\10.0

Right click the 10.0 folder, point to New, and then click DWORD Value.

Type DisableRemoteFx, and then press Enter.

Double-click DisableRemoteFx, enter 1 in the Value data box, select the Decimal option, and then click OK.

Click to expand...

Read more: Windows 10 SDK Preview Build 14965 Released | Building Apps for Windows

Brink · Oct 2, 2019

Windows 10 SDK Preview Build 17095 now available

Today, we released a new Windows 10 Preview Build of the SDK to be used in conjunction with Windows 10 Insider Preview. The Preview SDK Build 17095 contains bug fixes and under development changes to the API surface area.

The Preview SDK can be downloaded from developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum. For new developer feature requests, head over to our Windows Platform UserVoice.

Things to note:

This build is also available in the latest Visual Studio 2017 Preview (https://www.visualstudio.com/vs/preview/)

This build works in conjunction with previously released SDKs and Visual Studio 2017. You can install this SDK and still also continue to submit your apps that target Windows 10 Creators build or earlier to the store.

The Windows SDK will now formally only be supported by Visual Studio 2017 and greater. You can download the Visual Studio 2017 here.

This build of the Windows SDK will install on Windows 10 Insider Preview and supported Windows operating systems.

Known Issues

Cannot deploy to a device: When attempting to deploy to a mobile device, it fails with the following error: DEP0001: Unexpected Error: SmartDeviceException – Class not registered [0x80131500]

To work around this issue:

Go to Administrative Command Prompt

Run REGSVR32 “\Program Files (x86)\Windows Kits\10\bin\10.0.17095.0\x86\SirepClient.dll”

The following tools are not included with this release:

Filtdump.exe
JSConstraintDebug.exe
Regwindmd.exe
Topedit.exe

What’s New:

C++/WinRT Now Available: The C++/WinRT headers and cppwinrt compiler (cppwinrt.exe) are now included in the Windows SDK. The compiler comes in handy if you need to consume a third-party WinRT component or if you need to author your own WinRT components with C++/WinRT. The easiest way to get working with it after installing the Windows Insider Preview SDK is to start the Visual Studio Developer Command Prompt and run the compiler in that environment. Authoring support is currently experimental and subject to change. Stay tuned as we will publish more detailed instructions on how to use the compiler in the coming week.The ModernCPP blog has a deeper dive into the CppWinRT compiler. Please give us feedback by creating an issue at: microsoft/cppwinrt.

Breaking Changes

New MIDL key words.

As a part of the “modernizing IDL” effort, several new keywords are added to the midlrt tool. These new keywords will cause build breaks if they are encountered in IDL files.

The new keywords are:

event

set

get

partial

unsealed

overridable

protected

importwinmd

If any of these keywords is used as an identifier, it will generate a build failure indicating a syntax error.

The error will be similar to:

1 >d:\os\src\onecore\com\combase\unittest\astatestservers\testserver6\idl\remreleasetest.idl(12) : error MIDL2025 : [msg]syntax error [context]: expecting a declarator or * near “)”

To fix this, modify the identifier in error to an “@” prefix in front of the identifier. That will cause MIDL to treat the offending element as an identifier instead of a keyword.

API Updates and Additions

When targeting new APIs, consider writing your app to be adaptive in order to run correctly on the widest number of Windows 10 devices. Please see Dynamically detecting features with API contracts (10 by 10) for more information.

The following APIs have been added to the platform since the release of 16299.
Click to expand...

Read more: Windows 10 SDK Preview Build 17095 now available - Windows Developer Blog

Brink · Oct 2, 2019

Windows 10 SDK Preview Build 17035 now available

Today, we released a new Windows 10 Preview Build of the SDK to be used in conjunction with Windows 10 Insider Preview (Build 17035 or greater). The Preview SDK Build 17035 contains bug fixes and under development changes to the API surface area.

The Preview SDK can be downloaded from developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum. For new developer feature requests, head over to our Windows Platform UserVoice.

Things to note:

This build works in conjunction with previously released SDKs and Visual Studio 2017. You can install this SDK and still also continue to submit your apps that target Windows 10 Creators build or earlier to the store.

The Windows SDK will now formally only be supported by Visual Studio 2017 and greater. You can download the Visual Studio 2017 here.

Known Issues:

Installation on an operating system that is not a Windows 10 Insider Preview build is not supported and may fail.

What’s New:

C++/WinRT Now Available:
The C++/WinRT headers and cppwinrt compiler (cppwinrt.exe) are now included in the Windows SDK. The compiler comes in handy if you need to consume a third-party WinRT component or if you need to author your own WinRT components with C++/WinRT. The easiest way to get working with it after installing the Windows Insider Preview SDK is to start the Visual Studio Developer Command Prompt and run the compiler in that environment. Authoring support is currently experimental and subject to change. Stay tuned as we will publish more detailed instructions on how to use the compiler in the coming week. The ModernCPP blog has a deeper dive into the CppWinRT compiler. Please give us feedback by creating an issue at: microsoft/cppwinrt.

Breaking Changes

New MIDL key words.

As a part of the “modernizing IDL” effort, several new keywords are added to the midlrt tool. These new keywords will cause build breaks if they are encountered in IDL files.
The new keywords are:

event

set

get

partial

unsealed

overridable

protected

importwinmd

If any of these keywords are used as an identifier, it will generate a build failure indicating a syntax error.

The error will be similar to:

1 >d:\os\src\onecore\com\combase\unittest\astatestservers\testserver6\idl\remreleasetest.idl(12) : error MIDL2025 : [msg]syntax error [context]: expecting a declarator or * near “)”

To fix this, modify the identifier in error to an “@” prefix in front of the identifier. That will cause MIDL to treat the offending element as an identifier instead of a keyword.
Click to expand...

Read more: Windows 10 SDK Preview Build 17035 now available - Building Apps for Windows

Windows 10: Windows 10 SDK Preview Build 18990 available now - October 1

Windows 10 SDK Preview Build 18990 available now - October 1

Windows 10 SDK Preview Build 18990 available now - October 1

Windows 10 SDK Preview Build 18990 available now - October 1

Windows 10 SDK Preview Build 18990 available now - October 1 - Similar Threads - SDK Preview Build

Windows 10 SDK Preview Build 20241 now available - October 21

Windows 10 SDK Preview Build 20236 now available - October 14

Windows 10 SDK Preview Build 20231 now available - October 7

Windows 10 SDK Preview Build 20161 now available - July 1

Windows 10 SDK Preview Build 19592 now available - April 1

Windows 10 SDK Preview Build 19008 now available - October 29 Insider

Windows 10 SDK Preview Build 19002 now available - October 22 Insider

Windows 10 SDK Preview Build 18999 available now - October 15 Insider

Windows 10 SDK Preview Build 18995 available now - October 10