Windows 10: How to troubleshoot Desktop DLL Mso20win32client.dll version 0.0.0.0 time stamp 0x62e7d99 ?

I need help related to Mso20win32client.dll either one of the following:how to know if it is corrupted?how to repair?what is latest version ?what is time stamp 0x62e7d99I have tried repair PowerPoint which did not resolve crashing and involved Module Mso20win32client.dll ; My question arise because DLL files are extremely vulnerable to problems as per:what makes DLL files so convenient and efficient, also makes them extremely vulnerable to problems. If something happens to a shared DLL file, either it goes missing or gets corrupted in some waySign out of Office and then sign back in to Office

:)

 

failed to load dll 0*80020702

failed to load dll 0*80020702

 

KERNEL32.DLL!UnknownFunction (0x00007ffa959e26bd) + 0 bytes [UnknownFile:0]

Hey there,

Currently trying to play Ark on Epic games and getting a kernel error. Don't know what to do about it. Details listed below.

Fatal error!







VERSION: 356.1

ShooterGame.exe!FLatentActionManager:rocessLatentActions() (0x00007ff758d5bbd5) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\latentactionmanager.cpp:26]

ShooterGame.exe!AActor::Tick() (0x00007ff758b847bd) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\actor.cpp:803]

ShooterGame.exe!AMatineeActorManager::Tick() (0x00007ff758d27796) + 8 bytes [f:\build\lostisland\engine\source\runtime\engine\private\interpolation.cpp:9983]

ShooterGame.exe!AActor::TickActor() (0x00007ff758b8475e) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\actor.cpp:789]

ShooterGame.exe!TGraphTask<FTickTaskSequencer::FTickFunctionTask>::ExecuteTask() (0x00007ff758f6561e) + 31 bytes [f:\build\lostisland\engine\source\runtime\core\public\async\taskgraphinterfaces.h:871]

ShooterGame.exe!FNamedTaskThread:rocessTasksNamedThread() (0x00007ff7583c6178) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\async\taskgraph.cpp:939]

ShooterGame.exe!FNamedTaskThread:rocessTasksUntilQuit() (0x00007ff7583c532d) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\async\taskgraph.cpp:680]

ShooterGame.exe!FTaskGraphImplementation::WaitUntilTasksComplete() (0x00007ff7583c815c) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\async\taskgraph.cpp:1777]

ShooterGame.exe!FTaskGraphInterface::WaitUntilTaskCompletes() (0x00007ff758478d69) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\public\async\taskgraphinterfaces.h:320]

ShooterGame.exe!FTickTaskSequencer::ReleaseTickGroup() (0x00007ff758f2af94) + 144 bytes [f:\build\lostisland\engine\source\runtime\engine\private\ticktaskmanager.cpp:188]

ShooterGame.exe!FTickTaskManager::RunTickGroup() (0x00007ff758f2eff2) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\ticktaskmanager.cpp:867]

ShooterGame.exe!UWorld::RunTickGroup() (0x00007ff758d6ef1b) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\leveltick.cpp:697]

ShooterGame.exe!UWorld::Tick() (0x00007ff758d7020f) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\leveltick.cpp:1214]

ShooterGame.exe!UGameEngine::Tick() (0x00007ff758c9a170) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\gameengine.cpp:1195]

ShooterGame.exe!FEngineLoop::Tick() (0x00007ff75644b9f9) + 0 bytes [f:\build\lostisland\engine\source\runtime\launch\private\launchengineloop.cpp:2647]

ShooterGame.exe!GuardedMain() (0x00007ff75644634c) + 0 bytes [f:\build\lostisland\engine\source\runtime\launch\private\launch.cpp:140]

ShooterGame.exe!GuardedMainWrapper() (0x00007ff75644cf6a) + 5 bytes [f:\build\lostisland\engine\source\runtime\launch\private\windows\launchwindows.cpp:125]

ShooterGame.exe!WinMain() (0x00007ff75644d0b9) + 8 bytes [f:\build\lostisland\engine\source\runtime\launch\private\windows\launchwindows.cpp:213]

ShooterGame.exe!__tmainCRTStartup() (0x00007ff759ff5811) + 21 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618]

KERNEL32.DLL!UnknownFunction (0x00007ffa959e26bd) + 0 bytes [UnknownFile:0]

ntdll.dll!UnknownFunction (0x00007ffa9774dfb8) + 0 bytes [UnknownFile:0]

ntdll.dll!UnknownFunction (0x00007ffa9774dfb8) + 0 bytes [UnknownFile:0]

 

Bad Image Errors - dll files changing to 0 bytes

Hi
Have an unusual problem (to me anyway)

Last week I got "Bad Image" errors with Adobe Lightroom (the program had worked OK previously). Two .dll files were listed as corrupt and in Explorer both were shown has having 0 bytes size. Re-installation resolved the problem.
Today I have had the same "bad image" error with another program. Techsmith SnagIt. Once again it was .dll files and they show in explorer as 0 bytes. The timestamp on the 0 byte dlls is the time of the error i.e. today (not when the files were installed).

What I've done so far :
Ran McAfee viruscan across all disks - no problems reported.
Ran Malwarebytes - no problems reported

Went to the properties for the disk drive and under "Tools" ran error check - nothing found
The disk is an SSD so I went to Samsung Magician which shows drive condition as good and S.M.A.R.T. shows wear levelling count at Current Value 99. I do not use Rapid Mode.

The problems are happening on a Samsung 850 Evo 500GB

Any suggestions welcome

Dave