SPFX Error - [trust-cert] CertUtil Error

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

Additional environment details

browser version - Version 116.0.1938.69 (Official build) (64-bit)
SPFx version - 1.17.4
gulp-cli@2.3.0
touch-cli@0.0.1
yo@4.3.1
Node.js version - v16.13.0
OS - Win 11 Pro

Describe the bug / error

I have been getting this error after trying to execute gulp trust-dev-cert on a new web part project and haven't been able to fix it, please kindly help. I followed the set up process here https://learn.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment and also tried in my other PC but still throws the same error. I am executing this statement from the webpart solution folder. It does give me the Certificate installation prompt for localhost and after the error is thrown, it creates rushstack-serve.key, rushstack-serve.pem files in .rushstack folder. Here is the error:

Thank you.

Steps to reproduce

Install node v16.13.0
install gulp cli, yoeman and sharepoint generator
Create webpart with the generator scaffolding
Run gulp trust-dev-cert

Expected behavior

certificate successfully installed and running gulp serve would bring up the workspace

WymerDev

Hi WymerDev , I just tried to repro this locally but didn't see the issue.

Are you seeing an issue when you actually do a gulp serve and test on a SharePoint page (e.g. workbench)? You would basically see an error around non-https resources being attempted to be loaded.

Can you try running gulp untrust-dev-cert and then retry gulp trust-dev-cert?

Last, the prompt should elevate, but it may be worth trying to run command prompt with Run As Administrator before running the gulp trust-dev-cert command.

Nick Pape (@nick-pape)

Hi Nick Pape (@nick-pape) I get this before doing gulp serve and when I execute this command it just throws this error "The existing development certificate is not currently trusted by your system. Untrust the certificate and generate a new one, or set the canGenerateNewCertificate parameter to true when calling ensureCertificateAsync."
I have tried gulp untrust-dev-cert and then retry gulp trust-dev-cert but I keep getting the same CertUtil Error with Task errors:1.
And yes I am using Windows PowerShell with elevated perms (Admin) .

Thank you for looking into it.

Looking into the error further... The code for this task is public here. It uses the CertificateManager from rushstack here.

The error looks like is written here when setting the friendly name.

I see several issues with this code:

