FAQ (36)

What to Do If the "Cause: failed to avio_open(error=-13)" Error Occurs During Recording

This error may occur because AhnLab V3 or Avast falsely detects oCam as suspicious. Below is a detailed explanation of how to resolve the issue for each antivirus program.


For AhnLab V3, if oCam is being falsely detected, you can resolve the issue by adding the `oCam.exe` file in the oCam installation folder to the scan exclusion list.  

1. Open the AhnLab V3 program.  

2. Go to the Settings menu and find the 'Scan Exclusions' or 'Exclusion Settings' option.  

3. In the 'File/Folder Exclusions' section, click the 'Add' button.  

4. Go to the folder where oCam is installed, for example `C:\Program Files\oCam`, and select the `oCam.exe` file.  

5. Add it to the exclusion list and save the settings.  

6. Run oCam again and check whether recording works normally.


* There may also be a conflict with the anti-ransomware feature.

For example, if drive E is set as a ransomware-protected drive and oCam's save folder is also set to drive E, an error may occur during recording. This happens because the anti-ransomware feature restricts file writing on that drive, preventing oCam from saving the video file.

In this case, keep drive E as a ransomware-protected drive and set oCam's recording save folder to drive C or D instead.

Because drive E is configured as a ransomware-protected drive, file creation and modification are restricted for security purposes, so programs such as oCam are blocked from saving files there. Therefore, the simplest solution is to move the save path to drive C or another unrestricted location.

If you want to continue using drive E, you may also consider temporarily disabling the anti-ransomware setting or adding the oCam executable file (`oCam.exe`) as an exception in the security policy for that drive. 



 

For Avast, if oCam is falsely detected, a pop-up message like the one below may appear. In that case:  

1. In the pop-up, click the 'Allow App' button to register oCam as a trusted program.  

2. This will remove the error and allow oCam to work normally.


If the pop-up does not appear, you can adjust the allow settings manually:  

1. On the Avast main screen, click 'Menu' and then select 'Settings'.  

2. Go to the 'Blocked & Allowed Apps' section.  

3. Click the '+ Allow App' button and add the oCam executable file (`oCam.exe`).  

4. Once oCam has been added to the allowed apps list, save the setting and run oCam again. Recording should then work without any issues.


 


As an alternative, you can also disable part of the protection feature:  

1. Open the 'Protection' menu on the Avast main screen.  

2. Find the 'Ransomware Shield' option and turn it off.  

3. Disabling Ransomware Shield may resolve the error related to oCam.



You can choose and apply whichever method is more convenient. If the problem continues even after changing the antivirus settings, it may also help to contact AhnLab or Avast customer support.


Today's News/Tips

End-of-Support Dates for Windows Operating Systems

End-of-Support Dates for Windows Operating Systems

  • Windows XP
    Release date: December 31, 2001
    End of support: April 8, 2014

  • Windows Vista
    Release date: January 25, 2007
    End of support: April 11, 2017

  • Windows 7
    Release date: October 22, 2009
    End of support: January 14, 2020

  • Windows 8
    Release date: October 30, 2012
    End of support: January 10, 2023

  • Windows 10
    Release date: July 29, 2015
    End of support: October 14, 2025


Since operating systems that have reached end of support no longer receive security updates, it is recommended that you switch to a different operating system for safe use.

OhSoft - secretfolder The File Appears to Be Encrypted
oCam - howto How to Record Gameplay