Question

mfc140u.dll is missing

Laserfiche

Updated January 31, 2019

asked on September 18, 2018

When trying to run the LF Windows Client I get this error:

Faulting application name: LF.exe, version: 10.3.1.479, time stamp: 0x5aac406e
Faulting module name: mfc140u.dll, version: 6.3.9600.18895, time stamp: 0x5a4b127e
Exception code: 0xc0000135
Fault offset: 0x0009d4e2
Faulting process id: 0x1b90
Faulting application start time: 0x01d44f98de892d06
Faulting application path: C:\Program Files (x86)\Laserfiche\Client\LF.exe
Faulting module path: mfc140u.dll
Report Id: 7c5ee758-bb8e-11e8-8166-002590eae486
Faulting package full name: 
Faulting package-relative application ID:

Attempted Solutions I've tried:

1) Uninstall, and download a fresh Rio 10.3.1.181 and reinstall.

2) Download mfc140u.dll manually and place in path stated missing.

3) Install https://www.microsoft.com/en-us/download/details.aspx?id=30679

So far no luck on this issue.

0 0

Answer

SELECTED ANSWER

replied on January 31, 2019

Yes.

Under C:\Windows\SysWOW64, file mfc140u.dll did not exist.

I coped over the file from a working computer and pasted it that location and ran Windows Client and it booted just fine after.

1 0

Replies

replied on September 19, 2018

mfc140u.dll is a system file that normally goes in c:\windows\syswow64. It looks like you installed an older version but the LF installation should have taken care of that. Try running en\Support\vcredist_x86.exe from the LF install package. If that doesn't work, please open a support case so we can troubleshoot the issue.

0 0

replied on September 25, 2018

That didn't work. I will get a support ticket going for it. Thanks!

0 0

replied on January 31, 2019

Was there a solution to this? I have the same error.

0 0

View 1 previous reply

SELECTED ANSWER

replied on January 31, 2019

Yes.

Under C:\Windows\SysWOW64, file mfc140u.dll did not exist.

I coped over the file from a working computer and pasted it that location and ran Windows Client and it booted just fine after.

1 0

replied on January 31, 2019

Running the en\Support\vcredist_x86.exe did not work for me for unknown reasons. Access for the executable was most likely blocked to that SysWOW64 path.

Doing it manual worked for me.

1 0

replied on January 31, 2019

Chase, you are the best.

That worked for me. I also had to copy over vcruntime140 and msvcp140. After those 3 were copied, the Client launched.

Thanks for the fast reply.

0 0

replied on January 31, 2019

You bet.

0 0

You are not allowed to follow up in this post.

Question

Question

mfc140u.dll is missing

Answer

Replies

Sign in to reply to this post.