Here’s a thought: When GW determines a file or path does not exist (and so reports that OFL is not possible for the displayed path and file), is it checking the actual path location and filename for existence? Or is it instead checking a cache whose path and name information might no longer be valid, such as in the midst of an application update? Does GW also care about changed file version numbers when it decides OFL is not available? It seems that just before I noticed this OFL problem, Windows updated the file in question (compattelrunner.exe). See attached image of the Alert when the update happened. Could GW be checking for the file’s old version number or location, instead of the current one?
1 Like