Subscriber Kurt wrote about a troubling, recurring file missing or file corruption problem:
Terry, I’m having a problem with probable corruption of the urlmon.dll on my system. I’m running Windows 7 Professional on a system I build myself (because I wanted lots of power in my system). Certain programs give me the following message "unable to access ordinal459, file is either corrupted or missing from the urlmon.dll."
I’ve tried all of the fixes I could find on the internet to repair the problem and they always fail. The only fix I’ve found is to run an upgrade of Windows 7 from my original disk. This always makes the issue clear up but only for about 24 to 36 hours. After that period of time the error reappears. I’ve done backups immediately following the repair, thinking I could just install the backed up files to get rid of the corrupted files. WRONG! The file remains corrupted following the re-installation of the back up.
At this point I’m out of ideas on how to fix this issue. Do have any ideas on to permanently fix this urlmon.dll issue?
Thanks in advance, Kurt
I hadn’t seen the problem before, but I could suggest some steps to help him define what was happening.
I suggested that he do his fix, find the urlmon.dll file and note the date and time of it. Screenprint it for documentation.
Then, when it happens again, I suggested that he should check the date and time on the file.
He shouldn’t be having the problem — if he is, something may be changing the file to a different version or even a version that contains malware.
I advised him that, if he has an infection that keeps changing the file even after a Win7 repair, then it’s probably time to reinstall — or, if you use Acronis True Image, a restore from an older (a non-current) backup image, that is, one from before the problem started occurring.
Kurt wrote back to say:
Terry, thanks for your suggestions. I did everything you said, I even found a malware buried deep in my system. I removed it, reinstalled windows and McAfee’s. The system worked for about 48 hours and the problem re-appeared.
At this point I figured out that whenever McAfee’s tried to update itself it would corrupt the urlmon.dll file. So I contacted McAfee’s and the problem was elevated to the programmer stage and it was found that IE on my system wasn’t ever upgraded from the installation of Windows. IE has crammed so many bells and whistles into their browser that it was constantly crashing. So I switched to Firefox.
Well it turns out that McAfee’s uses IE exclusively to update itself. So I updated IE to the latest version (I have a 2.6 Terabyte drive which leaves me plenty of room to waste on programs I don’t really use, like IE.) and I re-installed McAfee’s to its latest version and dat file.
Results? It worked. I didn’t have to re-install Windows and everything appears to be working fine. I’ll give it a few days of non-problem running before I declare this a total success.
Thanks for your assistance and maybe your readers can use this information if they are experiencing these problems.
Thanks and Happy Thanksgiving (if you celebrate it)