{"id":3630,"date":"2016-06-04T12:13:39","date_gmt":"2016-06-04T17:13:39","guid":{"rendered":"http:\/\/neosmart.net\/blog\/?p=3630"},"modified":"2016-06-04T12:13:39","modified_gmt":"2016-06-04T17:13:39","slug":"embedded-product-key-tool-update","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/embedded-product-key-tool-update\/","title":{"rendered":"Windows Product Key Lookup Tool 1.1 Released"},"content":{"rendered":"<p><a href=\"http:\/\/neosmart.net\/blog\/wp-content\/uploads\/Logo-128x128.png\" rel=\"follow\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-3189 colorbox-3630\" src=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/Logo-128x128.png\" alt=\"Product Key Tool\" width=\"128\" height=\"128\" \/><\/a>An\u00a0update to our Windows 10 Product Key Utility has been issued that addresses a number of minor issues. Since <a href=\"https:\/\/neosmart.net\/blog\/2014\/windows-10-embedded-product-key-tool\/\" rel=\"follow\">its initial release<\/a> in December 2014, the BIOS-Embedded Product Key lookup tool has been downloaded and used over two hundred thousand times, and has quickly become the go-to tool for retrieving product keys embedded in the BIOS or system firmware.<\/p>\n<p><!--more--><\/p>\n<p>This update chiefly addresses what has a headache for us and our wonderful support staff and moderators over in the forums more than anything else, namely, the behavior of the utility when used on a PC without an embedded product key. The OEM\u00a0Product Key Tool was originally made for in-house use and provided to customers via the email customer support channel then released to the general public when it became apparent that it was a common enough issue that would benefit from a solution. As a result, the error messages weren&#8217;t very descriptive or user-friendly:<\/p>\n<div id=\"attachment_3631\" style=\"width: 511px\" class=\"wp-caption alignnone\"><a href=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/2618-5f063bc8c0d4179605a2c9efbecb4abb.png\" rel=\"follow\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-3631\" class=\"size-full wp-image-3631 colorbox-3630\" src=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/2618-5f063bc8c0d4179605a2c9efbecb4abb.png\" alt=\"The old &quot;Unable to open MSDM table&quot; error.\" width=\"501\" height=\"191\" srcset=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/2618-5f063bc8c0d4179605a2c9efbecb4abb.png 501w, https:\/\/neosmart.net\/blog\/wp-content\/uploads\/2618-5f063bc8c0d4179605a2c9efbecb4abb-500x191.png 500w\" sizes=\"auto, (max-width: 501px) 100vw, 501px\" \/><\/a><p id=\"caption-attachment-3631\" class=\"wp-caption-text\">The old &#8220;Unable to open MSDM table&#8221; error.<\/p><\/div>\n<p>This naturally generate a massive amount of questions and support requests, and an uncountable number of &#8220;this software is broken and doesn&#8217;t work&#8221; emails and forum threads. While frustrating to deal with, it&#8217;s certainly not hard to see why users would think the problem is with the software or their PC.<\/p>\n<p>As a general rule of thumb, if enough people complain about something then it&#8217;s broken, even if it&#8217;s not. So with nothing more than a single extra sentence injected into an existing line of code, the new error dialog in version 1.1 becomes like this:<\/p>\n<div id=\"attachment_3632\" style=\"width: 494px\" class=\"wp-caption alignnone\"><a href=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/Unable-to-open-MSDM-table.png\" rel=\"follow\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-3632\" class=\"size-full wp-image-3632 colorbox-3630\" src=\"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/Unable-to-open-MSDM-table.png\" alt=\"It took all of two minutes to change the error text to this, instead.\" width=\"484\" height=\"185\" \/><\/a><p id=\"caption-attachment-3632\" class=\"wp-caption-text\">It took all of two minutes to change the error text to this, instead.<\/p><\/div>\n<p>Not a functional change, but definitely a practical one!<\/p>\n<p>In addition, the version detection has been improved to correctly detect Windows 10,\u00a0and comes with an updated about dialog. It of course remains 100% free to download and use, remains standalone, and without any runtime dependencies:<\/p>\n<p><strong style=\"font-size:120%\">Download<\/strong><\/p>\n<p class=\"save\"><a style=\"font-size: 80%\" href=\"https:\/\/neosmart.net\/OemKey\/\" rel=\"follow\">Windows Embeded\u00a0Product Key Utility v1.1<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>An\u00a0update to our Windows 10 Product Key Utility has been issued that addresses a number of minor issues. Since its initial release in December 2014, the BIOS-Embedded Product Key lookup tool has been downloaded and used over two hundred thousand &hellip; <a href=\"https:\/\/neosmart.net\/blog\/embedded-product-key-tool-update\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":505,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[367,909,890,901,919],"class_list":["post-3630","post","type-post","status-publish","format-standard","hentry","category-software","tag-download","tag-free","tag-product-key-tool","tag-software","tag-update"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4xDa-Wy","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/3630","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/users\/505"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/comments?post=3630"}],"version-history":[{"count":5,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/3630\/revisions"}],"predecessor-version":[{"id":3637,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/3630\/revisions\/3637"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media?parent=3630"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/categories?post=3630"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/tags?post=3630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}