PFX import SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

PFX/P12 import fails: The specified network password is not correct (Windows)

Windows can't import the .pfx, either because the password is wrong or the file uses an unsupported/damaged format.

Exact message you may see The specified network password is not correctPFX import The specified network password is not correctImport-PfxCertificate: The specified network password is not correctcertutil -importpfx The specified network password is not correctWindows cannot import PFX password
Seen on: Windows SSL PowerShell

Meaning

Verify the password and the file with openssl pkcs12 -in file.pfx -noout. Re-export with a compatible algorithm (-keypbe PBE-SHA1-3DES -certpbe PBE-SHA1-3DES -macalg sha1 for old Windows, AES for current), and import with Import-PfxCertificate or certutil to see the exact error.

Common causes

  • Wrong password (or hidden characters)
  • PFX exported with AES not supported by an old Windows
  • Corrupt file transfer (text mode)
  • Missing private key in the file
  • Empty password confusion

⚡ Quick fix

  1. Test the file with OpenSSL
  2. Re-export with an algorithm compatible with the target Windows
  3. Use Import-PfxCertificate -Password

Detailed fix by platform

PowerShell

  1. bash
    $pw = ConvertTo-SecureString "secret" -AsPlainText -Force
    Import-PfxCertificate -FilePath .\site.pfx -CertStoreLocation Cert:\LocalMachine\My -Password $pw

How to diagnose

  1. Password — Correct?
  2. Algorithm — Supported?
  3. File — Intact?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

0x800CCC0D — Outlook error 0x800CCC0D: Cannot find the server — the host name of the mail server couldn't be resolved (Email / SMTP)0x800CCC0D0x800CCC0E — Outlook error 0x800CCC0E: Cannot connect to the outgoing (SMTP) server — sending failed (Email / SMTP)0x800CCC0Ecertificate does not have a private key (IIS) — Windows/IIS: A specified logon session does not exist / The certificate does not have a private key associated with it (SSL / TLS)certificate does not …Could not establish trust relationship for the SSL/TLS secure channel — .NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel (SSL / TLS)Could not establish t…CRYPT_E_NO_REVOCATION_CHECK — curl (Windows Schannel): schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate (SSL / TLS)CRYPT_E_NO_REVOCATION…Django — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)Djangolegacy provider — OpenSSL 3: Error outputting keys and certificates ... unsupported (PKCS#12 uses legacy RC2/3DES) (SSL / TLS)legacy providerPFX export — Cannot export or import the certificate with its private key (PFX/PKCS#12 has no private key) (SSL / TLS)PFX exportPFX import

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.