All of those missing cab files are likely just install things that don’t matter. My guess is it looks for all possibly available cab files, and installs them if they were packed with the installer. It’s sloppy, but nothing can be done about that.
This installer attempts to load a dll, which fails to load. That’s not good:
Failed API: LoadLibrary()
Error: (1114) - A dynamic link library (DLL) initialization routine failed.
It tries to continue on, but of course without all of the proper resources loaded, you get:
LoadDSetup32() failed. - in the function DirectXSetupGetEULAW
My guess is that is the function that is supposed to open the Installer window and bring up the EULA, which fails, as the necessary library inclusions failed, which are almost certainly core Windows libraries for handling processes and windows.
Failed API: CloseHandle()
Error: (6) - The handle is invalid.
^ The handle is referring to the process that is supposed to be running right now, namely the EULA/Installer process. It is blank, because it didn’t initialize, likely in the LoadDSetup32() function.
Basically, the installer process can’t load properly, which would explain the odd behavior. It is quite possible your OS has some major issues.
You could try running some basic repair commands from an Elevated cmd window.
sfc /scannow
^ Will check to make sure all core OS files are in tact and will replace them automatically, if necessary (may require a restart once complete). It never hurts to run that command.
Without the machine in front of me, all I can say is there are some deep issues going on, that likely go beyond DirectX alone.