[DISCUSSION] Windows 10 Pro for Workstations SKU

Just a guess...but if we take cmd.exe & cmd.exe.mui from higher editions and replace the ones in Win10 Home/Pro b16299..will that enable creating a ReFS partition?
Or other changes also required?

 

keys not working. Do you have some new?

 

You need to login to view this posts content.

 

Only aesthetically.

NVDIMM-N support alone is huge, and PfW optimizes the synergy between the NVDIMM-N memory and M.2 NVMe SSDs quite well out-of-the-box. After making a few GPO changes, tweaking indexing and setting the virtual memory paging file to a static custom size the difference was even more substantial.

SMB Direct, with a RDMA-capable network adapter, provides a huge boost in throughput and substantially lowers CPU usage.

Full usage of the Intel Xeon E7 series (all Xeon/server grade processors).

Hyper-V is more polished, particularly its virtual switch setup. It also utilizes VT-d I/O (and I'm certain AMD's IOMMU) at a much more beneficial level.

I'm sure I'll notice more as I keep using it. Workstation is not synonymous with desktop PC.

 

I've read an article by Mary Jo Foley about ProWS, looks like the current release does not yet support Threadripper/Epyc CPUs.
But RS4 will add support for those. Nice.

This new edition will only get better and better as new feature updates are released.
Looks like v1803/RS4 will be a huge update.

 

Can't comment on either of those. I'm running a few Xeon E7-8890s and was finally able to get Intel's Uncore Monitoring and Counter applications to work properly. It's showing interaction between all cores on all CPUs so suffice it to say, PfW is utilizing them. I have not optimized the CPUs whatsoever nor intend to at this time. But right now it's a super-solid setup OS with 16 GB NVDIMM-N memory, 2 M.2 NVMe SSDs, quad Xeon E7-8890s, dual 2-port (4 total ports) Gigabit LAN cards with one card dedicated exclusively to a Hyper-V 64-bit guest system with secure VT-d access, and I tossed in 2 spare regular WD Red NASWare HDDs that I decided to use solely for Storage Spaces setup with RTFS. If I decide to actually use this setup, I'll be swapping out the WD Red NASWare's for SAS SSDs. the WD NASWare drives are some of the most solid HDDs you can get but I just can't handle the slow-ass speeds of those kinds of drives anymore.

Overall PfW has not hit any real snags with this hardware and it's pretty neat to have a substantive Windows OS similar to Professional or Enterprise in aesthetics and features but able to utilize such hardware.

 

del​

 

Surely not many users will have that kind of setup, to notice Workstation be any different than Pro

 

One hardly needs high-end hardware to notice a difference. Simply logging multiple CPU cores' throughput, heat and overall rates of high processing while playing a fairly intensive game or multitasking will show a difference.

Simply setting up a VM using Hyper-V with a dual-NIC card (that tons of regular motherboards have now) will show a difference.

Using any sort of VPN/interweb/domain network paths will show a difference.

PfW and Professional are synonymous with each other outside of aesthetics.

 

so are you saying pro ws would handle multiple cores more efficiently then other 10 versions?

 

I previously activated WPS on a different drive with a digital license linked to my MS account. So with the new 17017 build I decided to go for the gusto, and use WPS as my main drive. Everything is good, and I signed into my MS account during installation. WPS activated with digital license linked to m y MS account, and account verified! Joy of joys, and wonder of wonders! Life is so good!

 

Is itp ossible convert Windows Pro to Windows Pro Workstations?

 

By entering the key for Pro WS the edition will change.

 

hmm, from what I understand this still does not give you a "complete" and "real" pro ws experience, does it? will it recognize and accept more than 2 CPU sockets?

 

If you check back this thread you'll find that it does not. For complete experience convert Core Index to ProWork.

 

thanks just confirming, cause I think some people think it does

 

I think it must be a bug. If it doesn't convert from Pro to ProWS fully then why even allow the upgrade/conversion in first place?
These days Microsoft crowd-sources all the beta testing. Dona might be the lone lady sitting in office hitting keyboard frantically to fix last minute bugs. Think how many testers/coders might have lost jobs at Microsoft due to insiders/telemetry/neural network mumbo jumbo. I may be sounding like Rick & Morty lol.

PS: Only one person said that he/she/it was not able to get 4 CPUs to work. We need more data.

 

Not sure what MS intended with that licensing switch, but it creates quite a mess in the registry. That caused a lot of trouble for all KMS tools to gather the Edition correctly (@abbodi1406 still calls it dirty hack). The conversion doesn't create any problems, so there must be differences.

EDIT: In my tests the license switched version didn't accept more than two CPU sockets likewise.

 

Did any try to change license/key prior installation and see if CPUs are 4?
i.e. with dism

 

If you are going to mount Pro to change license, you may as well mount Core, and get correct PWS.