A Host Integrity custom script fails to launch when using the %F% variable with 8.3 file names disabled.

book

Article ID: 170395

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

When using Host Integrity with the Utility: Run a script feature, the custom script is failing to run as expected. The rest of the Host Integrity checks run without issue, however.

Windows cannot find 'C:\Program'. Make sure you typed the name correctly, and then try again.

Cause

This behavior is expected if 8.3 file names have been disabled on the machine using "fsutil.exe behavior set disable8dot3 1" or via the registry.

Environment

Windows 7, 8, and 10

Resolution

In the settings for the custom requirement script, under the line Execute the command (use %F% to specify the script name):, instead of a plain %F% use double quotes as "%F%". This works around the limitation to cscript when 8.3 is disabled and spaces are introduced in the path (i.e. C:\Program Files\).

As example:

 

Attachments