{"id":71912,"date":"2025-09-09T10:09:35","date_gmt":"2025-09-09T04:39:35","guid":{"rendered":"https:\/\/www.seminarsonly.com\/news\/?p=71912"},"modified":"2025-09-09T21:32:11","modified_gmt":"2025-09-09T16:02:11","slug":"a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix","status":"publish","type":"post","link":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/","title":{"rendered":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix"},"content":{"rendered":"<h3><span style=\"color: #008000;\"><em>I&#8217;ve created restrictions on our client devices so that they are only allowed to use TLS 1.2. Now in the event viewer i see tons of error messages: <strong>&#8220;A fatal error occurred while creating a TLS client credential. The internal error state is 10013.&#8221;<\/strong><\/em><\/span><\/h3>\n<h2 data-start=\"302\" data-end=\"324\"><span style=\"color: #800000;\">\u2705 Recommended Fixes<\/span><\/h2>\n<h3 data-start=\"326\" data-end=\"378\"><span style=\"color: #333399;\">1. Enable TLS Protocols in Internet Properties<\/span><\/h3>\n<p data-start=\"379\" data-end=\"416\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Temporarily re-enabling TLS 1.0 and 1.1 can help isolate the issue:<\/span><\/p>\n<ol data-start=\"418\" data-end=\"765\">\n<li data-start=\"418\" data-end=\"460\">\n<p data-start=\"421\" data-end=\"460\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Run <code data-start=\"4\" data-end=\"17\" data-is-last-node=\"\">inetcpl.cpl<\/code><\/span><\/p>\n<\/li>\n<li data-start=\"461\" data-end=\"503\">\n<p data-start=\"464\" data-end=\"503\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Open the <strong data-start=\"9\" data-end=\"21\">Advanced<\/strong> tab<\/span><\/p>\n<\/li>\n<li data-start=\"504\" data-end=\"683\">\n<p data-start=\"507\" data-end=\"546\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Under the <strong data-start=\"10\" data-end=\"22\">Security<\/strong> section, enable:<\/span><\/p>\n<ul data-start=\"550\" data-end=\"683\">\n<li data-start=\"550\" data-end=\"591\">\n<p data-start=\"552\" data-end=\"591\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">TLS\u00a01.0<\/span><\/p>\n<\/li>\n<li data-start=\"595\" data-end=\"636\">\n<p data-start=\"597\" data-end=\"636\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">TLS\u00a01.1<\/span><\/p>\n<\/li>\n<li data-start=\"640\" data-end=\"683\">\n<p data-start=\"642\" data-end=\"683\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">TLS\u00a01.2 and optionally TLS\u00a01.3<\/span><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li data-start=\"684\" data-end=\"765\">\n<p data-start=\"687\" data-end=\"765\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Apply changes and reboot.<\/span><\/p>\n<\/li>\n<\/ol>\n<hr data-start=\"767\" data-end=\"770\" \/>\n<h3 data-start=\"772\" data-end=\"814\"><span style=\"color: #333399;\">2. Enable TLS 1.2 \/ 1.3 via Registry<\/span><\/h3>\n<p data-start=\"815\" data-end=\"854\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Ensure the OS supports modern protocols correctly and disables obsolete ones:<\/span><\/p>\n<ul data-start=\"856\" data-end=\"1286\">\n<li data-start=\"856\" data-end=\"986\">\n<p data-start=\"858\" data-end=\"897\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Open <code data-start=\"5\" data-end=\"14\">regedit<\/code> and navigate to:<\/span><\/p>\n<div class=\"contain-inline-size rounded-2xl relative bg-token-sidebar-surface-primary\">\n<div class=\"overflow-y-auto p-4\" dir=\"ltr\"><code class=\"whitespace-pre!\">HKLM\\<span class=\"hljs-keyword\">SYSTEM<\/span>\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols<br \/>\n<\/code><\/div>\n<\/div>\n<\/li>\n<li data-start=\"987\" data-end=\"1204\">\n<p data-start=\"989\" data-end=\"1028\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Make sure both <strong data-start=\"15\" data-end=\"26\">TLS\u00a01.2<\/strong> (and TLS\u00a01.3, on supported systems) have the following subkeys:<\/span><\/p>\n<div class=\"contain-inline-size rounded-2xl relative bg-token-sidebar-surface-primary\">\n<div class=\"overflow-y-auto p-4\" dir=\"ltr\"><code class=\"whitespace-pre!\"><code class=\"whitespace-pre!\">[<span class=\"hljs-meta\">Protocol<\/span>]\\Client<br \/>\nDisabledByDefault = DWORD <span class=\"hljs-number\">0<\/span><br \/>\nEnabled = DWORD <span class=\"hljs-number\">1<\/span><\/code><\/code>[<span class=\"hljs-meta\">Protocol<\/span>]\\Server (<span class=\"hljs-keyword\">if<\/span> relevant)<br \/>\nDisabledByDefault = DWORD <span class=\"hljs-number\">0<\/span><br \/>\nEnabled = DWORD <span class=\"hljs-number\">1<\/span><\/p>\n<\/div>\n<\/div>\n<\/li>\n<li data-start=\"1206\" data-end=\"1286\">\n<p data-start=\"1208\" data-end=\"1286\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">If not present, create the keys manually. Reboot afterwards.<\/span><\/p>\n<\/li>\n<\/ul>\n<hr data-start=\"1288\" data-end=\"1291\" \/>\n<h3 data-start=\"1293\" data-end=\"1348\"><span style=\"color: #333399;\">3. Enable .NET to Use System Default TLS Versions<\/span><\/h3>\n<p data-start=\"1349\" data-end=\"1388\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Many applications built on .NET still default to older protocols unless configured:<\/span><\/p>\n<ul data-start=\"1390\" data-end=\"1789\">\n<li data-start=\"1390\" data-end=\"1707\">\n<p data-start=\"1392\" data-end=\"1431\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Add or update these registry keys:<\/span><\/p>\n<div class=\"contain-inline-size rounded-2xl relative bg-token-sidebar-surface-primary\">\n<div class=\"overflow-y-auto p-4\" dir=\"ltr\"><code class=\"whitespace-pre!\"><code class=\"whitespace-pre!\">HKLM\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319<br \/>\nSystemDefaultTlsVersions = DWORD 1<br \/>\nSchUseStrongCrypto = DWORD 1<\/code><\/code>HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\.NETFramework\\v4.0.30319<br \/>\nSystemDefaultTlsVersions = DWORD 1<br \/>\nSchUseStrongCrypto = DWORD 1<\/p>\n<\/div>\n<\/div>\n<\/li>\n<li data-start=\"1709\" data-end=\"1789\">\n<p data-start=\"1711\" data-end=\"1789\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Also apply to .NET 2.0\/3.5 if required. Reboot to apply.<\/span><\/p>\n<\/li>\n<\/ul>\n<hr data-start=\"1791\" data-end=\"1794\" \/>\n<h3 data-start=\"1796\" data-end=\"1842\"><span style=\"color: #333399;\">4. Use IIS Crypto Tool (GUI Alternative)<\/span><\/h3>\n<p data-start=\"1843\" data-end=\"1882\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">If you&#8217;re uncomfortable editing the registry:<\/span><\/p>\n<ul data-start=\"1884\" data-end=\"2026\">\n<li data-start=\"1884\" data-end=\"1925\">\n<p data-start=\"1886\" data-end=\"1925\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Download and run <strong data-start=\"17\" data-end=\"31\">IIS Crypto<\/strong> from Nartac Software.<\/span><\/p>\n<\/li>\n<li data-start=\"1926\" data-end=\"1967\">\n<p data-start=\"1928\" data-end=\"1967\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">Click <strong data-start=\"6\" data-end=\"24\">Best Practices<\/strong> to configure TLS protocols and cipher suites automatically.<\/span><\/p>\n<\/li>\n<li data-start=\"1968\" data-end=\"2026\">\n<p data-start=\"1970\" data-end=\"2026\">Reboot afterward.<\/p>\n<\/li>\n<\/ul>\n<hr data-start=\"2028\" data-end=\"2031\" \/>\n<h3 data-start=\"2033\" data-end=\"2097\"><span style=\"color: #333399;\">5. Reset NTFS Permissions for MachineKeys (Advanced Issue)<\/span><\/h3>\n<p data-start=\"2098\" data-end=\"2137\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">On some Windows 11\/10 systems, improper permissions or ghost profiles in:<\/span><\/p>\n<div class=\"contain-inline-size rounded-2xl relative bg-token-sidebar-surface-primary\">\n<div class=\"overflow-y-auto p-4\" dir=\"ltr\"><code class=\"whitespace-pre!\"><span class=\"hljs-section\">C:\\ProgramData\\Microsoft\\Crypto\\RSA\\MachineKeys<\/span><br \/>\n<\/code><\/div>\n<\/div>\n<p data-start=\"2196\" data-end=\"2235\"><span class=\"relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out\">can cause TLS credentials to fail. Resetting permissions may resolve persistent errors:<\/span><\/p>\n<div class=\"contain-inline-size rounded-2xl relative bg-token-sidebar-surface-primary\">\n<div class=\"overflow-y-auto p-4\" dir=\"ltr\"><code class=\"whitespace-pre!\">icacls <span class=\"hljs-string\">\"C:\\ProgramData\\Microsoft\\Crypto\\RSA\\MachineKeys\"<\/span> \/reset \/t \/c \/l<\/code><\/div>\n<\/div>\n<hr data-start=\"2359\" data-end=\"2362\" \/>\n<h3 data-start=\"2364\" data-end=\"2420\"><span style=\"color: #333399;\">6. Identify the Faulty Process (If Errors Persist)<\/span><\/h3>\n<ul data-start=\"2421\" data-end=\"2736\">\n<li data-start=\"2421\" data-end=\"2504\">\n<p data-start=\"2423\" data-end=\"2504\">Open <strong data-start=\"2428\" data-end=\"2444\">Event Viewer<\/strong> \u2192 Filter <strong data-start=\"2454\" data-end=\"2483\">Schannel \/ Event ID 36871<\/strong> to find the <strong data-start=\"2496\" data-end=\"2503\">PID<\/strong>.<\/p>\n<\/li>\n<li data-start=\"2505\" data-end=\"2588\">\n<p data-start=\"2507\" data-end=\"2588\">Match the PID in <strong data-start=\"2524\" data-end=\"2550\">Task Manager \u2192 Details<\/strong> to see which app triggered the error.<\/p>\n<\/li>\n<li data-start=\"2589\" data-end=\"2736\">\n<p data-start=\"2591\" data-end=\"2736\">Some users resolved it by logging out of <strong data-start=\"2632\" data-end=\"2655\">Mail &amp; Calendar app<\/strong>, which triggered the issue in their case.<\/p>\n<\/li>\n<\/ul>\n<h2 id=\"toc-hId--1798703887\"><span style=\"color: #800000;\">Enable TLS 1.2 for Schannel<\/span><\/h2>\n<h3 id=\"toc-hId--252407057\">All Windows Server versions<\/h3>\n<p>TLS protocols are enabled or disabled in Windows Schannel by editing the Windows Registry. Each protocol version can be enabled or disabled independently. You don&#8217;t need to enable or disable one protocol version to enable or disable another protocol version.<\/p>\n<p>he <strong>Enabled<\/strong> DWORD registry value defines whether the protocol version can be used. If the value is set to 0, the protocol version cannot be used, even if it is enabled by default or if the application explicitly requests that protocol version. If the value is set to 1, the protocol version can be used if enabled by default or if the application explicitly requests that protocol version. If the value is not defined, the operating system\u2019s default value will be used. We recommend configuring the value to have a consistent state across your servers.<\/p>\n<p>The\u00a0<strong>DisabledByDefault<\/strong>\u00a0DWORD registry value defines whether the protocol version is used by default. This setting only applies when the application doesn&#8217;t explicitly request the protocol versions to be used. If the value is set to 0, the protocol version will be available for use by default. If the value is set to 1, the protocol version will not be available for use by default. If the value is not defined, the operating system\u2019s default value will be used.<\/p>\n<h3>Also Read : <a href=\"https:\/\/www.seminarsonly.com\/news\/activate-vestavia-activate-games-now-in-vestavia\/\">Activate Games now in Vestavia<\/a><\/h3>\n<p>We recommend configuring the value to have a consistent state across your servers. For example; consider what would happen if TLS 1.2\u2019s values were set to a combination of\u00a0<strong>Enabled<\/strong>\u00a0and\u00a0<strong>DisabledByDefault<\/strong>\u00a0both set to a value of 1. In this example an application could only use TLS 1.2 if the application specifically called for TLS 1.2. If the application did not specifically call for TLS 1.2, then it would not be able to use TLS 1.2 as even though the protocol is enabled, it is not in the default list of available protocols. To enable TLS 1.2 for both server (inbound) and client (outbound) connections on an Exchange Server please perform the following.<\/p>\n<ol>\n<li>From Notepad.exe, create a text file named\u00a0<strong>TLS12-Enable.reg<\/strong>.<\/li>\n<li>Copy and paste the following text into the file.<\/li>\n<\/ol>\n<p class=\"code\">Windows Registry Editor Version 5.00<br \/>\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.2]<br \/>\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.2\\Client]<br \/>\n&#8220;DisabledByDefault&#8221;=dword:00000000<br \/>\n&#8220;Enabled&#8221;=dword:00000001<br \/>\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.2\\Server]<br \/>\n&#8220;DisabledByDefault&#8221;=dword:00000000<br \/>\n&#8220;Enabled&#8221;=dword:00000001<\/p>\n<ol start=\"3\">\n<li>Save\u00a0<strong>TLS12-Enable.reg<\/strong>.<\/li>\n<li>Double-click the\u00a0<strong>TLS12-Enable.reg<\/strong>\u00a0file.<\/li>\n<li>Click\u00a0<strong>Yes<\/strong>\u00a0to update your Windows Registry with these changes.<\/li>\n<li>Restart the machine for the changes to take effect.<\/li>\n<\/ol>\n<h2 id=\"toc-hId--865240178\"><span style=\"color: #800000;\">Enable TLS 1.2 for .NET 4.x<\/span><\/h2>\n<p>This step is only required for Exchange Server 2013 or later installations where .NET 4.x is relied upon. The\u00a0<strong>SystemDefaultTlsVersions<\/strong>\u00a0registry value defines which security protocol version defaults will be used by .NET Framework 4.x. If the value is set to 1, then .NET Framework 4.x will inherit its defaults from the Windows Schannel\u00a0<strong>DisabledByDefault<\/strong>\u00a0registry values. If the value is undefined, it will behave as if the value is set to 0. By configuring .NET Framework 4.x to inherit its values from Schannel we gain the ability to use the latest versions of TLS supported by the OS, including TLS 1.2.<\/p>\n<ol>\n<li>From Notepad.exe, create a text file named\u00a0<strong>NET4X-UseSchannelDefaults.reg<\/strong>.<\/li>\n<li>Copy, and then paste the following text.<\/li>\n<\/ol>\n<p class=\"code\">Windows Registry Editor Version 5.00<br \/>\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319]<br \/>\n&#8220;SystemDefaultTlsVersions&#8221;=dword:00000001<br \/>\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319]<br \/>\n&#8220;SystemDefaultTlsVersions&#8221;=dword:00000001<\/p>\n<ol start=\"3\">\n<li>Save the\u00a0<strong>NET4X-UseSchannelDefaults.reg<\/strong>\u00a0file.<\/li>\n<li>Double-click the\u00a0<strong>NET4X-UseSchannelDefaults.reg<\/strong>\u00a0file.<\/li>\n<li>Click\u00a0<strong>Yes\u00a0<\/strong>to update your Windows Registry with these changes.<\/li>\n<li>Restart your computer for the change to take effect.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve created restrictions on our client devices so that they are only allowed to use TLS 1.2. Now in the event viewer i see tons of error messages: &#8220;A fatal&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6048],"tags":[],"class_list":["post-71912","post","type-post","status-publish","format-standard","hentry","category-error-fix"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix - Seminarsonly.com<\/title>\n<meta name=\"description\" content=\"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to &quot;MachineKeys&quot; folder broke our IIS and we had to restore the server from a backup\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix\" \/>\n<meta property=\"og:description\" content=\"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to &quot;MachineKeys&quot; folder broke our IIS and we had to restore the server from a backup\" \/>\n<meta property=\"og:url\" content=\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\" \/>\n<meta property=\"og:site_name\" content=\"Seminarsonly.com\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/seminarsonly\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-09T04:39:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-09T16:02:11+00:00\" \/>\n<meta name=\"author\" content=\"Freddy John\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@seminarsonly\" \/>\n<meta name=\"twitter:site\" content=\"@seminarsonly\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Freddy John\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\"},\"author\":{\"name\":\"Freddy John\",\"@id\":\"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd\"},\"headline\":\"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix\",\"datePublished\":\"2025-09-09T04:39:35+00:00\",\"dateModified\":\"2025-09-09T16:02:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\"},\"wordCount\":912,\"commentCount\":0,\"articleSection\":[\"Error Fix\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\",\"url\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\",\"name\":\"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix - Seminarsonly.com\",\"isPartOf\":{\"@id\":\"https:\/\/seminarsonly.com\/news\/#website\"},\"datePublished\":\"2025-09-09T04:39:35+00:00\",\"dateModified\":\"2025-09-09T16:02:11+00:00\",\"author\":{\"@id\":\"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd\"},\"description\":\"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to \\\"MachineKeys\\\" folder broke our IIS and we had to restore the server from a backup\",\"breadcrumb\":{\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/seminarsonly.com\/news\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/seminarsonly.com\/news\/#website\",\"url\":\"https:\/\/seminarsonly.com\/news\/\",\"name\":\"Seminarsonly.com\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/seminarsonly.com\/news\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd\",\"name\":\"Freddy John\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g\",\"caption\":\"Freddy John\"},\"sameAs\":[\"https:\/\/seminarsonly.com\/news\"],\"url\":\"https:\/\/seminarsonly.com\/news\/author\/anupvnaick_51wq8y4s\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix - Seminarsonly.com","description":"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to \"MachineKeys\" folder broke our IIS and we had to restore the server from a backup","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/","og_locale":"en_US","og_type":"article","og_title":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix","og_description":"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to \"MachineKeys\" folder broke our IIS and we had to restore the server from a backup","og_url":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/","og_site_name":"Seminarsonly.com","article_publisher":"https:\/\/facebook.com\/seminarsonly","article_published_time":"2025-09-09T04:39:35+00:00","article_modified_time":"2025-09-09T16:02:11+00:00","author":"Freddy John","twitter_card":"summary_large_image","twitter_creator":"@seminarsonly","twitter_site":"@seminarsonly","twitter_misc":{"Written by":"Freddy John","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#article","isPartOf":{"@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/"},"author":{"name":"Freddy John","@id":"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd"},"headline":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix","datePublished":"2025-09-09T04:39:35+00:00","dateModified":"2025-09-09T16:02:11+00:00","mainEntityOfPage":{"@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/"},"wordCount":912,"commentCount":0,"articleSection":["Error Fix"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/","url":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/","name":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix - Seminarsonly.com","isPartOf":{"@id":"https:\/\/seminarsonly.com\/news\/#website"},"datePublished":"2025-09-09T04:39:35+00:00","dateModified":"2025-09-09T16:02:11+00:00","author":{"@id":"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd"},"description":"Enabling FIPS fixes the issue but the mail delivery stops which is a disadvantage on an Exchange server! Changing the Read permission to \"MachineKeys\" folder broke our IIS and we had to restore the server from a backup","breadcrumb":{"@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/seminarsonly.com\/news\/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013-error-fix\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/seminarsonly.com\/news\/"},{"@type":"ListItem","position":2,"name":"A Fatal Error Occurred While Creating a TLS Client Credential. The Internal Error State is 10013 Error Fix"}]},{"@type":"WebSite","@id":"https:\/\/seminarsonly.com\/news\/#website","url":"https:\/\/seminarsonly.com\/news\/","name":"Seminarsonly.com","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/seminarsonly.com\/news\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/seminarsonly.com\/news\/#\/schema\/person\/75cf706896b7210fb0a84651adc258bd","name":"Freddy John","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/671d452f5fe9027ab894cbed50911cc764b2c16878222070bf044f21705d4c94?s=96&d=mm&r=g","caption":"Freddy John"},"sameAs":["https:\/\/seminarsonly.com\/news"],"url":"https:\/\/seminarsonly.com\/news\/author\/anupvnaick_51wq8y4s\/"}]}},"_links":{"self":[{"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/posts\/71912","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/comments?post=71912"}],"version-history":[{"count":0,"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/posts\/71912\/revisions"}],"wp:attachment":[{"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/media?parent=71912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/categories?post=71912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seminarsonly.com\/news\/wp-json\/wp\/v2\/tags?post=71912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}