just started noticing this error again once I upgraded to hijack v340 with 2.0 final software. Did this go away for anyone else?