Resolving "No ARF File Found" Error Due to PowerShell Timeouts
This article addresses the "No ARF File Found" error encountered during CYRISMA vulnerability scans. This error typically results from PowerShell timeouts or I/O exceptions that interrupt the scan process.
Written by Liam Downward
Updated at May 28th, 2025
- User Manual
- Self Onboarding Guide
- Agents
- The Cyber Risk Assessment Process
- PSA Integrations
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- API Documents
- CYRISMA Change Log
- Support Ticket SLA
- Billing Questions
Table of Contents
What is an ARF File?
The Asset Reporting Format (ARF) file contains the results of the full vulnerability scan performed by the CYRISMA agent. When this file is missing, it indicates the scan did not complete successfully.
Root Cause
The scan process in CYRISMA runs in two stages:
Preliminary Checks – These gather basic data (open ports, weak SSL/TLS cipher suites) using registry queries.
Full Vulnerability Scan – This step inspects the OS and 3rd-party applications for known vulnerabilities.
The "No ARF File Found" error appears when PowerShell or the underlying system fails during the second stage, often due to:
- PowerShell startup delays
- Timeout exceptions
- I/O errors or corrupted PowerShell environments
Diagnostic Steps for PowerShell Health
Follow the steps below to diagnose PowerShell issues on affected machines.
1. Launch PowerShell as Administrator
or
If the console fails to start or is significantly delayed, it may indicate corruption.
2. Run Basic Test Commands
Failures or long delays suggest misconfiguration or deeper system issues.
3. Check Execution Policy
Errors or timeouts here may be policy-related.
4. Launch Without Profile
If this works correctly, the issue may lie within a corrupt profile script such as Microsoft.PowerShell_profile.ps1.
5. Check Event Viewer
Open Event Viewer:
Go to Windows Logs > Application or System
Look for PowerShell-related errors or Application Errors
Remediation Steps
A. If Profile Script Is the Problem
Rename the user profile script:
B. Repair Windows PowerShell (v5.1)
Open Command Prompt as Administrator and run:
C. Reset PowerShell Core (pwsh)
Uninstall PowerShell Core from Apps & Features
Download the latest release from the PowerShell GitHub Releases
Reinstall and confirm functionality
Temporary Workaround
If built-in PowerShell remains non-functional:
Use CMD, WSL, or Windows Terminal
Alternatively, download and run the portable PowerShell Core ZIP edition and execute pwsh.exe directly
Conclusion
The "No ARF File Found" error is typically a symptom of interrupted scan execution due to PowerShell instability. Diagnosing and restoring a healthy PowerShell environment often resolves the issue and allows scans to complete successfully.