mso20win32client.dll

[Snowfalcon]

I too am getting CTDs connected to this .dll. I used the repair option in control panel to repair Office 365. Following that P3D 5.1 wouldn't even run. After reinstalling Office P3D did run but I get CTDs in the sim usually clicking on pop ups.

This was noticed and reported by several people in the PMDG Beta test forum which I cannot link to here.

Think we need to find why a Office .dll is interacting with P3D

[Martyson]

I too am getting CTDs connected to this .dll. I used the repair option in control panel to repair Office 365. Following that P3D 5.1 wouldn't even run. After reinstalling Office P3D did run but I get CTDs in the sim usually clicking on pop ups.

This was noticed and reported by several people in the PMDG Beta test forum which I cannot link to here.

Think we need to find why a Office .dll is interacting with P3D

@ Snowfalcon ,

What is your Office 365 version number?

Maybe others in PMDG Beta could post here there Office product name and its version number and also WIN10 version number.

[86SWONAVY]

I must be completely misunderstanding the version of Office I have. I have Home &Student 2019 my thought process is that I have Office 2019. From what I read the latest Office updates are for Office 2010?
Again curious as to how this DLL is connected with P3dv5, and how to update Office to latest version.

Or do I have to subscribe to Office 365, which, at the current moment is NOT installed on my computer.

@ 86SWONAVY ,

You are ok with Office 2019 as far as I can tell.
Comes with Security updates but no Upgrades.

You paid $149 (US) for the software, correct?

"Again curious as to how this DLL is connected with P3dv5, and how to update Office to latest version."
I am not having that problem with MS 365.
Maybe give Office Support a call or E-mail.

Concur with requesting assistance from the Microsoft team. I have a sneaking suspicion they will point finger at P3D. However whats the worse that could happen by asking for help?

[Snowfalcon]

Office version 16.0.13426.20404

[Snowfalcon]

Just reinstalled this dll with a "clean" version downloaded from Microsoft. Ran P3D clicked on a pop up and got this:

Faulting application name: Prepar3D.exe, version: 5.1.12.26829, time stamp: 0x5fb44f72
Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5fd1d17d
Exception code: 0xc0000005
Fault offset: 0x00000000000533cd
Faulting process id: 0x1a50
Faulting application start time: 0x01d6dcbc26422e07
Faulting application path: E:\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
Report Id: 2e954b57-1348-44d3-a96b-1d38821270f3
Faulting package full name:
Faulting package-relative application ID:

I uninstalled Office 365: Now P3D won't run at all.

[Martyson]

@ 86SWONAVY ,

From your first post:
Faulting module name: mso20win32client.dll, version: 0.0.0.0,

Faulting application path: B:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll


Could you verify you have a “B” drive?


Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll

Could you verify what is inside this folder:
C:\Program Files\Common Files\Microsoft Shared\Office16

[Snowfalcon]

After checking my system. There is no MSO20WIN32CLIENT.DLL in the location

C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll

Still why is P3D trying to access this windows dll??

[Martyson]

@ Snowfalcon ,

P3D is not causing the problem, IMO.

"mso20win32client.dll"

Do you have MS Office 32 bit or MS Office 64 (for 64 bit OS)?

Reboot your PC.

Wait a minute.

Look in the Task Manager.

Background Processes.

Are any MS Office processes listed?

Note:
I mentioned earlier it may require support from MS Office to determine your Office purchase / setup on your PC.

[gsnde]

I understand office is running fine for the people who report the issue. So I don’t expect MS Office Support can help in any way. How should they support another application failing? How should they understand why removing their application leaves another application unworkable?

[Martyson]

I understand office is running fine for the people who report the issue. So I don’t expect MS Office Support can help in any way. How should they support another application failing? How should they understand why removing their application leaves another application unworkable?

@ gsnde ,

This topic is about mso20win32client.dll

Do you know what it is?

Do you know where it is supposed to be?

Do you know what normally causes an error naming it?

Do you have MS Office installed on your PC?

[gsnde]

Sure, I can help you.

Do you know what it is?

It is a Microsoft Dynamic Link Library and part of their Microsoft Office Suite. As such it gets installed if you have either the full Office Suite or parts of it, e.g. Visio, Project or Access. Microsoft rarely publishs the purpose of their DLLs, understandable since Office 365 adds 1.045 in the program folder alone, not counting those that are installed into %windir%. So the specific purpose of this DLL is not something I can tell you for sure, but license validation is a pretty good candidate.

Do you know where it is supposed to be?

Well, that depends a bit where you have installed your Office and if you have the 32 or 64 bit version. I explain it to you according to my setup - the folder structure within the Office applications are the same, no matter what drive or main folder you use.

32bit location:
C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\OFFICE16

64bit location:
C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16

Do you know what normally causes an error naming it?

Like all errors from libraries that are so tightly integrated into the OS there are a bunch of reasons. License validation seem to be related to that specific DLL. In an environment where SSO was blocked by the GPO: Office 2016 / Miscellaneous / "Block Signing into Office" the crash went away after changing the GPO. But that is just one example.

Do you have MS Office installed on your PC?

Yes, I have.

[Martyson]

@ gsnde ,

Do you know what it is?
“the specific purpose of this DLL is not something I can tell you for sure,”

Possibly Office support could if they were contacted about the mso20win32client.dll error in this situation


Do you know where it is supposed to be?
“ I explain it to you “

I already knew, I was asking you if you knew.
https://www.ryadel.com/en/microsoft-off ... -versions/


Do you know what normally causes an error naming it?
“Like all errors from libraries that are so tightly integrated into the OS there are a bunch of reasons.”

Possibly Office support could if they were contacted about the mso20win32client.dll error in this situation

Do you have MS Office installed on your PC?
“Yes, I have.”

Have you had an Office mso20win32client.dll error on your P3D setup?

[gsnde]

Possibly Office support could if they were contacted about the mso20win32client.dll error in this situation

I don't think so. People in support are neither qualified nor do they have the resources to explain development details of their companies applications. But even more they are not paid to do so, and in many cases not allowed to do so. I have used both Microsoft business and private support, in case this would be your next question.

MS will ask why they want to know. They could answer that another, non-MS application crashes due to this DLL. MS will tell them to contact the support of the other application.

I already knew, I was asking you if you knew.
That is mighty nice of you to test my knowledge :-)

https://www.ryadel.com/en/microsoft-off ... -versions/
That is a very thorough summary of the default locations of the MS Office installers!

Have you had an Office mso20win32client.dll on your P3D setup?
Nope, I have separate office and simulation computers.

[Martyson]

@ gsnde ,

Possibly Office support could if they were contacted about the mso20win32client.dll error in this situation

“I don't think so.”

That is the problem.
You are not sure.


Have you had an Office mso20win32client.dll on your P3D setup?
“Nope, I have separate office and simulation computers.”

So you cannot offer first hand follow up information, actual test results, on this reported problem.

[gsnde]

Thanks for helping me understand that I cannot offer support here!

You know how MS support reacts on specific questions and that one cannot abstractly analyze computer issues, so I leave this in your experienced hands.