Number of Cores Incorrectly Detected - Server 2003/XP

KB ID: 1749
Product: Veeam Backup & Replication
Version: 6.x, 7
Published: 2013-04-17
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When adding a Server 2003 or Windows XP machine to Veeam, the true number of cores is not detected properly. Instead Veeam Backup & Replication only detects the number of Sockets.

Example:
A virtual machine with Server 2003, having a configuration of 2 Sockets and 4 Cores, is added to Veeam Backup & Replication. On the summary page the following is shown.

User-added image

Additionally the following can be found in the VeeamShell.log
Info     [This server] Determining cpu info.
Info     [This server] PhyCpu: 1, PhyCore: 2, LogCpu: 8.

Cause

The cause is the same for both Windows XP and Server 2003. Below is the text from the Microsoft KB article on this topic for Server 2003.

"This issue occurs because Windows Server 2003 does not have the functionality to detect hyperthreading processors and multicore processors. 

Note This functionality was introduced in Windows Vista by using the Win32_ComputerSystem class and the Win32_Processorclass in Windows Management Instrumentation (WMI)."

Solution

This issue can be tested by running the following command in PowerShell:

Get-WmiObject -class win32_processor -Property  numberofcores


If this command fails, then you will need to apply the hotfix below, and reboot:

Server 2003 - http://support.microsoft.com/kb/932370
Windows XP - http://support.microsoft.com/kb/936235

After reboot open the properties for the Windows machine again, and next through the pages to cause Veeam to re-query the number of cores.

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.