Scanner Failed


A scanner failed for a reason that PDQ Inventory didn't know how to handle.

Possible Causes

The cause will depend on the nature of the error. Check the error message included with the error.

Many times the cause is corruption in the .NET framework on the target computer, requiring a repair or reinstall.

Another possibility is that the target computer was either booting up or shutting down. You will also get this error if you attempt to scan a computer that is configuring Windows' updates or a service pack installation prior to restarting.



In this state (configuring updates)  the target can be seen on the network but the OS cannot be accessed or managed.

Recommended Fix

If repairing or reinstalling .NET on the target computer doesn't work then submit the error to Admin Arsenal support.  Our support staff can perform additional research in to the cause and fix for the error.

Was this article helpful?
1 out of 3 found this helpful
Have more questions? Submit a request


  • 0

    A common error code is -1073741819 which is usually caused by anti virus software preventing access to the scanner's files.

  • 0

    Done the reinstall of .net but I still get the error code 225, what files/locations require an exception to be created in the av software?

  • 0

    Hi Aaron,

    Have the following folder exempted:


    If you've been using PDQ Inventory since version 2.x then you may need to exempt the folder C:\Windows\PDQInventory-Scanner

  • 0

    I updated .Net to 4.5 as requested by Brandon Rewis and that sorted out the problem, AV software so far has not been an issue for me, I use Avira Profesional Security

  • 0

    "Many times the cause is corruption in the .NET framework on the target computer, requiring a repair or reinstall."  what version?  I don't see any note about .net in the deployment guide!

  • 0

    .NET 4 or higher is listed in the requirements for PDQ Inventory. The version you would need to repair is the most current 4.x version that is installed on the target. If you don't have the latest (at this writing it is 4.6.1) you could just upgrade and that would probably do the trick.

    You don't have to worry about repairing .NET 3.5 or lower when it comes to PDQ products as they do not utilize any .NET below 4.

Article is closed for comments.
Powered by Zendesk