Post your actual Windows 10 Build.

[Alexander1970]

You can post your actual Windows 10 Build (a Picture would be very nice).
Of course,you can also update here,when you have updated Windows 10.
Thank you for your Contributions.
(Please avoid to also Post your Product ID and/or Device ID).

#################################################################

 

[Deleted User]

not sure what the use of this thread would be aside for making fun of people who purposely stay massively outdated, either way i'm stuck on 1909 because of "potential incompatabilities"

 

[Alexander1970]

not sure what the use of this thread would be aside for making fun of people who purposely stay massively outdated, either way i'm stuck on 1909 because of "potential incompatabilities"

Why is this so hard,to only post a Picture in the Computer Section ?
Without any ulterior motives or to denounce other PC users.....
Is it an "IT Crime" when Users are on Version 1709 ? *sigh*

 

[Magnus87]

 

[Deleted User]

Why is this so hard,to only post a Picture in the Computer Section ?
Without any ulterior motives or to denounce other PC users.....
Is it an "IT Crime" when Users are on Version 1709 ? *sigh*

in this day and age, yes it is a crime to stay outdated and insecure, lacking critical updates lol
especially when you put it into the context of IT

here, since you complained about lacking a picture, despite not making it clear that one was apparently required

 

[nryn99]

first post since forever. pc doesn't give me the 2004 version but i'm okay with it.

 

[Alexander1970]

in this day and age, yes it is a crime to stay outdated and insecure, lacking critical updates lol
especially when you put it into the context of IT

here, since you complained about lacking a picture, despite not making it clear that one was apparently required

Thank you.

 

[Tom Bombadildo]

CBA to take a screenshot, but I manually updated all my Windows 10 PCs to 2004 this weekend, mostly because a couple of the features they added are actually useful to me this time and partly because I was bored.

Limiting bandwidth Windows Update uses is something I've wanted for ages (without needing third party software), and being able to see GPU temp in task manager is nice when I'm testing games and such on my laptop since it's just a quick shortcut away from launching.

 

[Minox]

CBA to take a screenshot, but I manually updated all my Windows 10 PCs to 2004 this weekend, mostly because a couple of the features they added are actually useful to me this time and partly because I was bored.

Limiting bandwidth Windows Update uses is something I've wanted for ages (without needing third party software), and being able to see GPU temp in task manager is nice when I'm testing games and such on my laptop since it's just a quick shortcut away from launching.

Monster, you're risking everyone's computer by being 16 years out of date :V

 

[Alexander1970]

 

[Hayato213]

Sitting on Version 1909 and OS build 18363.959 right now.

 

[RandomUser]

in this day and age, yes it is a crime to stay outdated and insecure, lacking critical updates lol
especially when you put it into the context of IT

here, since you complained about lacking a picture, despite not making it clear that one was apparently required

Actually do not feel bad about staying on an older build of Windows 10 OS. Believe it or not anyone whom uses Xeon computers knows that Windows Server version uses an even older build of Windows 10, for example Windows Server 2019 is like Windows 10 build 1809. They even use the same Updates as Windows 10 1809. So if anything it isn't too much of a fuss because Windows Server users are relegated to an older build of Windows 10.

 

[Deleted User]

Actually do not feel bad about staying on an older build of Windows 10 OS. Believe it or not anyone whom uses Xeon computers knows that Windows Server version uses an even older build of Windows 10, for example Windows Server 2019 is like Windows 10 build 1809. They even use the same Updates as Windows 10 1809. So if anything it isn't too much of a fuss because Windows Server users are relegated to an older build of Windows 10.

but that's windows server, not windows 10, it's technically an entirely seperate OS on microsoft's terms

 

[Tom Bombadildo]

Actually do not feel bad about staying on an older build of Windows 10 OS. Believe it or not anyone whom uses Xeon computers knows that Windows Server version uses an even older build of Windows 10, for example Windows Server 2019 is like Windows 10 build 1809. They even use the same Updates as Windows 10 1809. So if anything it isn't too much of a fuss because Windows Server users are relegated to an older build of Windows 10.

Well..."sort of".

There's the LTSC Windows Server 2019 which is stuck on 1809, and then the Semi Annual Channel version of Windows Server which gets stays up to date with the normal Windows 10 (2004 was released in May, same time as consumer 2004). They're technically two different things, though, as the SAC doesn't come with a GUI (IIRC) and is more focused on Hyper-V stuff and containers (so mostly like "cloud computing" applications, whereas Windows Server 2019 is for the usual Windows Server stuff, file servers, SQL stuff, AD, etc etc.

