The solution seems temporary as the HP software (presumably) re-created the original telemetry directory and the monitor racing has resumed. I renamed the directory (again), and that seemed to fix the issue. The point here is that even if we rename the directory, it will eventually be recreated by HP. This occurred without a restart, which means it was likely either a live update or a timed re-spawning of the directory.
A more permanent fix would be creating a new empty telemetry directory and setting permissions preventing Windows or other apps from writing to it. If anyone knows how to do this, please post back.
Hi Michael,
I guess that 'creating a new empty telemetry directory and setting permissions preventing Windows or other apps from writing to it' will most likely not work. Windows Update has probably always enough rights to put files into such a directory. Guess we need to wait till some folks at HP acknowledge that it's their challenge to fix. In between we must keep changing directory names if we want to avoid to have the monitor changing to 'racing mode' again.
Furthermore, last night I developed the thought that it's not 100% certain the cause is wiith the HP Telemetry software. It might be that the Philips monitor responding to an illegal instructing (receiving from an external source such as the HP Telemetry software) 'reset itself to racing mode'. This based on the errormessage I've seen:
Error :VcpCodeDataHandler::GetValueFromVcp - Failed for the Command :20 in Normal format
Error :VcpCodeDataHandler::GetValueFromVcp - Failed for the Command :220 in Normal format
Error :VcpCodeDataHandler::GetValueFromVcp - Failed for the Command :229 in Normal format
Trust that HP and if needed Philips will find a solution soon!