Four solutions to four computing problems

Topic

New Reply

LANGALIST By Fred Langa AskWoody subscribers are an eclectic bunch, as evidenced by this quartet of interesting — and exceptionally wide-ranging
[See the full post at: Four solutions to four computing problems]

2 users thanked author for this post.

lmacri, abbodi86

Reply | Quote

Replies

Hi, I tried the solution Tracey mentions for obtaining the Windows 10 product key for an OEM system, which mine is.  I got this response:

Microsoft Windows [Version 10.0.18363.1139]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>wmic path softwarelicensingservice get OA3xOriginalProductKey
OA3xOriginalProductKey

C:\WINDOWS\system32>

Which is not quite the desired response…  Suggestions?

Reply | Quote

The free Belarc Advisor app will give you the Windows and software keys on your PC and much much more.

1 user thanked author for this post.

SueW

Reply | Quote

That seems to indicate the key is empty as it works on the machine I tested.

cheers, Paul

Reply | Quote

Works on my 1909 pro

Reply | Quote

Seems this command is only good for an OEM install of Windows 10. It does nothing for me either.

This command (at an admin CMD prompt) however – does a lot more:

slmgr /dlv

Cheers

Sonic

 

 

1 user thanked author for this post.

Steve S.

Reply | Quote

dvhirst865 wrote:

Microsoft Windows [Version 10.0.18363.1139] (c) 2019 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>wmic path softwarelicensingservice get OA3xOriginalProductKey

OA3xOriginalProductKey

C:\WINDOWS\system32>

I got the same as you on a Non-OEM, home built machine. W10 Pro 1909 18363.1082.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I have an OEM desktop computer that came preinstalled with Win 10 Pro.  Knowing the product key was attached to my specific hardware, I purchased a Win 10 Pro retail license from PC World magazine so I would be able to migrate the license to new hardware – if/when it became necessary.  The special low price was worth some peace of mind I figured.

Wanting to confirm that the key was actually accepted, I used the command prompt method suggested. It returned my old key rather than the new one.

Digging further I turned off Windows Security real-time protection and ran Nirsoft’s produkey.exe directly from within the downloaded zip file. It ran perfectly and revealed two keys.  A “Windows (BIOS OEM Key)” which was the same one that the command window method showed and a “Windows 10 Pro” key which turns out to be the retail key I had purchased and “upgraded” to.

So, I’m good to go after turning real-time protection back on.

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Just to be clear for current measurement one would need to split the power cord into line and neutral wires or use a AC Line Splitter.

see
https://www.amazon.com/Extech-480172-AC-Line-Splitter/dp/B0000YHN9W
https://www.instructables.com/CLAMP-THOSE-AMPS/

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

The command to get the product key had an interesting result. This box had Windows 10 Home on it and I (legally) upgraded it to Windows 10 Pro. (Aside, a non-profit can legally do this as an upgrade instead of a new install.) Anyway, the wmic command return the product key for the original Home version. Belarc found both keys, though the Prod key was in the “(Key: ends with XXXXX)” form.

Reply | Quote