Described behavior of Set-SecureBootUEFI with the -ContentFilePath and -SignedFilePath parameters do not match actual behavior.

[wmjdgla]

Example 2: Set the DBX UEFI variable by using a signed package

PS C:\> Set-SecureBootUEFI -ContentFilePath FormattedVariable.bin -SignedFilePath GeneratedFileToSign.bin.p7
Name       : dbx 
Bytes      : {161, 89, 192, 165...} 
Attributes : NON VOLATILE 
             BOOTSERVICE ACCESS 
             RUNTIME ACCESS 
             TIME BASED AUTHENTICATED WRITE ACCESS

The output is incorrect. After executing the command, the output is:

Supply values for the following parameters:
Name: 

The user is prompted for the name of the UEFI variable to be set. After entering the name, the user is prompted:

Time:  

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: a83acc83-8bbf-c983-57bc-6a025330ae5d
• Version Independent ID: a732c541-8e27-4068-0d0c-2c0f17f0a334
• Content: Set-SecureBootUEFI (SecureBoot)
• Content Source: docset/winserver2022-ps/secureboot/Set-SecureBootUEFI.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[scanum]

@wmjdgla
This repository is for PowerShell core documentation. You seem to be looking for support, which we can't provide here.

I suggest you try posting your issue with context in one of the available community support forums.

[wmjdgla]

@scanum I'm really puzzled. I clearly stated that the documentation incorrect, and you somehow interpreted that I'm asking for support?

[scanum]

Hi @wmjdgla an apology for the misunderstanding, we will get someone to look at this issue as soon as possible.

[msbemba]

@wmjdgla Thank you for your feedback. We have made changes to the document via PR##3473

Once the author approves, the changes will be live.

Thanks
Sri

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!