<p>Hi,</p> <p>I am basically having the same situation as in the question <a href="http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/1d7e4f84-4a9b-46c6-a040-91fc8ea066ae">http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/1d7e4f84-4a9b-46c6-a040-91fc8ea066ae</a>, but on Server 2008 x86, not 2008 R2 (Unfortunately, 2008 R2 is not available as 32 bit, and one legacy app needs that).</p> <p>According to the virtual machine vendor (It is RedHat KVM), the recommended workaround is to set the USEPLATFORMCLOCK BCD option to avoid using the TSC timer, and then use W32Time or another NTP client to automatically adjust the clock speed.</p> <p>Unfortunately, when I try this on 2008 (NT 6.0.6002), I get the following error message:</p> <code>C:\Windows\system32>bcdedit /set {default} useplatformclock true The element data type specified is not recognized, or does not apply to the specified entry. Run "bcdedit /?" for command line assistance.</code> <p>So what is the proper way to make Server 2008 (not R2) not use the TSC counter as a time source?</p> <p>Is it the same command with some non-obvious change, or is it a completely different setting?</p> <p><b>P.S.</b></p> <p>As this is probably the same issue for Vista Desktop, I have posted almost the same question in the Vista consumer forum. Once I get an answer that works in either forum, I will copy it to the other one for the benefit of other users.</p>