Known Issue: DirectX SDK (June 2010) Setup and the S1023 error


Note that the DirectX SDK is deprecated. See “Where is the DirectX SDK?“, “Where is the DirectX SDK (2013 Edition)?“, and “Where is the DirectX SDK (2015 Edition)?” for details.

Over the past few month we’ve been getting reports of problems with the DirectX SDK (June 2010) setup failing for customers displaying an installation error when it gets to point of installing the “redistributable packages”. This particular problem has been traced to an issue with the Visual C++ 2010 Redistributable Package version 10.0.30319 (RTM). When the 10.0.40219 (Service Pack 1) version is already present on the system, the 10.0.30319 (RTM) version returns a failure instead of a success as was expected.

The work-around for this issue is straight-forward:

(1) Remove the Visual C++ 2010 Redistributable Package version 10.0.40219 (Service Pack 1) from the system (both x86 and x64 if applicable). This can be easily done via a command-line with administrator rights:

MsiExec.exe /passive /X{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
MsiExec.exe /passive /X{1D8E6291-B0D5-35EC-8441-6616F567A0F7}

(2) Install the DirectX SDK (June 2010)

(3) Reinstall the Visual C++ 2010 Redistributable Package version 10.0.40219 (Service Pack 1). On an x64 system, you should install both the x86 and x64 versions of the C++ REDIST. Be sure to install the most current version available, which at this point is the KB 2565063 with a security fix.

This issue is also covered by KB 2717426

Note: This issue does not affect earlier version of the DirectX SDK which deploy the VS 2005 / VS 2008 CRT REDIST and do not deploy the VS 2010 CRT REDIST. This issue does not affect the DirectX End-User Runtime web or stand-alone installer as those packages do not deploy any version of the VC++ CRT.

Windows SDK: The Windows SDK 7.1 has exactly the same issue as noted in KB 2717426.

Windows 7 Service Pack 1 / Windows 8 users: The Direct3D 10.x/Direct3D 11.x SDK Debug Layers installed by the DirectX SDK (June 2010) are not compatible with Windows 8 or Windows 7 SP1 + KB 2670838. See this post for details on installing the correct version.

Setup writers: If you are creating a deployment for your application and you are using VS 2010, it is recommended you use the Service Pack 1 version and not the RTM version to avoid this issue. You should also consider picking up the updated version of the DirectX End-User Runtime Package if you are deploying DirectX SDK components with your application, and of course fully understand the issues detailed in this earlier blog post.

FCIV: This of course assumes you actually have an uncorrupted copy of the DirectX SDK setup package. The best way to validate this it to run fciv -sha1 DXSDK_Jun10.exe and verify you get 8fe98c00fde0f524760bb9021f438bd7d9304a69 dxsdk_jun10.exe

Comments (59)

  1. YuriOh says:

    But the article "Where is the DirectX SDK" neither covers WHEN a new DX-SDK is coming nor can we see, which version it is. Also I find it not very comfortable to download a complete new Windows SDK when a new DX SDK has been released. And one has no oversight of news about a new DX SDK. That was not the best idea in my opinion.

    Also I'm wondering where the DirectX End-User Redistributables are. Are they integrated into the Windows SDK, too?

  2. LW says:

    He replied this to me before, YuriOh.

    Read this:

    blogs.msdn.com/…/getting-started-with-direct3d-11.aspx

  3. YuriOh says:

    It's not a good answer.

  4. "Because the Windows SDK is the primary developer SDK for Windows, we now ship DirectX as part of the Windows SDK.

    For access to historical versions of these DirectX SDK tools and technologies, download previous versions of the DirectX SDK from the Microsoft Download Center. We shipped the last version of the DirectX SDK in June 2010."

  5. "Any project that uses run-time shader compilation will need to have D3DCOMPILER_44.DLL copied to the local executable path for the project. This DLL is available in this sub-directory of the Windows SDK install under %ProgramFiles(x86)%Windows Kits8.0RedistD3D<arch> where <arch> is x86 and x64.

    The D3DCOMPILER_44.DLL from the Windows SDK is not a system component and should not be copied to the Windows system directory. You can redistribute this DLL to other machines with your application as a side-by-side DLL."

    NOTE: The same is true of D3DCSX (we didn't call it out here because it's not used by any DirectX SDK sample)

    XINPUT: msdn.microsoft.com/…/hh405051.aspx

    XAUDIO: msdn.microsoft.com/…/ee415802.aspx

    D3DX and XACT are deprecated.

  6. grumpy says:

    One chief advantage of having the DX SDK separate was its much faster turnaround. We used to get SDK updates every 2 or 3 months, and there were pretty significant improvements between each version of the SDK.

    The Windows SDK has, by contrast, been updated at best once per year, and rarely had the same kind of improved tools or new functionality that was provided by the DX SDK.

    So, when D3D is now part of the Windows SDK, does this mean we should no longer expect to see significant improvements to D3D SDK-wise? Is PIX and all the other tools and libraries provided by the SDK basically set in stone, with only incremental updates and bugfixes basically synchronized with OS releases?

  7. YuriOh says:

    Additionally it's not good to hear, that the new SDK Components (XAudio, XInput) will not be available for Windows 7. Want Microsoft the force the customers to buy Windows 8? For Vista there was a platform update to use it with DX 11. But DX 11.1 should only be available for Windows 8? Why? Because there are voices that say Windows 8 will flop? Not the best idea Microsoft ever had, I think.

  8. "Direct3D" has since ~2004 changed at the pace of the Windows OS release cycle (major release, Service Packs, etc.). Frequent DirectX SDK releases have not changed "Direct3D" any faster than the OS cycle for some time, and there's no news here in this regard. I can certainly understand that the perception was that more frequent DirectX SDK releases meant lots of frequent improvements here, but that not really been what has transpired in recent years.

    The "PIX for Windows" tool is part of Visual Studio, so that is the release cycle to expect there. The good news is that they have more people working on the new VS version than have been available to work on PIX for Windows for many years.

    The HLSL compiler (FXC, D3DCompiler*.DLL), D3DCSX, the debug layer, and the reference device have not always been updated in every "DirectX SDK" release of the past few years. The HLSL compiler has certainly had a lot of major and minor updates over the years, but fast servicing here has often resulted in regressions as well which has required yet more fast servicing. I don't personally believe the Windows SDK release cycle is a significant problem for the expected pace of this work going forward.

    Samples and some tools (aka DirectXTex) are delievered via the Windows code gallery code.msdn.microsoft.com so the release cycle is basically continuous there. There have also been numerous minor updates made here on this blog. By pulling the samples and various 'miscellaneous tools' out of the new Windows SDK, this both lessens the need for extremely frequent releases, as well as addresses a chief complaint of the Windows SDK just being too big.

    The only components that have really 'slowed down' from where we've been in the past few years has been XINPUT and XAUDIO2–well, just XAUDIO2 since XINPUT 1.3 hasn't changed since April 2007. These have become Windows OS components so these technologies are indeed likely to only change at the Windows OS release cycle. XAUDIO 2.7 and XINPUT 1.3 in the DirectX SDK continue to be available for developers working on Windows 7 titles. The majority of changes in XAUDIO 2.8 and XINPUT 1.4 are to support the needs of Windows 8 Metro style applications, not major new features over the existing versions. I would not expect the incremental changes to XAUDIO 2.8 or XINPUT 1.4 to really be percieved as a lever to "force the customers to buy Windows 8".

    DirectX 11.1 is expected to be available in some form on Windows 7, and that is likely to be the same kinds of things that were released in the DirectX 11 on Windows Vista: "Direct3D", "DXGI", "WDDM", "WARP", "WIC", "Direct2D", and "DirectWrite". Details here are TBD. We plan to release an updated XUSB driver (the one that is used by XINPUT) via WIndows Update as well which should address most known issues for XINPUT 1.3 on Windows 7 as well.

    DirectXMath (aka XNAMath version 3.x) is releasing through the Windows SDK as well, but as a fully inline header implementation it is not difficult to provide faster servicing here if needed. There is nothing OS specific to this component and it works on older versions of the OS just fine–the only real limitation here is that you can't use it with a compiler older than VS 2010.

  9. Kris says:

    I'm confused, why is D3DX deprecated?

  10. Kris – See the first few slides in my presentation from Gamefest 2011 "Modern Texture Content Pipelines" for some context <http://www.microsoft.com/…/details.aspx

  11. Dido says:

    i had error s1023 aswell but nothing posted here worked, but going through the DirectX.log file i managed to pinpoint the error i had, it was something wrong with accessing or corrupted d3dx9_31.dll to d3dx9_43.dll files in c:windowsSysWOW64 and c:windowsSystem32 so i moved them away temporarily to see if that would work and it did! So finally after hours of wasting time i got it working 🙂

  12. Thane says:

    Will DirectX support stereoscopic 3D any time soon? I also have an idea for A.I. visual detection system using a secondary graphics card. I'll put it here, because i cant sign into the forums:

    An Ai visual detection system based on actual color, possibly using an older secondary video card like PhysX can, working in tandem with the game engine. It involves taking a lower resolution screenshot of the player and randomly analyzing a sample of pixels around the player and comparing that to a random sample of pixels of the player and comparing the difference. Players with a separate video card could up the amount of sampling and the resolution of the shots and the amount of shots over time. The difference shouldn't be the only factor of course, player movement speed, Ai current awareness state, etc could factor in. Great for sandbox games where the A.I. comprise the only real antagonists.

  13. Thane – 3D stereographic support is part of the DirectX 11.1 / DXGI 1.2 / WDDM 1.2 feature set for Windows 8. See <msdn.microsoft.com/…/hh404490.aspx> and <http://www.buildwindows.com/&gt;

  14. Mihai Maerean says:

    You can also get the S1023 error if the download doesn't complete. If the browser doesn't manage to download the whole 571 mb file, the executable seems to be valid and the user is able to run it.

    So the download page should state the size of the download (as all download pages on MSDN and Microsoft).

  15. Funbrain says:

    Hi,

    Thanks For Helpful Information

  16. http://www.stroll-air.com/ says:

    I find great information in your blog

  17. play games free online says:

    I really love the way you write this article, it’s seems that you’re very knowledgeable on the subject matter.

  18. Sunmaker says:

    Your step by step explanation is good and informative.

  19. Jens says:

    Thanks Chuck! This solved my s1023 issue in a snap.

  20. Kurt says:

    Solved my problem! Thanks so much! 😀 Let the game development continue…

  21. anon says:

    It should be noted that, for some users you may have to restart your machine (or possibly log off and log back in to the current profile) for the effect of removing the service pack to take place.

  22. Yes, if one of the files was 'in use' at the time, that's quite likely.

  23. Ticked off says:

    I've followed all of these steps and restarted my computer; I am still getting the same error code.

  24. (1) You should check the log file DirectX_SDK.log in the %WINDIR%Logs folder to see what exactly is triggering the problem. The issue and resolution above is specific to the VS 2010 REDIST.

    (2) What are you trying to do with the DirectX SDK? It is quite possible there are other newer ways of getting waht you need.

  25. The fixed worked for me on x64 win 7 pro.

    Thanks!

  26. John says:

    This has not helped me install DirectX SDK (June 2010) .

    I have no entries in the Control Panel -> Add/Remove Programs for MSVC++2010, but DirectX SDK (June 2010)  still refuses to install, giving me erro s1023 during or after "Installing Runtime".

    DirectX_SDK.log says only

    02/26/13 00:12:42: DXSDKSetup: CLR version number = 2.0.50727

    So that's not at all helpful

  27. @John: That's why I recommend the command-line option above. You don't need to find it that way. Also make sure you follow the instructions with FCIV to validate that you are using a uncorrupted copy of the setup program. You also don't mention what OS you are using…

  28. John says:

    I ran the commandline uninstalls first, before even checking in the control panel.

    FCIV gave the right value

    Windows 7 x64.

    I installed the June 2007 sdk to tide me over for the time being, and havent yet retried the June 2010 installer

  29. @John – Can you install Windows 7.1 SDK on this system?

  30. Can I follow these instructions if I have installed VS 2010 (10.0.40219.1 SP1Rel) and VS 2012 (11.0.51106.01 Update 1)?

  31. The problem this is addressing is not affected by VS 2012 or by the VS 2010 product. It's specifically the VS 2010 REDIST packages.

    Note that if you are using  VS 2012, you should be aware of the major changes to the Windows 8.0 SDK that comes with it w.r.t. to the legacy DirectX SDK. You can also use the Windows 8.0 SDK with VS 2010.

  32. Fábio Henriques da Silva says:

    Aew Galera o que ele Falou deu certo esse cara e bom Nota 10 nao tem melhor

  33. ozz says:

    thanks so much! you were very helpful 🙂 regards

  34. Much Appreciated says:

    Thank you 🙂

  35. Jo Ann J. A. Jordan says:

    I am having problems with this on a new Windows 8 laptop, any suggestions would be appreciated.

  36. @Jo Ann JA Jordan – Can you be more specific?

  37. RunningSpace says:

    Everything went well, every step worked properly, issue solved, thank you!!

  38. Daniel says:

    Thank you. Clear and easy. I uninstalled the service pack 1 visual c++ stuff, installed directx and then reinstalled service pack 1. Worked perfectly.

  39. Stefan says:

    Unfortunately, nothing of the above mentioned helped me. I can't get the sdk installed… Is there still someone around who could provide a different way?

  40. @Stefan – What error are you getting exactly? What OS are you using?  Have you eliminated all versions of the VS 2010 Runtime on your system?  Also, what do you need from the SDK?

  41. Shyam Mahato says:

    just uninstall Microsoft Visual C++ 2010 Redistributable Package version 10.0.40219 (Service Pack 1) from the system (both x86 and x64 if applicable) and turn off the antivirous protection then install Direct SDK june 2010

  42. Daniel says:

    Worked! Thank u

  43. Ali Maksum says:

    i have trouble when installing DXSDK JUN 2010.

    i use win 8.1 pro with WMC 64 bit.

    it's say error s1010

  44. S1010 usually indicates that you have a corrupt copy of the DirectX SDK. Use the FCIV check above to verify you have a valid copy.

  45. Ali Maksum says:

    I've already check the File using FCIV. here is the result :

    82663da036401a6b10997e28b4a918a498bbbbd4 . it different from FCIV check in above…

    then.. what should i do..? must i re-download DXSDK..?

    i download it from http://www.microsoft.com/…/details.aspx

  46. You might try clearing your browser cache and re-download it. What do you believe you need it for?

  47. Ali Maksum says:

    I'll try what you recommend first…

    To be true to you…

    i need install this DXSDK Jun 2010 in order to install Football Manager 15.3.2

    it gonna crash dump when i try to open it.

    So, I want to try install DXSDK Jun 2010 in order solve Crash Dump in Football Manager 15.3.2.

    What do you think..? any possible way to solve crash dump in Football Manager 15.3.2 ..?

  48. You never need to install the DirectX SDK which is for developers building games to get a retail game to work. Instead use the DirectX End-User Redistribution Package DXWSETUP or DXSETUP keeping in mind that it doesn't actually "install DirectX".

  49. SAN says:

    Hi, Can you solve this problem please?

    When I opened the DXSDK_Jun10.exe It shows me an error stating that " A DIRECTX COMPONENT MICROSOFT.DIRECTX.AUDIOPLAYBACK.DLL" is being used by other applications.

    Ihave closed all other applications, but still there is an issue.

  50. Make sure you run the installer "as administrator"

  51. dx says:

    hi, i have not installed any 2010 redistributable , still i am getting s1023 error while installing DXSDK_Jun10

    plz help. i am stuck.

  52. @dx – You need to provide a lot more detail: What OS are you using? Do you see the error details in DirectX_SDK.log in the %WINDIR%Logs?

  53. dc says:

    i am using windows 7,  VS2008 is installed in my PC.

    there are 3 files.  will will not paste whole content.

    DirectX.log

    DirectX_SDK.log

    DXError.log

    —————————————————————————————————————————————————

    DirectX.log is ending with

    01/19/16 15:42:27: dxupdate: CMDXInstall::Install(): InstallAssembly() failed, error = 0x80131018.

    01/19/16 15:42:27: dxupdate: DXSError(): FormatMessage() failed, system cannot find message text for error.

    01/19/16 15:42:27: dxupdate: CMDXInstall::Install(): Unable to install Microsoft.DirectX.dll.

    01/19/16 15:42:27: dxupdate: DirectXUpdateInstallPlugIn(): MDXInstall::Install() failed.

    01/19/16 15:42:27: dsetup32: CSetup::InstallPlugIn(): DirectXUpdateInstallPlugIn() failed.

    01/19/16 15:42:27: dsetup32: CSetup::SetupForDirectX(): InstallPlugIn() failed.

    01/19/16 15:42:27: dsetup32: start finalizing: phase: 256 – 256, total: 0 – 27

    01/19/16 15:42:27: dsetup32: Installation ended with value -9 = Internal or unsupported error

    —————————————————————————————————————————————————-

    DirectX_SDK.log is ending with

    1/19/2016 – 11:18:26 AM:

    Initialize log file

    1/19/2016 – 11:18:26 AM: Command Line:

    1/19/2016 – 11:18:26 AM:

    Closing log file

    1/19/2016 – 11:18:28 AM:

    Initialize log file

    1/19/2016 – 11:18:28 AM: Command Line:

    1/19/2016 – 11:18:28 AM:

    Closing log file

    1/19/2016 – 11:18:30 AM:

    Initialize log file

    1/19/2016 – 11:18:30 AM: Command Line:

    1/19/2016 – 11:18:30 AM:

    Closing log file

    01/19/16 15:41:35: DXSDKSetup: CLR version number = 2.0.50727

    —————————————————————————————————————————————————-

    DXError.log ending with

    ——————–

    [01/19/16 15:42:27] module: dxupdate(Jun  2 2010), file: dxupdate.cpp, line: 5783, function: DirectXUpdateInstallPlugIn

       MDXInstall::Install() failed.

    ——————–

    [01/19/16 15:42:27] module: dsetup32(Jun  2 2010), file: dxupdate.cpp, line: 280, function: CSetup::InstallPlugIn

       DirectXUpdateInstallPlugIn() failed.

    ——————–

    [01/19/16 15:42:27] module: dsetup32(Jun  2 2010), file: setup.cpp, line: 1723, function: CSetup::SetupForDirectX

       InstallPlugIn() failed.

    —————————————————————————————————————————————————-

    please help

  54. dx says:

    @Chuck Walbourn – MSFT 1  :- hi, any update?  i really need this on priority. I am stuck.

  55. @dx – First, have you done the FCIV check mentioned above to ensure you have an uncorrupted copy of the DXSDK Setup?

    The problem appears to center on the legacy Managed DirectX 1.1 assemblies. These require the .NET 2.0/3.5 Runtime to be enabled, which it should be on Windows 7. You should try running the latest April 2011 refresh of DXSETUP to see if that succeeds on your system, and manually check to see that you have .NET 2.0 installed.

  56. dx says:

    @Chuck Walbourn – MSFT 1

    Thanks for reply,

    1. FCIV is ok.

    2. Tried to refresh to DXSetup. the hyperlink u have given is going to some japanese microsoft site, so not able to understand what have to be done here . I triend to find any updated version for directx after jun2010 but not able to find one.

    3. tried to installed .net frame 2.0 . It was not already there.

    Getting : This product is not supported on windows vista (but my machine is windows 7)

    I understand there is some issue with the machine.

    but problem is for some reason i cant format / reinstall everything.

    what can be done?

  57. @dx: Sorry, but it sounds like your machine is not in a good state.

  58. @Chuck Walbourn - MSFT says:

    hi,

    That is understood. any way out? repair or something.

    i really cant install win7 again. working at clients end. so not able to do anything.

    plz help. something somehow.

  59. Christopher W. Johnson says:

    Today I ran into the same problem as dx, except I have a fresh install of Windows 7.  I remember running into this installation problem back when I was using VS2010 but I have VS2015 (Community Edition) installed now, with no VS2010 Redistributables installed.  I already had .NET 2.0 installed.

    The only difference between this and previous installations was having VS2015 installed, so I uninstalled the VS2015 runtimes, restarted my computer, and then the DirectX SDK installation worked.

    It looks like the VS2015 redistributables have the same or similar incompatibilities the VS2010 redistributables had.