Hi, Waft rax
Welcome to the Microsoft Community.
Thank you for your feedback. The “an internal system error occurred” error while installing the DirectX SDK can usually be caused by corrupted system files, permission issues, or incompatible system settings. Since you have already tried SFC scanning to repair the system files, here are some troubleshooting options:
- Check the log files
The error message suggests checking dxerror.log and DirectX.log, you can find them via the following paths:
Open File Explorer and go to C:\Windows, find and open these log files to view the error messages in them.
Depending on the specific error messages recorded in the logs, you may be able to find more clues.
I will send you a private message where you can send me the logs.
- Install DirectX SDK with administrator privileges
Sometimes insufficient permissions can cause the installation to fail, try right-clicking on the DirectX SDK installer and selecting “Run as administrator”.
This will ensure that the installation process has sufficient system privileges.
- Installing the Visual C++ Redistributable Package
DirectX SDK relies on Visual C++ Redistributable components, and missing them may result in installation errors. You can download and install the latest Visual C++ Redistributable version from the Microsoft website.
- Check DirectX file integrity
You can try to check the integrity of DirectX by using the DXDIAG utility:
Press Windows + R, type dxdiag and press Enter.
In the DirectX Diagnostic Tool interface, look for any missing files or errors.
- Using the DirectX Web Installer
If you just want to get the DirectX files, you can use Microsoft's DirectX Web Installer, which will automatically detect and install the missing DirectX components.
If none of the above methods work, you can try an in-place upgrade which will refresh your windows and will not delete your data, but for important data, it is still recommended that you back up.
How to run In-place upgrade in Windows 11 - Microsoft Community
I look forward to your feedback.
Best Regards,
Aaron| Microsoft Community Support Specialist