Error message @ Win 7 Pro start up "There was aproblem starting C:\programdata\ofpviaowu.dat - The specified module could not be found."
Error message @ Win 7 Pro start up "There was a problem starting C:\programdata\ofpviaowu.dat - The specified module could not be found."
This error message appears every time I start (boot) my computer and windows starts (Firefox is not running at start up). Firefox 15.01 functions properly otherwise.
This started after I installed the 15.0.1 patch.
I uninstalled and reinstalled Firefox but the problem remains. Google search for "ofpviaowu.dat" came up with "2012-08-29 Firefox Release 15 Startup Crash Report" as the only listing.
Is this a Firefox issue?
เปลี่ยนแปลงโดย QAMgr เมื่อ
วิธีแก้ปัญหาที่เลือก
My system has this folder: C:\ProgramData\Mozilla\logs\. I don't think Firefox or the update service should write directly to the root of C:\ProgramData\. It could be a configuration error, or it might be completely unrelated.
You may be able to remove the problem .dat file from your startup sequence using Microsoft's Autoruns utility: Autoruns for Windows. If you find an entry, can you describe it?
อ่านคำตอบนี้ในบริบท 👍 1การตอบกลับทั้งหมด (3)
hello QAMgr, i'm not aware of this file being a part of firefox & also find it slightly suspicious that there are no more google search hits. maybe this is malware related... could you do a full scan of your system with the security software already in place and/or a different tool like the free version of malwarebytes?
วิธีแก้ปัญหาที่เลือก
My system has this folder: C:\ProgramData\Mozilla\logs\. I don't think Firefox or the update service should write directly to the root of C:\ProgramData\. It could be a configuration error, or it might be completely unrelated.
You may be able to remove the problem .dat file from your startup sequence using Microsoft's Autoruns utility: Autoruns for Windows. If you find an entry, can you describe it?
Autoruns for Windows found this:
Gpsdutwswyar File not found: C:\ProgramData\Ofpviaowu.dat
I unchecked the item, rebooted, the problem has gone away... Lets see if it stays away...
Thanks for the suggestion!