We use a custom application that crashes unfortunately when there is any Windows environment variable whose value consists merely of blanks, no matter how many blanks.
After updating ESET endpoint from version 5 to 6, this application doesn't work anymore due to the "empty" system variable ESET_OPTIONS.
When we remove the variable, the custom application works, but after a reboot the "empty" variable reappears!!
Is there any way to prevent ESET from setting this variable to an empty string, at least as a workaround until we have a fix for the custom application?