Author Topic: invalid arx on *some* machines  (Read 2518 times)

0 Members and 1 Guest are viewing this topic.


  • Newt
  • Posts: 31
invalid arx on *some* machines
« on: September 06, 2021, 11:08:49 AM »
Hi there,

recently a customer of ours has problems loading an arx for AutoCAD 2018. Unfortunately not on all computers - one of them loads the arx successfully. It makes no difference whether the file ought to be loaded from a network share or locally.
I had the opportunity to save sessions via Process Monitor when it succeeded and also on one of the machines that says, that it is an invalid arx. The only process touching the arx in both cases was acad.exe. No virus scanner, nothing else. The general pattern of operations seems to be CreateFile - CreateFileMapping - ReadFile with some CloseFile intersparsed.
I attached the logfiles, filtered on the path with the arx, just in case anyone cares to look inside  :whistling:
I also used the tool "DependenciesGui.exe" from After adding the AutoCAD bin path to the search folders the only file marked was "C:\Windows\system32\OLEAUT32.dll" and I think "C:\Windows\system32\mfc140u.dll", both of which are also highlighted on my machine which successfully loads the arx. Maybe one thing of interest is that the arx includes another dll and if this one is not included (during compilation), then the arx also gets loaded on those machines that otherwise say it is an invalid arx.
I'm totally lost and hope anyone has a hint what else to do to find a solution.

Thanks in advance, Bernd

It's Alive!

  • Retired
  • Needs a day job
  • Posts: 7488
  • AKA Daniel
Re: invalid arx on *some* machines
« Reply #1 on: September 07, 2021, 06:43:07 AM »
you're using VS2015(V140) and targeting windows 8.1?
I remember there being issues with one or some of the updates for visual studio 2015, maybe you need to add a C++ runtime to your installer


  • Newt
  • Posts: 31
Re: invalid arx on *some* machines
« Reply #2 on: September 07, 2021, 08:09:03 AM »
No, both machines are running Windows 10 (build 19043.2) :-(