Pre-Req Check Failed (Scan failed, failed to start scan (0x1374900)

Issue

When attempting to patch there are a large about of detections of vulnerabilities that are not applicable to the client machine. When scanning, these definitions are flagged as detected for reason "Pre-req Check failed." This can cause numerous failures, bloated detected definition results, and incorrect logging.

Symptoms

To know whether or not you are getting a Pre-req check failure there are a few symptoms you can look for in order to know if this is the cause of your patch failures. This issue only occurs with Next Gen vulnerabilities.

1. Scan Failed returns

One of the first symptoms most customers notice is an abundance of "Scan Failed, Failed to start scan (0x1374900)" returns in their clients patching history. These returns are an indication that the core server received a failure to start the scan during Vulcan. This is due to important files not being in the proper location during the scan, more on that later.

2. Bloated "All Detected" patches list

The second symptom that can point to a Pre-req check failed is the bloated "All Detected" folder in the Patch and Security. This is normally filled with a large amount of detection of either previously undetected or not applicable vulnerabilities. Since there was a failure during the scan for these vulnerabilities they will be flagged as detected and will show up in this folder. When selecting one of your definitions you will see the reason for detection as "Pre-Req Check Failed."

3. Ivanti folders on the root of C:\

The final Symptom of this issue is the presence of two Ivanti folders that are being placed in the root of C:\.  "vulScan" and "LANDesk" will appear in the root of C:\ instead of the locations "ProgramData" and "Program Files(x86)" respectively. This is caused by them not being properly configured to the proper locations.

Resolution

This issue can be easily resolved by correcting the registry key where the vulScan folder should be properly located. Open Regedit and locate the following key

x64 Devices

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\Shell Folders

x32 Devices

HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

Here you will find the "Common AppData" key. If you are experiencing this issue it is caused by this key being blank. Simply add "C:\ProgramData" without the quotes then run a scan. This should allow for a proper scan and the vulScan and LANDesk folders will properly update in their designated locations. You are free to delete the folders on the C:\ root without any impact on the product.