Directx 11 Web Installer

0 views

Skip to first unread message

Darios Uclaray

unread,

Aug 3, 2024, 5:38:56 PM8/3/24

to kunretare

Not really that much of a nuisance, but every time I update to a new beta, The installer asks me if I want to install DirectX. I click no and it gives me an error message, rather than just finishing the installation. Again, not a major bug, but a bug nevertheless in my opinion.

Clicking no is the cause of the error as the installer that LB is requiring isn't running to completion. Click yes if you don't want to see the error message. Respectfully this is definitely not a bug.

Why would i want to reinstall directx everytime i want to update launchbox? And if its not a bug, and clicking no makes the installer not going to completion, why would it let me select yes or no? Sounds like one of those weird "its a feature" arguments to me

I have experienced a lot of installers, and most of them just have an option of ticking the additional software (like directx), so it gets installed or not, and it doesnt give you an error, if you untick it. Maybe you could do it that way then.

Yeah that part has nothing to do with me and I guess an option to not download DX would probably prevent that but really I assume if you choose yes it probably just checks the latest version against what you have. If it needs to download something it does if not it just finishes At least that is how running the DX installer from MS works, if you have the newest version it just tells you so and it doesn't install anything. I imagine most of the users just let it run.

Yes. The only way to check if DirectX is installed is to run that installer, which requires admin rights. I have removed that DirectX check for updates in the past, but all it did was cause us multiple headaches and end users ended up with errors that they couldn't troubleshoot because of missing DirectX libraries. So as much of a headache as it is to some people, it's staying for good.

Hi guys, I know some folks have gotten this fixed already, but even if this is resolved, we'd like to take a look at some error logs to prevent the issue from occurring going forward/

If you were affected by this can you DM me your install logs for the game.

You'll find them at C:\Program Files (x86)\Origin Games\Apex\__Installer\InstallLog.txt by default.

I'm not able to DM you (Access is apparently denied), but here is the install logs for my secondary computer attached to this message. I got it fixed by going to the Origin Games\Apex\__Installer\directx\redist file and deleting everything except the DSETUP.dll, dsetup32.dll, and DXSETUP.exe.

Okay ... I am doing a new build and I had FSX on a different drive and I created a shortcut to get to it. Now I am getting an error message ... Flight Simulator cannot run because the version of Microft DirectX installed on your computer is incompatible. Please reinstall DirectX 9.0 by running flight simulator setup, or douwnload the current version.

@ Th1racer - Your issue is probably related to a fairly well known issue regarding Win 10. Win 10 does not ship with DX9 by default. As you have only copied over the FSX files you would not have any DX9 related files as they are System files and are stored outside of FSX. Even if you had the discs you will still have problems as the version of DX9 included on the discs is woefully out of date and are known to be incompatible with Win 10....

2. Right click on the saved .exe and select Run as Administrator from the options listed. Let the installer do its work. NOTE that the redist pack includes files for DX9 (versions A to c), DX10 and DX11. The install process will check for what versions are installed and then install missing versions and/or replace missing, corrupted or invalid files of any version already installed.

Other things that you both need to consider is what other essential 'library' files may be missing, especially with Win 10 as, by default, it ships without some of the earlier versions of such 'libraries' that FSX relies on. The main essential ones are:

You will need to download the relevant 'bit' version for your OS (i.e. 32 or 64 bit). Click on the required link and a standard download option box will appear - DO NOT run the installer from this but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Install each package separately, starting with the oldest version, and reboot using the appropriate option for your OS version stated above between each install.

It is worth pointing out that you can have multiple versions of these 'libraries' installed. They are not just required by FSX but are used by many programs and apps. They will work happily along side each other and a program or app will automatically use the most compatible version.

I did the same thing. Copied all my files to the new drive, but after I got the directx issue straighten out FSX would stop working when I tried to load the program. I had to delete everything and start from scratch, which meant reinstalling steam ... then it took 9 hours to install FSX ... I don't recall it taking that long when I first install it. But unfortunately you have to start all over again.

Steam is actually best viewed as having two parts - the Client (which acts as your gateway to your account, the Steam website/shop, etc) and the Library (this is where your downloaded content is stored)

By default, when you first install Steam and create your account all that is there is the basic Client. As part of the installation it creates a sub folder called SteamApps. A further set of subfolders are also created within this folder, one being called Common, and it is this folder that becomes, by default, the Library location.

Using the tools available via your account library settings, you can dictate where new content is installed (either for all content or on a product by product basis) or move previously installed items to a new location. It must be noted that Steam will always use the SteamApps\Common part of file naming structure irrespective of what you name the root target folder. I.E if you were to move game A to a new drive the folder structure will look like this example:

As I don't use pedals I have not directly encountered this type of problem. I have seen other threads relating to this type of issue and many seem to be resolved by installing the latest available driver/software for the device.

WRT to it not being listed have you checked ALL controller related settings. When you first go the page it lands on the Calibrate page but if you click on the other two tabs you may find that is appears under one of those.

Another option would be to disconnect the pedals, throttle and stick and then reboot the PC. Then reconnect each item starting with the pedals (using a different USB slot than previously used) and see what happens .

The only other advice I can offer is to use google to search for solutions specific to the brand of pedals that you are using. The search will probably throw up links to many of the flightsim threads relating to the issue.

Option 2 - Insert FSX disc TWO into the drive and stop it from auto-running. Right click on the drive icon and select OPEN from the resulting menu. This will show the contents of the disc. Scroll down the contents to located a file named msxml - it will have a standard MS Windows Installer icon. Double click on the file to run the program. Once the installer has done its work reboot and test FSX.

Option 3 - Go to this MS PAGE and download a version compatible with language version you have. As you are using Win 10 a possible relevant point to make here is that, if you have the English version of the game and methods 1 or 2 resolves the issue, it may still be beneficial to download and install the English version of this file.