Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Mac Pro 5,1 12 core and Boot Camp Win 10

iamnotme

iamnotme

macrumors regular
Original poster
Jan 24, 2015
160
202
SW Ontario, Canada
I just installed win 10 with bootcamp and everything went smoothly other than audio driver but for some reason windows only sees 1 cpu (6 cores)
It's 64 bit home edition. It does see all the ram which is 50-50 beside each cpu. Windows home edition should support all 12 cores I thought. Anyone knows anything?
 
Home editions usually only support 1 physical CPU, I'm pretty sure that the same is true for Windows 10?
 
This is just for anyone googling:

after speaking with Microsoft I can confirm the following:

Windows 10 Home (Maximum processor sockets used = 1)

Windows 10 Professional (Maximum processor sockets used = 2+)



So if anyone is using a workstation machine with a dual Xeon Board you will need windows 10 Professional to make best use of it. I have also confirmed these findings by upgrading to windows 10 Pro and now both of my processors are registering and being used.

Windows 10 Professional - Mac Pro Mid 2010 (12 core) working like a dream .... Now
Click to expand...

https://social.technet.microsoft.co...ised-in-task-manager?forum=win10itprohardware
 
Last edited:
prvt.donut said:
Your sauce was left on the kitchen table and has gone bad.
Click to expand...
Haha Thanks, couldn't properly add it so changed it now to just a direct link.

Edit: damn, this Microsoft Sharepoint link is difficult to direct too..., sorry no proper link to be added, the information is true however :)
 
prvt.donut said:
A swing and a miss.
Click to expand...
So which Windows home editions haven't been limited to one socket?

And if you are so sure I'm wrong why don't you just write what is wrong in your post instead of acting like an idiot?

You've contributed nothing but absolute garbage to this thread, why do you even respond if you don't have anything other than stupid one liners to say?
 
Last edited:
bogg said:
So which Windows home editions haven't been limited to one socket?

And if you are so sure I'm wrong why don't you just write what is wrong in your post instead of acting like an idiot?

You've contributed nothing but absolute garbage to this thread, why do you even respond if you don't have anything other than stupid one liners to say?
Click to expand...

Sigh.... Ok, I will explain.

Look above, the op (bokkow) understood. You see, the link that he provided was broken. He had put the link in text "source", showing that that was the source for his information.

I clicked his link, noticed that it was broken and then used a joke using the word sauce instead of source as "sauce" is a common "meme" on the Internet.

Bokkow, saw my post, realized the mistake, fixed the url link, and thanked me for letting him know.

But you also replied seeming to not understand what I was talking about and questioning the facts of Windows multi-cpu version support.

I then posted "a swing and a miss" in the hopes that you would look back at the thread and see bokkow's reply and see that I was talking about the bad link. But you didn't and so now I am having to explain this all.
 
Hmm. Rather annoyingly, there seems to be zero documentation from Microsoft about which Windows 10 editions support multiple physical CPUs.

I don't like to not provide references, but all I can find it this table that it posted into a similar question about Windows 8.

Here and here

I can find a page that mentions Windows 10 supporting multi CPUs, but it does not say that different versions support it.

So it seems that for the client versions, Windows 10 pro and enterprise are the only versions that support multiple CPUs.

Maybe the lack of documentation is because their server OSs require multiple licenses (1 license per physical processor in 2012 and now with 2016, it has changed to depend on the number of total physical cores the hardware has) in multi cpu/core machines and they don't want to publically announce that a single client license will support more than a server license.
 
prvt.donut said:
Sigh.... Ok, I will explain.

Look above, the op (bokkow) understood. You see, the link that he provided was broken. He had put the link in text "source", showing that that was the source for his information.

I clicked his link, noticed that it was broken and then used a joke using the word sauce instead of source as "sauce" is a common "meme" on the Internet.

Bokkow, saw my post, realized the mistake, fixed the url link, and thanked me for letting him know.

But you also replied seeming to not understand what I was talking about and questioning the facts of Windows multi-cpu version support.

I then posted "a swing and a miss" in the hopes that you would look back at the thread and see bokkow's reply and see that I was talking about the bad link. But you didn't and so now I am having to explain this all.
Click to expand...

I understood perfectly well what you were talking about with your "sauce turned...", as I stated "It doesn't matter". It doesn't matter if his link to the source was non-functional, the fact is no less true...

So the only one not understanding the other in that instance here is you not understanding me, not the other way around.
 
bogg said:
I understood perfectly well what you were talking about with your "sauce turned...", as I stated "It doesn't matter". It doesn't matter if his link to the source was non-functional, the fact is no less true...

So the only one not understanding the other in that instance here is you not understanding me, not the other way around.
Click to expand...

Sigh.... I never said your information was wrong. I said his link was bad (notice I referenced his source) I was not talking to you. Then you replied to that talking about all home editions not supporting multiple processors (which had nothing to do with what I was saying, as I had made the comment to Bokkor in the hopes that he would fix the link to the source of the useful information so that future visitors to the site will be able to get good referenced information). But you keep thinking I am insulting you and trying to defend the information provided.

That complete miss at understanding that I was talking about the broken URL is then why I wrote the joke "a swing and a miss".

Look back at the threads, see that Bokkor thanked me for letting him know the link was broken.

/end thread.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back