But really, if you're using Windows Server 2019, you don't really need any of the fancy new stuff that consumer Windows 10 gets with it's major updates (and if you think you do, you'd probably be just fine with a standard Windows 10 install and adding server things separately yourself), and I assume the whole point of leaving it on one version to make LTS updates easier than having to support multiple different version.

 

[rehevkor]

.....why?

 

[RandomUser]

but that's windows server, not windows 10, it's technically an entirely seperate OS on microsoft's terms

Technically yes, but reality says otherwise. They use the same updates as Windows 10 updates do. Updating Windows Server actually downloads Windows 10 msu updates and they are usable in both Windows 10 and Server.

Well..."sort of".

There's the LTSC Windows Server 2019 which is stuck on 1809, and then the Semi Annual Channel version of Windows Server which gets stays up to date with the normal Windows 10 (2004 was released in May, same time as consumer 2004). They're technically two different things, though, as the SAC doesn't come with a GUI (IIRC) and is more focused on Hyper-V stuff and containers (so mostly like "cloud computing" applications, whereas Windows Server 2019 is for the usual Windows Server stuff, file servers, SQL stuff, AD, etc etc.

But really, if you're using Windows Server 2019, you don't really need any of the fancy new stuff that consumer Windows 10 gets with it's major updates (and if you think you do, you'd probably be just fine with a standard Windows 10 install and adding server things separately yourself), and I assume the whole point of leaving it on one version to make LTS updates easier than having to support multiple different version.

Thank you for bringing me up to speed about the 2004 version of Server, I did not know they have Semi Annual Channel version. Like you said no GUI, and most likely no desktop experience. Another reason for using Windows Server is for support more then 2 physical processors, so Windows Server is necessary. There is a trick that can be done to force Windows Server to act like Windows 10 and it isn't documented on the Convert Server to Workstation website. This trick only last for one Windows session, however can repeat the trick unlimited amount of times. You can install software that would refuse to install in Windows Server with the trick and after Windows revert back, the software runs fine in Windows Server. Also using this trick allows task manager to act like Windows 10 task manager, thus functioning the same way as the Windows 10 counterpart. So technically no it isn't the same, but reality says otherwise.

 

[Tom Bombadildo]

Another reason for using Windows Server is for support more then 2 physical processors, so Windows Server is necessary.

Except that's wrong, Windows 10 Pro supports 2 CPUs just fine (which I can confirm, since I've installed a stock Windows 10 Pro build on my 2x Xeon x5680 server, before I setup Proxmox for VMs anyways), and Windows 10 Pro Workstation supports up to 4 CPUs at once (and up to 6TB of RAM, cuz why not? ) https://www.microsoft.com/en-us/windowsforbusiness/workstations <

 

[RandomUser]

Except that's wrong, Windows 10 Pro supports 2 CPUs just fine (which I can confirm, since I've installed a stock Windows 10 Pro build on my 2x Xeon x5680 server, before I setup Proxmox for VMs anyways), and Windows 10 Pro Workstation supports up to 4 CPUs at once (and up to 6TB of RAM, cuz why not? ) https://www.microsoft.com/en-us/windowsforbusiness/workstations <

I believe I stated more then 2 physical processor not just 2. When did Windows 10 Pro Workstation released? I want to give this a try, seems interesting. Windows 10 Pro still supports no more then 2 physical Processor though, but the workstation one seem to support 4. I wonder if my activation token with Windows 10 pro is usable for the workstation version?

 

[Tom Bombadildo]

I believe I stated more then 2 physical processor not just 2. When did Windows 10 Pro Workstation released? I want to give this a try, seems interesting. Windows 10 Pro still supports no more then 2 physical Processor though, but the workstation one seem to support 4. I wonder if my activation token with Windows 10 pro is usable for the workstation version?

Since 2016 or so IIRC, it's definitely not some new thing.

Whether your other activation will work or not I doubt it since it's a difference version, but eh just use hwidgen

 

[RandomUser]

Since 2016 or so IIRC, it's definitely not some new thing.

Whether your other activation will work or not I doubt it since it's a difference version, but eh just use hwidgen

That explains how I missed that, I skipped over the whole 2016 version of all OS revisions and most likely up to 2018. That is a great find and surprise it requires a serial key to get access to this edition of Windows instead of being able to select it from the list of install. I tried to increase the physical processor count setting in VMWare just to see if the new edition sees it, and sure enough, it does.
Thank you for bringing this edition to my attention.

For everyone, check it out in VMWare.