Windows 10 home or pro

Ztruker · 30 Oct 2019

Bree said:

Look for C:\Windows\System32\gpedit.msc, the Group Policy editor is only installed in Pro.

The 'retrieve key from backup' option in ShowKeyPlus can also be used to find the key in an offline system.

Are you sure about gpedit.msc? I thought Pro and Home were identical, and the upgrade from home to pro was a simple key change?

Never thought about ShowKeyPlus, rats, should have. Thanks.

Try3 · 30 Oct 2019

Rich,

Yes. Home contains
C:\Windows\System32\gpedit.dll
but not
C:\Windows\System32\gpedit.msc

Denis

Ztruker · 30 Oct 2019

Ah, thus the error when you type gpedit,msc from a run box. Got it.

W10 Tweaker · 30 Oct 2019

1030 win10 Home.txt

Try3 said:

Rich,

Yes. Home contains
C:\Windows\System32\gpedit.dll
but not
C:\Windows\System32\gpedit.msc

Denis

OK, maybe I did cheat by Tweaking my Win10 Home a bit.

1030 win10 Home.txt

Windows 10 home or pro-1030-gpedit-file.jpg

Ztruker · 30 Oct 2019

W10 Tweaker said:

1030 win10 Home.txt

OK, maybe I did cheat by Tweaking my Win10 Home a bit.

Do you have a folder called C:\ProgramData\regid.1991-06.com.microsoft, and if yes, what it the file it contains?

Try3 · 30 Oct 2019

Rich,

I have Windows 10 Home. I have the folder C:\ProgramData\regid.1991-06.com.microsoft and it contains
regid.1991-06.com.microsoft_Windows-10-Home.swidtag

I think this is the most reliable method given that people are known to manually add C:\Windows\System32\gpedit.msc to the Home Edition.
Of course, somebody could also add/substitute the file
regid.1991-06.com.microsoft_Windows-10-Home.swidtag
or
regid.1991-06.com.microsoft_Windows-10-Pro.swidtag
but only if they were trying to kid themselves for no logical reason.

Denis

W10 Tweaker · 30 Oct 2019

Ztruker said:

Do you have a folder called C:\ProgramData\regid.1991-06.com.microsoft, and if yes, what it the file it contains?

Yes

Ztruker · 30 Oct 2019

Thanks Dennis, I think that's the easiest and as you say, most reliable way. Test for the file, pipe the output through find and you'll know with little effort.

I'm just about finished installing a Win 10 Home X64 Hyper-V VM to play with this but since you gave me the info I needed, it's no longer necessary.

Forget the batch file

use a Command Prompt command.

Code:

type  C:\ProgramData\regid.1991-06.com.microsoft\regid.1991-06.com.microsoft_Windows-10-*.swidtag  | find /i "<product_title>"

Replace C with the drive letter of the Windows 10 partition you want to query.

Farvatten · 30 Oct 2019

Farvatten said:

~~And it's nice to have that build reference right there in black and white too~~.

I was disappointed looking back to just last week that this file under:

C:\ProgramData\regid.1991-06.com.microsoft

Is NOT a reliable source for an up to date Product_Version ( Build Number ) after finding this in my October 24th MR image under build 418 and just before the 449 update:

Code:

    <product_title>Windows 10 Pro</product_title>
    <product_version>
        <name>10.0.18362.1</name>

Ztruker · 31 Oct 2019

That is strange. I wonder why it's wrong? How did you get to 418, WU or UUPDUMP or MCT?