A: This is a known bug with the Discover 11.1 patch.  Either upgrade to Discover 12.0 or contact us for updated files to get this utility running with Discover 11.1.