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

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.

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.

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.

Comments (17)

  1. Andrew McDonald says:

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

    Ugh. I hope this won't end up in the redist version!

  2. Lars Viklund says:

    I guess it's time to start linking the proper fat redist for my software downloads then, even though it's larger, just to avoid risking that any of my users ends up with browser bars.

    Thank you for ruining the web setup.

  3. Kurg says:

    Ohh thanks Bing bar correct all my issues, why attach directX when i only want the Bing bar..

  4. Noob Pwner says:

    how is can i run bing bars in dx11 mode???

    it makes firefox faster?

    plz help me???

  5. RE: Andrew

    The installation of the Bing Bar is not part of the offline REDIST package, and there are not any plans to add it there since that impacts software redistribution. There are as I note in the post a lot of other fixes that will be in a future update of the offline REDIST package.

    RE: Lars

    You likely only need a fairly small package. See <blogs.msdn.com/…/not-so-direct-setup.aspx>

  6. James B says:

    Bing Bar? Awesome. I noticed this when using the web setup today.

    I knew I needed some reason to code for OpenGL exclusively. Thank you Microsoft for making my decision as a developer easier.

  7. RE: James B

    I'm not sure you are really as reliant on the 'web installer' as you might think. Most of DIrect3D comes with the OS, so the only reason the web installer is still around is as a catch all support mechanism for some applications that incorrectly use DirectSetup or fail to deploy the right versions of D3DX or some other optional side-by-side component.

  8. McSucky says:

    yes, sucky bingbar is really going to make everyone's life better.

    great PR, adding an option nobody wants because it's insecure non-functional PR fudge.

  9. Graham Junetz says:

    How to install dxwebsetup with bandwith? My computer doesn't proccess the programs

  10. @Graham: I really don't understand your question.

  11. osama says:

    How to install dxwebsetup with bandwith? My computer doesn't proccess the programs

  12. @Osama: if the web installer isn't working for you, try to use the standalone package. Of course, without more details about which OS you are using I can't really provide any other advice.

  13. deda says:

    how update directx11.2? i have windows 8.1…

  14. @Deda. See Not So Direct Setup. If you have Windows 8.1, you already have DirectX 11.2 installed. The rest depends on having the latest drivers for your video card and/or a video card that supports a desired feature level.

  15. Rich says:

    Where is the web installer now? The link in this post now goes to a Windows 10 page.

  16. Nico says:

    I want to install DirectX from my installer. But, is it possible to force the dxwebsetup installation window to a certain place on the screen? To the center at least. Thanks!!

    1. The DXWEBSETUP is not intended for ‘chaining’ from an existing installer. You should use the DirectX End-User Runtimes (DXSETUP) and configure it to have only those CABs that are actually required for your application and target platform per MSDN.

Skip to main content