Jump to content

can not start the game with LW mod (0xc0000142)


fanxianyin

Recommended Posts

Before I install the Long War Mod, I can play the original game. It works well.

 

However, after the LW mod was installed, it went wrong.

 

it shows: can not start normally(0xc0000142)

 

Did I miss something?

 

PC with win10, bought last week.

 

Link to comment
Share on other sites

Some part of this standard reply is now causing the post to get blocked. So I am going to try posting it in "chunks" of separate paragraphs to isolate what is causing the problem.

 

Paragraph 1:

Please see the "Basic Guide to installing mods"; the "Environment" section in particular. Absolutely DO NOT install into the default "C:\Program Files" folders. LW makes this a condition for the same reasons.

-Dubious-

Link to comment
Share on other sites

(Doesn't seem to be the use of embedded URLs.)

 

Paragraphs 2:

 

Likely you will need to run the game in a "Win7" compatibility mode. Additionally, while Win10's DirectX12 includes support for DX9, at the time it was released, the game was designed to look for DirectX9 files with specific versions in the file names (i.e. d3d9_32.dll). Later versions of DirectX might be "backwards compatible", but the file names are not the same and the game does not recognize them as being equivalent.

-Dubious-

Link to comment
Share on other sites

Paragraph 3:

 

Is your version of Windows 32 or 64-bit? (32-bit may require "BOOT[dot]INI" changes to use more than 2GB of memory. See this 2-4GB game memory limits and solutions article.) XCOM EU/EW/LW is a 32-bit game, so you need the 32-bit versions of any downloadable tools or libraries, like "C++ Runtimes" or "DirectX drivers" installed on your 64-bit system. 32-bit libraries are not interchangeable with 64-bit versions. They install to different locations. There is a reason MS makes both versions available.

(This caused problems when I used a "period" in place of "[dot]" in the "BOOT" filename in the first sentence. Never was a problem before.)

 

-Dubious-

Link to comment
Share on other sites

Remainder of the paragraphs:

 

Some games try to install an older DX version they come bundled with. Those versions may not be compatible with the later versions of Windows, which is why you should manually install the version you know is compatible. Then those games will see that DX version is already installed and not try to install their bundled version causing incompatibility problems.

  • When the DX installer asks where to install the files to, you choose any folder you like, but generally have it unpack the files to a folder on the desktop or one dedicated to that purpose anywhere, because this folder can be deleted or emptied after the final install is done. (DirectX does not actually get installed at this point. The files are only 'unpacked' from an archive)
  • Once the files are unpacked to this folder you open the folder and locate DXSETUP.exe (the actual installer).
  • Run this installer (as an Administrator) to finalize the DirectX re-installation.
  • When the installer is finished delete this folder.

Each game uses a specific DX file, or files, (e.g. d3dx9_32). A newer game may use two DX files (e.g. d3dx9_42 and d3dx10_42).

See the MS article How to make Win10 run DirectX 9.0 for more details.

Thanks for your patience. Hope this resolves your problem.

 

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...