Certreq error 0x80090020 NTE_FAIL

ScottyDoo 111 Reputation points
2023-08-22T13:02:58.9033333+00:00

Hi,

I am having an issue trying to generate a basic CSR with certreq

OS: Windows 11 22H2 VDI with vTPM on VMWare 7

Issue: We are trying to generate a basic CSR using

Certreq -new <path to Inf> <path to CSR>

however it returns the error: “An internal error occurred. 0x80090020 (-2146893792 NTE_FAIL)”

We are using a basic request policy, I’ve tried a few variations but I don’t think the request file is the issue. We just need to generate the key pair so we have the corresponding private key when the CSR is singed. Policy file:

[Version]
Signature = "$WindowsNT$"
 
[NewRequest]
Subject = "CN=XXXX"
Exportable = TRUE
KeyLength = 2048
MachineKeySet = FALSE

We are seeing errors logged in the Windows “Crypto-NCrypt” log for the user trying to run the certreq command:

Cryptographic Operation failed.
 
Cryptographic Parameters:
      OperationType:     17
      Provider Name:     Microsoft Software Key Storage Provider
      Key Name:         NULL
      Key Type:        
      Algorithm Name:   
 
Failure Information:
      Return Code:       0x80090029
 

And:

Cryptographic Operation failed.
 
Cryptographic Parameters:
      OperationType:     16
      Provider Name:     Microsoft Platform Crypto Provider
      Key Name:         NULL
      Key Type:        
      Algorithm Name:   
 
Failure Information:
      Return Code:       0x80090029
 

I feel like it’s something to do with the vTPM but its not really my area of expertise. Thanks

Windows for business | Windows Client for IT Pros | User experience | Other

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Answer recommended by moderator
ScottyDoo 111 Reputation points
2025-01-15T12:41:51.5733333+00:00

Hi, yes, sorry for not posting our fix... For us this was a legacy Cryptographic provider DLL that was no longer present but still being set via a GPO... We found the key being added to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Defaults\Provider

We deleted the old provider key and everything started working.

Hope this helps.

Thanks.

Was this answer helpful?

1 additional answer

Sort by: Oldest
  1. Limitless Technology 45,246 Reputation points
    2023-08-23T09:33:23.8766667+00:00

    Hello

    Thank you for your question and reaching out.

    1. Each host must have a licence.
    2. Each physical processor must have a minimum of 8 core licences, and each server must have a minimum of 16 core licences.
    3. Core licences are offered in two-packs.
    4. When all physical cores in the server are licenced, Standard Edition grants rights for up to 2 Operating System Environments or Windows Server containers with Hyper-V isolation. All of the physical cores in the server must be licenced again for every additional 1 or 2 VMs.
    5. When all physical cores in the server are licenced, DataCenter Edition grants rights for an unlimited number of Operating System Environments or Windows Server containers with Hyper-V isolation.

    https://download.microsoft.com/download/7/C/E/7CED6910-C7B2-4196-8C55-208EE0B427E2/Windows_Server_2019_licensing_datasheet_EN_US.pdf

    --If the reply is helpful, please Upvote and Accept as answer--

    Was this answer helpful?