fixed in 4.2.5!
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
i've searched this bug today and it supposed to be fixed in 4.2.2. But... i'm running 4.2.4 Build 610 on Windows 7 64 Bit and the same error still appears.