Given the problem was solved by a virus definition update from that last thread and the new virus update have brought back the problem, while possible it is unlikely a windows bug.