Member Avatar for Arikay

Sometime back we bought a new computer and practically out of the box we have been getting error messages "ordinal 313 oleaut.32.dll could not be located" or something similar. I also have gotten the message "olaeaut.32.dll is outdated" I have googled this dll and have downloaded and installed (I think) a new copy of it but to no avail. My next step is to try to copy it from another computer and place it in the malfunctioning one but before I really screw things up I thought I ought to seek the advice of some folks who may know more about this than I do. With the dll not working right I cannot download certain programs (ironically like ones that will allegedly fix broken dll's!!) or get AOL to work (a problem because my kids like to use the computer in question. Any suggestions??

  • 2 Contributors
  • 2 Replies
  • 102 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Arikay

Dani AI

Generated

Quick note for and anyone who finds this thread later: the error points to a mismatch or corruption of the OLE automation library that Windows provides. Replacing that file from random web sites or from a machine with a different Windows build often makes the problem worse. ’ intent to replace the file is understandable, but try the safer, built‑in recovery steps first.

Run the System File Checker from an elevated command prompt:
sfc /scannow
Let it finish and reboot. On Windows 8/10/11, if SFC reports problems it cannot fix, follow with:
DISM /Online /Cleanup-Image /RestoreHealth
These repair the protected system files and normally restore the correct oleaut32 without manual file swaps.

Check a few basics before replacing files: confirm the OS edition and whether it is 32‑ or 64‑bit (System or About page), note which program triggers the error (AOL was mentioned), and scan Event Viewer for application errors to see what exactly is failing. If an app is at fault, uninstall/reinstall that app after the system repairs. Also install all Windows updates and any vendor-provided patches.

If SFC/DISM fail or the machine is new and still under warranty, consider a repair install, System Restore to an earlier point, or vendor support rather than manually overwriting system DLLs. If manual replacement becomes unavoidable, use official sources (installation media or Microsoft updates), back up the original file and create a restore point first. Avoid untrusted DLL download sites.

Recommended Answers

All 2 Replies

Member Avatar for TT4Titans

Did you get this problem fixed?

If not where did you get the copy you downloaded and where did you put it on your computer?

If you didn't get it fixed get the file here.

/http://www.dll-files.com/dllindex/dll-files.shtml?oleaut32/

put it in your windows/system32 folder.

if it says it can't because it is being used by another program do it in safe mode.

Member Avatar for Arikay

Thank you--I'll give it a try!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.