Product Key Tool: Unable to open MSDM table!

Obviously in your case (& mine actually as my system is an older one) other key finder tools are what is needed. But either way, Microsoft remembers it for you.
 
Your licence key is hashed somewhere in the OS. There are many tools available which will find it.
Our tool is looking solely at the key (if it exists) which is embedded in the hardware by the OEM.
 
Terry60 said:
Your licence key is hashed somewhere in the OS. There are many tools available which will find it.
Our tool is looking solely at the key (if it exists) which is embedded in the hardware by the OEM.
Click to expand...

OK you are saying my license key is hashed somewhere in the OS, the other person that is also working for Neosmart says it is installed on a cloud, so who is correct I guess it really does not matter to much if you read the earlier post because I used a different product key finder and now I have it. But thanks for your reply I appreciate it.
 
None of us work with Neosmart, we are simply volunteers. We are saying that the Neosmart tool is only for use on machines that have the key embedded in the chip (not the Cloud or buried elsewhere in the registry).
It wont work with any other type of machines.
Those other tools mentioned previously may or may not work. Windows 10 remains a mystery to most of us, so it's all hit and miss with the use of 3rd party tools.
If you have questions about them, then ask at their respective support sites.
 
OK sounds good ... No questions I have the product Key using another product and just did a clean install and the key works great. Thank you..
 
This game of 'Where's Waldo' that Microsoft and the PC manufacturers have set up with the product key is just one more insidious way to get more money (milk) out of their customers (cattle). I had to reset my Windows and this blew away the product key. It's not in BIOS, it's not hidden anywhere on the disk.. Neither MS nor HP are willing to help me without my forking over more $$. I've been a devout Windows user for decades having changed camps when the Apple 2 was out, but I'm ready to go back. My hate for MS has finally turned to rage.
 
DocScience said:
This game of 'Where's Waldo' that Microsoft and the PC manufacturers have set up with the product key is just one more insidious way to get more money (milk) out of their customers (cattle). I had to reset my Windows and this blew away the product key. It's not in BIOS, it's not hidden anywhere on the disk.. Neither MS nor HP are willing to help me without my forking over more $$. I've been a devout Windows user for decades having changed camps when the Apple 2 was out, but I'm ready to go back. My hate for MS has finally turned to rage.
Click to expand...

I formatted my drive and reloaded 10 with no problems. I even reset another computer and still not one problem.
 
Jeff100 said:
I formatted my drive and reloaded 10 with no problems. I even reset another computer and still not one problem.
Click to expand...

Hi Jeff100. Which (other) product did you use to establish the Key for Win 10 re-installation? After the comments on this posting, I have downloaded a package but am put off because my Anti-Virus software is warning me against it. I suspect it may be a mis-warning but would rather not take the chance.

Thanks in anticipation.

Regards.

Geoff H.
 
Jeff100 said:
Yes I got it, but why is your product key tool not working? feels like we are just going in circles. But anyway no big deal thanks for your help someone sent me another tool and I got the key.
Click to expand...
Please what key was that, cause I really need help in finding my OEM key
 
aqk said:
Yep. That's the message I got when I tried to read my Windows 8.1 Product Key.
Any ideas?
Incidentally, I'm running Win 8.1 and Ubuntu 14.04 booted through GRUB.
As well I have an "older" Mainboard- Its AWARD BIOS does not have the newer EFI support.
Click to expand...
Sounds like your BIOS doesn’t support EFI, which might be why the product key isn’t showing. Running dual boot with GRUB on older hardware can cause this. Maybe try a tool that reads keys from BIOS or use a key finder in Windows. Good luck!
 
Back
Top