Wordpad error

[ilikefree]

OK this one has me stumped. Wordpad runs fine, in fact everything seems to run fine but after running system file checker it tells me I have corrupt files and has successfully repaired them, but then Wordpad fails to start."entry point not found" and an error in ole32.dll
System restore returns Wordpad to a working state again.
Any ideas please

 

[Vistaar]

Hello ilikefree. I can only tell you that the last version of WINDOWS\System32\ole32.dll specifically for Vista was:



It was last analyzed at VirusTotal on 2019-10-22. If you never patched Vista to EOL due to the well-known Windows Update issue, then you would have an older version of ole32. I wonder what file(s) are reported as repaired in the CBS log.

 

[ilikefree]

My file version is 6.0.6002 24078
It worked fine before sfc/ scannow but after entry point not found
System restore fixed it, sort of
I will look into the scan logs tonight

 

[townsbg]

Receiving an Ole32.dll Error? Here's How to Fix It

A troubleshooting guide for ole32.dll is missing and similar errors. Don't download ole32.dll; learn how to fix the problem the right way.

www.lifewire.com

 

[Vistaar]

My file version is 6.0.6002 24078

What is its "Date modified"? If you upload it to VirusTotal, does it match a previous submission?

 

[ilikefree]

Virus total says no engines detected this file
CBS log file was missing, no log file to check

 

[Vistaar]

Virus total says no engines detected this file
CBS log file was missing, no log file to check

I'm still curious about the "Date modified." Have you installed any Windows 6.0 updates earmarked for Server 2008 SP2 since April 2017? System restore probably obliterated the CBS log.

 

[Vistaar]

I just remembered that sfc /verifyonly scans for corrupt files without attempting repairs, which might be useful in your case.

 

[wither 3]

I did a search on the file version for OLE32.dll which ilikefree says he has. I found this-

KB4014793: Microsoft Wordpad Remote Code Execution vulnerability (April 2017)

Might be worth looking to see if the referenced update is installed.

By the way, I forget what we did to turn my version of Vista into 6.0.6003, but the OLE32.dll version is 6.0.6003.20512.

 

[Vistaar]

I did a search on the file version for OLE32.dll which ilikefree says he has...

Hi wither 3. I do have KB4014793 installed, and to my surprise it installs both version 19755 (reported by me) and 24078 (reported by ilikefree):


After some head-scratching, the explanation is that I looked at ole32.dll in System32, whereas ilikefree looked at the same filename in winsxs:



So ilikefree and I actually have the same version, and we are getting nowhere with solving his issue.

By the way wither 3, how has Windows 6.0.6003 been working for you? Any black screens or broken software? I wouldn't expect any.

 

[wither 3]

You should have the first 3. For some reason, I thought you had updated to 6.0.6003.
The ole32.dll version that I referred to earlier, was for the file in System32. It's the same as in Syswow64.-

6.0.6003 has been fine. Haven't taken the time to look back in the forum to see how I got there.

 

[ilikefree]

My file was in system32
Will look at the link given, thanks

 

[ilikefree]

I have KB4014793 it was installed in August

 

[Vistaar]

My file [version 24078] was in system32

That MIGHT be your entire problem. I have double-checked, and the version in System32 is definitely 19755 - NOT 24078:



I would still suggest running sfc /verifyonly and studying the CBS log before taking any action. In case you wonder, it does not find any integrity violations on my Vista x86 system:



One possible course of action might be to uninstall KB4014793 from Installed Updates, check System32, then reinstall the update. Another might be to manually replace 24078 in System32 with a copy of 19755 from winsxs (it can also be found there). (Edit: Scratch Plan B.) Good luck!

 

[ilikefree]

OK I uninstalled the update KB4014793 and my ole32.dll file version changed to 23936
I ran sfc /scannow and no integrity violations were found
Wordpad is still openinmg so problem fixed
No idea why an update installed in August should start causing problems now but all seems well now
Note my file version is not the same as what you have

 

[wither 3]

isn't that special. When I look for that version of ole32.dll, I get this-

https://support.microsoft.com/en-us/help/3146706/ms16-044-security-update-for-windows-ole-april-12-2016

 

[Vistaar]

OK I uninstalled the update KB4014793 and my ole32.dll file version changed to 23936
I ran sfc /scannow and no integrity violations were found
Wordpad is still openinmg so problem fixed
No idea why an update installed in August should start causing problems now but all seems well now
Note my file version is not the same as what you have

If you uninstall an update that installed a newer file version, then you should of course end up with an older file version. I have no idea about your issue either, and only focused on ole32.dll because it was the only detail in post #1. (If I had your issue, I would want to look at a CBS log.) CVE-2017-0199 (addressed by KB4014793) did affect WordPad as well as Microsoft Office. It occurs to me that there could be some legitimate reason why we did not have the same file version in System32. I wonder what would happen if you reinstalled KB4014793.

 

[ilikefree]

I might make a restore point and do that later tonight

 

[ilikefree]

I had been using wordpad until a few days ago without any errors in sfc/ scannow

 

[wither 3]