We've just found that wPrime is indeed hanging on certain systems (confirmed on a fresh install of Windows Vista). It appears as though Vista would assign a different temporary directory to wPrime from CPUz (probably because wPrime was run as Admin). Consequently wPrime never found the CPUz output file and waited.