[DISCUSSION] Windows 10 Pro for Workstations SKU

Discussion in 'Windows 10' started by Micro, Aug 11, 2017.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    Just one is confusing...
     
  2. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    I am currently here right now. Untitled.png
     
  3. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    So, last time I downloaded 16299 using the Microsoft USB tool. I did an upgrade. This may be what messed things up.
    According to what I am reading here do I need to download 16299 and change the wim file again?
     
  4. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    because he does not have the full 16299 WS installed on his machine, he has only 16299.248 license switch so it's not the full WS with the real features. So now he has to install the full 16278 WS , then he has to activate it then upgrade to 16299 to get digital license with the full 16299 WS, don't you agree ?
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    He doesn't have to install anything less than the edition and build he want's (16299 real pro-ws), the screens he posted clearly showed he already has a HWID for Pro-ws, he even linked it to his MSA on previous installs.

    it won't officially take updates but if that's what he wants, he gets it.
     
  6. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    OK, As you can see 16278 is installed, It is currently activated and appears to be the full WS build.
    So from here if I download 16299 using the Microsoft USB tool and do an upgrade from where I currently am does that work or do I need to do something different to make sure I have the Full WS build.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    You need to create a 16299 pro-ws iso, install that, there was no need to install 16278 again....

    To see this:
    Code:
     Basic OEM Information For This Computer
     =======================================
    OS Version {SKU}         - Windows 10 Pro for Workstations {161} - x64
    OS Edition {Registry}    - ProfessionalWorkstation
    OS Edition {CBS}         - ProfessionalWorkstation
    OS Build/Update Revision - 16299 {rs3_release} / 15 {Baseline Release}
    Or this:
    Code:
    C:\Windows\system32>dism /online /get-currentedition
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Image Version: 10.0.16299.15
    
    Current edition is:
    
    Current Edition : ProfessionalWorkstation
    
    The operation completed successfully.
    
    C:\Windows\system32>
     
  8. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    So I need to do the whole UUP download of 16299, convert the install.wim again and rebuild the iso with the new wim and then just do an upgrade.
     
  9. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    ok i forgot he had already digital license for 16299 WS but i don't think you saw that he had downloaded 16278 one hour ago so you had to tell him to download 16299 home then converted to WS using WES one hour ago. :p
     
  10. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    Yes Exactly :p
     
  11. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    Downloading Home only UUP of 16299 right now. Will report back once I am done.
    That was my original mistake as I didn't convert 16299 to PFWS
     
  12. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    when i think about that, i don't think that downloading home 16299 then convert it to 16299 WS one hour ago would change anything because remember that he hadn't the Full 16299 WS, it was only a switch license from Pro to WS so i don't think that the digital license was the one that was associated to WS, i think the digital license was associated to Pro version but i am not sure, we would have known that if he had installed the 16299 WS.
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    The HWID is for Pro-WS, no matter how it was generated.

    He seems to use an online windows account, so normally when he now signs in with his MSA it should be HWID activated.
     
  14. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    are you really sure about that ?
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    Yes, but i never use online windows accounts myself.
     
  16. sultan.of.swing

    sultan.of.swing MDL Junior Member

    Feb 11, 2018
    72
    9
    0
    I think it was using my Professional License as I own a copy of that and since the OS was "Professional" that is what I feel it was using.
     
  17. mehdibleu

    mehdibleu MDL Expert

    Jun 14, 2017
    1,008
    251
    60
    ok i trust you.
     
  18. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,545
    450
    Code:
    MRP - OEM Query Tool v49.1 Enhanced  --  02/24/2018 {UTC} -- 10:31pm
     
    -------------------------------------------
    - Basic OEM Information For This Computer -
    -------------------------------------------
    OS Version {SKU}          - Windows 10 Pro for Workstations {161}
    OS Edition {Registry}     - ProfessionalWorkstation
    OS Edition {CBS}          - ProfessionalWorkstation
    OS Architecture           - 64 Bit
    OS Build/Update Revision  - 16299 {rs3_release} / 15 {Baseline Release}
    OS Language Name/Code     - en-US / Dec:1033 {Hex:409}
    OS Locale                 - en-US
    OS Language Value         - ENU
    OS Installation Date      - 2/24/2018 10:20:37 PM {Localized Date Format}
    CPU Name                  - Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz   
    CPU Description           - Intel64 Family 6 Model 58 Stepping 9
    CPU Architecture          - 32/64 Bit Instruction Set
    CPU Cores/Threads         - [2] / [2]
    Boot Drive Information    - BusType: SAS, Mode: AHCI, Partition: MBR, DriveType: HDD
    Boot Drive Model Name     - VMware Virtual S
    Bios Information          - Type: Phoenix Technologies LTD , Version: 6.00 , Date: 07/02/2012
    Total Physical Memory     - 4095 Mb
    Available Memory          - 2545 Mb
    GPU Primary Adaptor Name  - VMware SVGA 3D
    GPU Primary Adaptor Info  - Resolution: 1024x768 , Driver Date: 02/03/2017 , Driver Vers: 8.15.1.60
     
    --------------------
    - Scanned DMI/BIOS -
    --------------------
    #01 CSProduct Name        - VMware Virtual Platform         #09 SLIC Information - 2.2                                     
    #02 CSModel Name          - VMware Virtual Platform         #10 Product Key      - Not Shown On Saved Report     
    #03 CSBaseboard Prod      - 440BX Desktop Reference Platfo  #11 MSDM Key         - Not Shown On Saved Report     
    #04 CSProduct Vendor      - VMware, Inc.                    #11 MSDM Edition     - Win 8 Professional                       
    #05 CSManufacturer        - VMware, Inc.                    #11 MSDM Brand Name  - Dell                           
    #06 Baseboard MFR         - Intel Corporation               #12 BIOS/Boot Mode   - Legacy/MBR                     
    #07 Serial/Service Tag    - Not Shown On Saved Report       #13 Certificate      - Not Present                   
    #08 BIOS or SLIC ID       - DELL   - 6040000                #14 License Status   - Licensed {Retail}                       
     
    -----------
    - Summary -
    -----------
    OEM Theme/Branding        - Dell [id: #08]   
    OEM Activation Vista/7    - Dell [id: #08]
    Valid OEM Consumer OS     - Vista/Win7/Win8.x/Win10
    Valid OEM Server OS       - Server 2008/Server 2008R2/Server 2012
    MSDM Check Method Used    - {M1}
    Detected .Net Versions    - v1.1.4322 / v2.0.50727 / v4.0.30319 / v4.7.02556
    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.
     
    ** End of Query Tool report. **
    
     
  19. UndertakerBen

    UndertakerBen MDL Member

    Mar 3, 2016
    150
    520
    10
    #1380 UndertakerBen, Feb 24, 2018
    Last edited: Feb 24, 2018
    Code:
    MRP - OEM Query Tool v48.0 Enhanced  --  02/22/2018 {UTC} -- 1:01pm
     
    -------------------------------------------
    - Basic OEM Information For This Computer -
    -------------------------------------------
     OS Version {WMIC}         - Microsoft Windows 10 Pro for Workstations x64
     OS Edition {Registry}     - ProfessionalWorkstation
     OS Edition {CBS}          - ProfessionalWorkstation
     OS Build Number           - 16299
     OS Update Build Revision  - 248
     OS Language Name/Code     - de-DE / Dec:1031 {Hex:407}
     OS Locale                 - de-DE
     OS Language Value         - DEU
     OS Installation Date      - 21.02.2018 19:58:46 {Localized Date Format}
     CPU Name                  - AMD Phenom{tm} II X6 1055T Processor
     CPU Description           - AMD64 Family 16 Model 10 Stepping 0
     CPU Architecture          - 32/64 Bit Instruction Set
     CPU Cores/Threads         - [6] / [6]
     Boot Drive Information    - [BusType: RAID, Mode: AHCI, Partition: MBR, DriveType: HDD]
     Boot Drive Model Name     - [3+0 Stripe/RAID0]
     Bios Information          - [Type: Award Software International, Inc. , Version: FGi , Date: 06/05/2012]
     Total Physical Memory     - [8182 Mb]
     Available Memory          - [6355 Mb]
     GPU Primary Adaptor Name  - [NVIDIA GeForce GTX 460]
     GPU Primary Adaptor Info  - [Resolution: 1280x768 , Driver Date: 01/23/2018 , Driver Vers: 23.21.13.9077]
     
    --------------------
    - Scanned DMI/BIOS -
    --------------------
     #01 CSProduct Name        - GA-890GPA-UD3H                  #09 SLIC Information - No SLIC Table Detected                
     #02 CSModel Name          - GA-890GPA-UD3H                  #10 Product Key      - Not Shown On Saved Report  
     #03 CSBaseboard Prod      - GA-890GPA-UD3H                  #11 MSDM Key         - Invalid MSDM Table Detected
     #04 CSProduct Vendor      - Gigabyte Technology Co., Ltd.   #11 MSDM Edition     - Undefined                            
     #05 CSManufacturer        - Gigabyte Technology Co., Ltd.   #11 MSDM Brand Name  - Undefined                  
     #06 Baseboard MFR         - Gigabyte Technology Co., Ltd.   #12 BIOS/Boot Mode   - Legacy/MBR                  
     #07 Serial/Service Tag    - Undefined                       #13 Certificate      - Not Present                
     #08 BIOS or SLIC ID       - GBT    - 42302e31               #14 License Status   - Licensed {Retail}                    
     
    -----------
    - Summary -
    -----------
     OEM Theme/Branding        - Gigabyte [id: #04]
     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.02556
     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.
     
     ** End of Query Tool report. **