Not necessarily. I clean installed 16281 Pro-WS on VM and activated with normal key for that time. Then linked to my MS account and upgraded direct to 17101. I also have the "Possible Edition switch detected" and "OS Edition {CBS} - Professional" lines. Pro was never installed so perhaps the upgrade drags Pro-WS back into Pro where it belongs. Certainly I didn't do a license switch but perhaps the upgrade does Pro-WS > Pro > Pro-WS.
When on 16299.xxx the real pro-ws is installed it won't say "possible edition switch detected". On 16299.xxx Pro-ws is not actually supported and the license switch never will result in a 100% pro-ws. On IP rs4 release the licenseswitch is fixed.
I'm just saying I went from clean install of Pro-WS 16281 (with DE) direct to Pro-WS IP 17107 (never went to 16266.xxx) and it does say "possible edition switch detected". I don't think it is a problem (apart from with that line in the tools report) as from your posts I understand this is correct behavior. Spoiler Code: MRP - OEM Query Tool v49.1 Enhanced -- 02/25/2018 {UTC} -- 12:51am ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {SKU} - Windows 10 Pro for Workstations {161} OS Edition {Registry} - ProfessionalWorkstation {161} OS Edition {CBS} - Professional OS Architecture - 64 Bit OS Build/Update Revision - 17107 {rs4_release} / 1000 OS Language Name/Code - en-US / Dec:1033 {Hex:409} OS Locale - en-US OS Language Value - ENU OS Installation Date - 2/24/2018 6:04:28 PM {Localized Date Format} CPU Name - Intel{R} Core{TM} i5 CPU M 520 @ 2.40GHz CPU Description - Intel64 Family 6 Model 37 Stepping 5 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [2] / [2] Boot Drive Information - BusType: SAS, Mode: AHCI, Partition: GPT, Secure Boot:Enabled, DriveType: HDD, FS: NTFS Boot Drive Model Name - Virtual Disk Bios Information - Type: Microsoft Corporation , Version: Hyper-V UEFI Release v2.5 , Date: 08/22/2017 Total Physical Memory - 2681 Mb Available Memory - 685 Mb GPU Primary Adaptor Name - Microsoft Hyper-V Video GPU Primary Adaptor Info - Resolution: 1024x768 , Driver Date: 06/21/2006 , Driver Vers: 10.0.17107.1000 -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - Virtual Machine #09 SLIC Information - No SLIC Table Detected #02 CSModel Name - Virtual Machine #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - Virtual Machine #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - Microsoft Corporation #11 MSDM Edition - Undefined #05 CSManufacturer - Microsoft Corporation #11 MSDM Brand Name - Undefined #06 Baseboard MFR - Microsoft Corporation #12 BIOS/Boot Mode - UEFI/GPT #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - Not Present #08 BIOS or SLIC ID - VRTUAL - 1 #14 License Status - Licensed {Retail} ----------- - Summary - ----------- OEM Theme/Branding - EMachines [id: #01] OEM Activation Vista/7 - Un-Listed Valid OEM Consumer OS - Un-Listed Detected .Net Versions - v1.1.4322 / v2.0.50727 / v4.0.30319 / v4.7.03053 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 License Status Reason - 0x4004F401: This computer has a valid Digital/Store License. Other Notes: - SLIC ID or Version may not show correctly with UEFI or Secure Boot enabled. - Possible Edition switch detected. ** End of Query Tool report. **
That's strange indeed, are you absolutely sure that Pro edition wasn't installed on your machine on the first clean install ? To make sure whether Pro or WS is installed on your machine, do these 2 easy steps: go to command prompt then type : cmd (in admin mode) then you type this command line : dism /online /get-currentedition Logically, if you see "windows 10 pro WS" to appear, that means that you have the "real" WS, if you see Professional edition to appear, that means it's pro that is installed.
Exactly! I don't and never did have Pro installed - that is the question/issue. I clean installed on a VM 16281 Pro-WS (converted from home as normally described in this thread), activated it, linked to my MS account and joined insider program. I then upgraded (using Windows Update) direct to 17107 (the current IP version) and am still on Pro-WS. Interestingly the ISO I made from the downloaded UPP was for Pro but I didn't use it - just reboot/upgrade. Perhaps this is the cause? The VM has never had 10 Pro installed - I installed 8.1 Pro earlier so I could upgrade and get the DE but deleted the disk before doing the Pro-WS install. As I never switched to Pro (and Pro has never been installed on this VM) my guess is the upgrade switches to Pro and back (or perhaps just updates the reg key). My understanding from other posts here is that in RS4 Pro and Pro-WS are the same with just features enabled or not depending on license. In any case relying on QT to say someone has done a edition switch isn't necessarily correct (although it does say "Possible Edition switch detected". I don't want to make too much of a issue about it (or any issue at all really) - it was just an observation/curiosity.
i edited my previous post. run the command line i mentionned in my previous and tell me which edition appears in "current edition"
I get "ProfessionalWorkstation" for the command in "Current Edition": Spoiler Code: Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> cmd Microsoft Windows [Version 10.0.17107.1000] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>dism /online /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.17107.1000 Image Version: 10.0.17107.1000 Current edition is: Current Edition : ProfessionalWorkstation The operation completed successfully. C:\WINDOWS\system32> Edit - notice that "Current edition is:" is blank. Interesting? Code: Current edition is: Current Edition : ProfessionalWorkstation
So that means that you have the FULL Pro WS that is installed on your machine. i always use this command line to verify the current installed edition. It also means that there is something wrong with the quey tool which was probably not configured well, did you use the last version of the query tool ? if so, @mxman2k has to be informed about this.
17107 is Home/Pro only (all others are virtual editions), it will always show CBS professional, as said, they fixed the license switches on rs4 releases, the QT on 16299.xxx shows the three entries about the edition, on 16299.xxx it shows pro-ws for all three, on rs4 releases it always shows professsional at the cbs query.
The Query Tool examines several areas to determine what is the 'BASE' edition then what it has been possibly switched to. Because the base edition is Professional and the registry/sku says Pro-WS it flags up the license switch, simple but effective. If the Edition REG and Edition CBS match then it is not a switch. It is 98.9% correct (unless someone messes about with the registry to fool the OS it isn't what it is!). Before you ask, that includes altering the CBS registry entry to be Professional so that WS can obtain updates.
ok but how do you know that the base edition is Professional ? are you saying that because Pro WS has been released from Pro edition ?
CBS shows what is the base edtion! The underlying edition is Pro in this case. It can be derived from Core/Home but it is pro with the extra features, hence the name PROFESSIONAL Workstation I have yet to see a Core/Home Workstation edition (there again m$ creates so many versions it is a nitemare working out what is what!)
So it means that in his case @halasz , the registry has been probably modified by applying the trick that consists in making the updates work on Pro WS, that is why Edition REG and Edition CBS didn't match in his case. Correct ?
I don't know. I can only go on what the QT results indicated. If the 'trick' was applied then i cannot detect that without more code in the QT which is pointless, as m$ hopefully will allow WU updates without messing about with registry etc for Workstation when RS4 is released.
It really doesn't matter as it worked once to make it but so far I haven't been able to replicate it even following the same exact procedure. I do have the ISO which activates digitally upon install. I am afraid I can't make another one. Something happened during generalization which saved the activation, but it can't be replicated. Sorry.