The code is writing the (empty) stderr from certutil.exe to stderr, which overall makes SPFx build tools believe this task has failed, despite this step appearing to be "optional".
We aren't writing certutil.exe's stdout anywhere, which makes this issue hard to debug.
The code that is calling _trySetFriendlyNameAsync is lacking an await (here)[https://github.com/microsoft/rushstack/blame/main/libraries/debug-certificate-manager/src/CertificateManager.ts#L746]. So the warning specific to this step isn't appearing.

1st - learn why setting friendly name is failing

Can you try opening the node_modules/@rushstack/debug-certificate-manager/lib/CertificateManager.js locally and adding the following line:

Then run gulp trust-dev-cert --verbose and post the output.

This should give us an idea why setting friendly name is failing. If we can resolve that issue first you will be unblocked sooner than waiting for a code change.

2nd - update the following 2 lines and see if you are able to serve via https

After doing step 1 above.

Change both lines to be a warning instead of an error:

Add an await where this is called:

Run gulp trust-dev-cert --verbose twice. The first time you should see the warning. The second time you should see something like:

Then run gulp serve and test out the webpart on the workbench and post any errors you get (would be relating to https).

Nick Pape (@nick-pape)

Hi Nick Pape (@nick-pape). Thank you for the steps. I updated the js file as advised and followed the steps to get these output below:

1st (adding stdout line):

[11:48:48] Starting 'trust-dev-cert'...
[11:48:48] Starting gulp
[11:48:48] Starting subtask 'trust-cert'...
[11:48:48] [trust-cert] Attempting to trust a development certificate. This self-signed certificate only points to localhost and will be stored in your local user profile to be used by other instances of debug-certificate-manager. If you do not consent to trust this certificate, click "NO" in the dialog.
[11:48:50] [trust-cert] Successfully trusted development certificate.
[11:48:50] Finished subtask 'trust-cert' after 2.47 s
[11:48:50] Finished 'trust-dev-cert' after 2.47 s
[11:48:50] Error - [trust-cert] CertUtil Error:
[11:48:50] Error - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.

[11:48:51] ==================[ Finished ]==================
Error - [trust-cert] CertUtil Error:
Error - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.
[11:48:51] Suppressing - Warning - [sass] The local CSS class 'ms-Grid' is not camelCase and will not be type-safe.
[11:48:51] Project hw-web-part-1 version:0.0.1
[11:48:51] Build tools version:3.17.20
[11:48:51] Node version:v16.13.0
[11:48:51] Total duration:5.56 s
[11:48:51] Task errors:2

2nd: 1 - Update to warning, adding await, 1st run

[12:27:00] Starting 'trust-dev-cert'...
[12:27:00] Starting gulp
[12:27:00] Starting subtask 'trust-cert'...
[12:27:00] [trust-cert] The development certificate was not found in the store. CertUtil error:
[12:27:00] Warning - [trust-cert] The existing development certificate is not currently trusted by your system. Attempting to untrust the certificate and generate a new one.
[12:27:01] [trust-cert] Successfully untrusted development certificate.
[12:27:01] [trust-cert] Attempting to trust a development certificate. This self-signed certificate only points to localhost and will be stored in your local user profile to be used by other instances of debug-certificate-manager. If you do not consent to trust this certificate, click "NO" in the dialog.
[12:27:03] [trust-cert] Successfully trusted development certificate.
[12:27:03] Warning - [trust-cert] CertUtil Error:
[12:27:03] Warning - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.

[12:27:03] Warning - [trust-cert] Unable to set the certificate's friendly name.
[12:27:03] Finished subtask 'trust-cert' after 2.55 s
[12:27:03] Finished 'trust-dev-cert' after 2.55 s
[12:27:03] ==================[ Finished ]==================
Warning - [trust-cert] The existing development certificate is not currently trusted by your system. Attempting to untrust the certificate and generate a new one.
Warning - [trust-cert] CertUtil Error:
Warning - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.

Warning - [trust-cert] Unable to set the certificate's friendly name.
[12:27:04] Suppressing - Warning - [sass] The local CSS class 'ms-Grid' is not camelCase and will not be type-safe.
[12:27:04] Project hw-web-part-1 version:0.0.1
[12:27:04] Build tools version:3.17.20
[12:27:04] Node version:v16.13.0
[12:27:04] Total duration:5.68 s
[12:27:04] Task warnings:4

2nd: 2 - Update to warning, adding await, 2nd run

[12:29:41] Starting 'trust-dev-cert'...
[12:29:41] Starting gulp
[12:29:41] Starting subtask 'trust-cert'...
[12:29:41] [trust-cert] The development certificate was not found in the store. CertUtil error:
[12:29:41] Warning - [trust-cert] The existing development certificate is not currently trusted by your system. Attempting to untrust the certificate and generate a new one.
[12:29:41] [trust-cert] Successfully untrusted development certificate.
[12:29:41] [trust-cert] Attempting to trust a development certificate. This self-signed certificate only points to localhost and will be stored in your local user profile to be used by other instances of debug-certificate-manager. If you do not consent to trust this certificate, click "NO" in the dialog.
[12:29:43] [trust-cert] Successfully trusted development certificate.
[12:29:43] Warning - [trust-cert] CertUtil Error:
[12:29:43] Warning - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.

[12:29:43] Warning - [trust-cert] Unable to set the certificate's friendly name.
[12:29:43] Finished subtask 'trust-cert' after 2.54 s
[12:29:43] Finished 'trust-dev-cert' after 2.54 s
[12:29:44] ==================[ Finished ]==================
Warning - [trust-cert] The existing development certificate is not currently trusted by your system. Attempting to untrust the certificate and generate a new one.
Warning - [trust-cert] CertUtil Error:
Warning - [trust-cert] CertUtil Error: root "Trusted Root Certification Authorities"
CertUtil: -repairstore command FAILED: 0x80090011 (-2146893807 NTE_NOT_FOUND)
CertUtil: Object was not found.

Warning - [trust-cert] Unable to set the certificate's friendly name.
[12:29:44] Suppressing - Warning - [sass] The local CSS class 'ms-Grid' is not camelCase and will not be type-safe.
[12:29:44] Project hw-web-part-1 version:0.0.1
[12:29:44] Build tools version:3.17.20
[12:29:44] Node version:v16.13.0
[12:29:44] Total duration:5.7 s
[12:29:44] Task warnings:4

I didn't get the one like in your screenshot and didn't notice any change between the 1st and the 2nd runs.

3rd - running gulp serve

Build target: DEBUG
[12:38:16] Using gulpfile C:\SPFX\HWWebPart1\gulpfile.js
[12:38:16] Starting 'serve'...
[12:38:16] Starting gulp
[12:38:16] Starting subtask 'spfx-serve'...
[12:38:16] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
[12:38:17] Error - 'spfx-serve' sub task errored after 343 ms
The existing development certificate is not currently trusted by your system. Untrust the certificate and generate a new one, or set the canGenerateNewCertificate parameter to true when calling ensureCertificateAsync.
[12:38:17] 'serve' errored after 349 ms
[12:38:17]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1

My local CertificateManager.js updated snippet:

Hope the verbose error messages can help.
Thank you.

Interesting, so the deeper cause here is that the certificate that is trying to be updated with a friendly name isn't being found. That means there must be a hidden error occurring when trying to install the certificate.

Nick Pape (@nick-pape)

Nick Pape (@nick-pape) Checking to see if this issue is indeed a bug and is awaiting resolution? Meanwhile are there any another/older working versions so I can work on SPFX development? Thank you.

WymerDev

WymerDev Please try adding "C:\Windows\System32" in your environment variables and then should work.

WymerDev

WymerDev,
Just following up on the issue.

Have you been able to resolve the problem?

I think I did , I just forget to enter that terminal instance as an admin. But to be honest , it was brutal to debug the issue if someone new and he doesn't know how node js works. I had to comment out tones of code to get it working until I found an alternative solution. It was a stupid mistake.

…

On Wed, Jul 16, 2025, 8:49 AM Ashlesha-MSFT ***@***.***> wrote: *Ashlesha-MSFT* left a comment (SharePoint/sp-dev-docs#9201) <#9201 (comment)> @WymerDev <https://github.com/WymerDev>, Just following up on the issue. Have you been able to resolve the problem? — Reply to this email directly, view it on GitHub <#9201 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJATKRJE67T7QC4NKNSW2L3IZC5VAVCNFSM6AAAAABRXAO7NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANZYGQZTMOBQGM> . You are receiving this because you commented.Message ID: ***@***.***>

just want to add my solution for the one of possible reasons causing such an issue:

gulp trust-dev-cert --verbose

=>

Build target: DEBUG
Found config file: sass.json
Found config file: serve.json
Found config file: deploy-azure-storage.json
Found config file: package-solution.json
[15:18:28] Using gulpfile My_PATH\gulpfile.js
[15:18:28] Starting 'trust-dev-cert'...
[15:18:28] Starting gulp
[15:18:28] Starting subtask 'trust-cert'...
[15:18:28] [trust-cert] Attempting to trust a development certificate. This self-signed certificate only points to localhost and will be stored in your local user profile to be used by other instances of debug-certificate-manager. If you do not consent to trust this certificate, click "NO" in the dialog.
[15:18:28] Error - [trust-cert] Error: root "Trusted Root Certification Authorities"
,Signature matches Public Key
,CertUtil: -addstore command FAILED: 0x80070005 (WIN32: 5 ERROR_ACCESS_DENIED)
,CertUtil: Access is denied.

[15:18:28] Error - [trust-cert] Certificate trust failed with an unknown error.
[15:18:28] Error - 'trust-cert' sub task errored after 605 ms
 Error: Error trusting development certificate.
    at TrustCertTask.executeTask (My_PATH\node_modules\@microsoft\gulp-core-build-serve\lib\TrustCertTask.js:26:19)
[15:18:28] 'trust-dev-cert' errored after 612 ms
[15:18:28] Error: Error trusting development certificate.
    at TrustCertTask.executeTask (My_PATH\node_modules\@microsoft\gulp-core-build-serve\lib\TrustCertTask.js:26:19)
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1

eventually what helped:

for HKEY_CURRENT_USER\Software\Microsoft\SystemCertificates\Root\ProtectedRoots key give at least read rights for MachineName\Administrators, found here

If the issue is resolved, Can we go ahead and close the issue?

This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.

Navigation Menu

Repository navigation

SPFX Error - [trust-cert] CertUtil Error #9201

Target SharePoint environment

What SharePoint development model, framework, SDK or API is this about?

Developer environment

What browser(s) / client(s) have you tested

Additional environment details

Describe the bug / error

Steps to reproduce

Expected behavior

1st - learn why setting friendly name is failing

2nd - update the following 2 lines and see if you are able to serve via https

1st (adding stdout line):

2nd: 1 - Update to warning, adding await, 1st run

2nd: 2 - Update to warning, adding await, 2nd run

3rd - running gulp serve

My local CertificateManager.js updated snippet:

11 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

SPFX Error - [trust-cert] CertUtil Error #9201

Description

Target SharePoint environment

What SharePoint development model, framework, SDK or API is this about?

Developer environment

What browser(s) / client(s) have you tested

Additional environment details

Describe the bug / error

Steps to reproduce

Expected behavior

Activity

nick-pape commented on Sep 11, 2023

WymerDev commented on Sep 11, 2023

nick-pape commented on Sep 12, 2023

1st - learn why setting friendly name is failing

2nd - update the following 2 lines and see if you are able to serve via https

WymerDev commented on Sep 12, 2023

1st (adding stdout line):

2nd: 1 - Update to warning, adding await, 1st run

2nd: 2 - Update to warning, adding await, 2nd run

3rd - running gulp serve

My local CertificateManager.js updated snippet:

nick-pape commented on Sep 14, 2023

WymerDev commented on Sep 28, 2023

AkshayKishorChauhan commented on Oct 1, 2023

11 remaining items

Ashlesha-MSFT commented on Jul 16, 2025

hillal20 commented on Jul 17, 2025

tivanchuk-hawe commented on Aug 20, 2025

Ashlesha-MSFT commented on Oct 7, 2025

VesaJuvonen commented on Nov 3, 2026

github-actions commented on Nov 3, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions