Games for Windows and the DirectX SDK blog

Technical tips, tricks, and news about game development for Microsoft platforms including desktop, Xbox, and UWP

Project maintained by walbourn Hosted on GitHub Pages — Theme by mattgraham
Home | Posts by Tag | Posts by Month



Originally posted to Chuck Walbourn's Blog on MSDN,

We’ve republished the June 2010 DirectX End-User Runtime Web Installer, which now shows a release date of "11/30/2010" "4/18/2011" “2/20/2021”. This deploys all the same binaries as the June 2010 version, but the setup itself has been updated to resolve a few key issues.

IMPORTANT: The DirectX End-User Runtime has been updated in 2021 to address SHA-1 deprecation. Be sure to read this blog post and this one.

For the June 2010 DirectX SDK release, we switched over to the Visual C++ 2010 compiler toolset which generates binaries that are not compatible with Windows XP RTM, Windows XP Service Pack 1, or Windows Server 2003 RTM. Attempts to run the installer on these older versions of Windows resulted in a strange error about a missing EncodePointer() entry-point in KERNEL32.DLL. This updated installer will now display an error about that version not being supported. Windows XP RTM, Windows XP Service Pack 1, and Windows Server 2003 RTM along with Windows 2000, Windows 98, and Windows ME are not supported by the current DirectX End-User Runtime Installers. See “Not So DirectSetup” for more information about the state of DirectSetup.

NOTE: For game developers looking to repackage older games, consider using the Microsoft.DXSDK.D3DX NuGet package which provides a side-by-side shippable version of D3DX9_43.DLL, D3DX10_43.DLL, D3DX11_43.DLL, and D3DCompiler_43.dll under a new license per this blog post. For XAudio2 on Windows 7 SP1 or later, consider updating your audio code using the Microsoft.XAudio2.Redist NuGet package as detailed on Microsoft Docs. These packages do not make use of legacy DirectSetup and are shipped ‘application local’.

There’ve been several long-standing international font display issues in the End-User Runtime installer, particularly for languages that do not make use of Codepage 1252 (Simplified Chinese, Traditional Chinese, Czech, Japanese, Korean, Polish, and Russian). This has been corrected for most of the dialogs and prompts, although some problems persist in the status strings due to limitations of the underlying install technology. This ensures the EULA and the dialog UI is displayed correctly on all supported languages on Windows XP, Windows Vista, and Windows 7 with the appropriate language pack installed.

The .NET 4.0 Runtime has deprecated the GetCORVersion() entry-point, and the Managed DirectX 1.1 installation would trigger an error message if the system had .NET 4.0 but did not also have the .NET 1.1 or 2.0 Runtime available. This case was limited to Windows XP machines as Windows Vista and Windows 7 both include .NET 2.0. With this update, the error message is no longer triggered. Note that Managed DirectX 1.1 is not compatible with .NET 4.0, so it will not get installed on systems that only have the .NET 4.0 Runtime available.

We are currently evaluating when we might update the DirectX End-User Runtimes (stand-alone) with these fixes.

These fixes were also made to the DirectX End-User Runtimes (stand-alone)

In addition to correcting these issues, the DirectX End-User Runtime Web Installer will offer users the option to install the Bing™ Bar for non-Server versions of Windows if it is not already installed.

Update: As noted in this newer blog post, we have updated the DirectX End-user Runtimes (June 2010) stand-alone with these fixes. The latest DirectX End-User Runtime Web Installer now has a publish date of 4/18/2011.