Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
pls help..
- Thread starter RadoslavV1
- Start date
Had the same issue today as well. Worked through all options I could find online to no avail. I then sent a request to Support for help but have not heard back. In the meantime, I decided to try a solution through ChatGPT and it worked perfectly. Windows came back up, did two upgrades, and then asked me to recreate my PIN. After that, it all was good. Hope this helps anyone else who get the "Secure Boot found unauthorized changes to the firmware, operating system, or UEFI drivers. To manage Secure Boot settings, go to the virtual machine configuration settings, click Hardware, and expand Advanced Settings."
Attachments
Sebastian22
Bit poster
What solved it for me:
- open VM configuration
- go to Hardware
- remove the TPM Module
- start VM (now it works)
- shutdown VM
- add TPM module back
Thank you very much, VM (W11) is working again in my MacBook M4
I am experiencing an issue with Parallels Desktop on my Mac.
My virtual machine running Windows 11 was working normally until yesterday. However, today it fails to start and shows the following error:
"The Secure Boot feature prevented the operating system from starting. The Secure Boot policy settings in the firmware could not authenticate the code. Check the Secure Boot policy in Setup."
I did not make any manual changes to the virtual machine configuration. The issue appeared अचानक (possibly after an update or system restart).
I have checked the VM configuration, but I cannot find or modify the Secure Boot setting.
Could you please assist in resolving this issue?
Thank you.[/QUOTE]
My virtual machine running Windows 11 was working normally until yesterday. However, today it fails to start and shows the following error:
"The Secure Boot feature prevented the operating system from starting. The Secure Boot policy settings in the firmware could not authenticate the code. Check the Secure Boot policy in Setup."
I did not make any manual changes to the virtual machine configuration. The issue appeared अचानक (possibly after an update or system restart).
I have checked the VM configuration, but I cannot find or modify the Secure Boot setting.
Could you please assist in resolving this issue?
Thank you.[/QUOTE]
Hello, does it really work? I have Parallels 2026 and Win 11, MacBook. Thank youThank you very much, VM (W11) is working again in my MacBook M4
[/QUOTE]I am experiencing an issue with Parallels Desktop on my Mac.
My virtual machine running Windows 11 was working normally until yesterday. However, today it fails to start and shows the following error:
"The Secure Boot feature prevented the operating system from starting. The Secure Boot policy settings in the firmware could not authenticate the code. Check the Secure Boot policy in Setup."
I did not make any manual changes to the virtual machine configuration. The issue appeared अचानक (possibly after an update or system restart).
I have checked the VM configuration, but I cannot find or modify the Secure Boot setting.
Could you please assist in resolving this issue?
Thank you.
See my answer on the previous page
consider renaming the thread with a more descriptive title than "pls help", something that helps other people find it ("The Secure Boot feature prevented the operating system from starting")when installing w10 I always get this message about firmware and uefi, I can't figure out where to enable it .. installation of w10 fails, can't start .. so please advise what to do with it, i have the latest version of parallels pro..
pls help..
We observed that you encountered the error message "The Secure Boot Feature prevented the operating system from starting" when attempting to launch your virtual machine. This typically occurs when a recent Secure Boot certificate update hasn't yet been recognized by the virtual machine's older TPM (Trusted Platform Module) chip, a security component that verifies system integrity during startup.
Important note about BitLocker: If your Windows virtual machine uses BitLocker encryption, please ensure you have your BitLocker recovery key readily available before proceeding. After applying either workaround below, Windows may prompt for this key during startup. To locate your recovery key, please see Find your BitLocker recovery key.
Prerequisite: Before making any changes, we recommend creating a snapshot to preserve your current virtual machine state.
Workaround: Remove and re-add the TPM chip
1. Right-click the Parallels Desktop icon in your Mac dock and select "Control Center."
2. Click the gear/cog icon next to your virtual machine.
3. Select "Hardware."
4. Click "TPM Chip" in the left sidebar.
5. Click the "-" (minus) button at the bottom of the list to remove the TPM chip, then confirm by clicking "Remove."
6. Start the virtual machine.
7. Shut down the virtual machine completely.
8. Return to "Hardware", click the "+" (plus) button, and select "TPM Chip" to re-add it.
9. Close the configuration window and start the virtual machine again.
For more information, visual guidance, and additional troubleshooting options, please see Fixing the error "The Secure Boot feature prevented the operating system from starting" when launching your Windows 11.
Important note about BitLocker: If your Windows virtual machine uses BitLocker encryption, please ensure you have your BitLocker recovery key readily available before proceeding. After applying either workaround below, Windows may prompt for this key during startup. To locate your recovery key, please see Find your BitLocker recovery key.
Prerequisite: Before making any changes, we recommend creating a snapshot to preserve your current virtual machine state.
Workaround: Remove and re-add the TPM chip
1. Right-click the Parallels Desktop icon in your Mac dock and select "Control Center."
2. Click the gear/cog icon next to your virtual machine.
3. Select "Hardware."
4. Click "TPM Chip" in the left sidebar.
5. Click the "-" (minus) button at the bottom of the list to remove the TPM chip, then confirm by clicking "Remove."
6. Start the virtual machine.
7. Shut down the virtual machine completely.
8. Return to "Hardware", click the "+" (plus) button, and select "TPM Chip" to re-add it.
9. Close the configuration window and start the virtual machine again.
For more information, visual guidance, and additional troubleshooting options, please see Fixing the error "The Secure Boot feature prevented the operating system from starting" when launching your Windows 11.
This does not work as there is no option to "Remove" under the TPM chip.
Here is how I resolved the issue:
Step 1 -- Shut Down the Virtual Machine
In Parallels, go to the top Mac menu bar:
Virtual Machine → Stop
Choose "Shut Down."
Wait until the VM is completely stopped.
Step 2 -- Show the VM in Finder
In Parallels Control Center:
• Right-click the Windows 11 VM
• Choose "Show in Finder"
Step 3 -- Duplicate the VM (Backup)
In Finder:
• Locate the Windows 11.pvm file
• Right-click it
• Choose "Duplicate"
This creates a full backup before making changes.
Step 4 -- Open the VM Package
Right-click the original Windows 11.pvm file and choose:
"Show Package Contents"
Step 5 -- Delete the NVRAM Files
Inside the package contents, move ONLY these files to the Trash:
• NVRAM.dat
• NVRAM.tnvs
DO NOT delete any other files.
Step 6 -- Restart Everything
• Quit Parallels completely
• Restart your Mac
• Open Parallels again
• Start the Windows 11 VM
What This Fix Does
Deleting the NVRAM files forces Parallels to recreate the virtual firmware and Secure Boot security data.
Here is how I resolved the issue:
Step 1 -- Shut Down the Virtual Machine
In Parallels, go to the top Mac menu bar:
Virtual Machine → Stop
Choose "Shut Down."
Wait until the VM is completely stopped.
Step 2 -- Show the VM in Finder
In Parallels Control Center:
• Right-click the Windows 11 VM
• Choose "Show in Finder"
Step 3 -- Duplicate the VM (Backup)
In Finder:
• Locate the Windows 11.pvm file
• Right-click it
• Choose "Duplicate"
This creates a full backup before making changes.
Step 4 -- Open the VM Package
Right-click the original Windows 11.pvm file and choose:
"Show Package Contents"
Step 5 -- Delete the NVRAM Files
Inside the package contents, move ONLY these files to the Trash:
• NVRAM.dat
• NVRAM.tnvs
DO NOT delete any other files.
Step 6 -- Restart Everything
• Quit Parallels completely
• Restart your Mac
• Open Parallels again
• Start the Windows 11 VM
What This Fix Does
Deleting the NVRAM files forces Parallels to recreate the virtual firmware and Secure Boot security data.
Hello, is that safer? I m scared to use it without bit locker key, I don't have it, but I think I didn't do the bit locker key by the first start of the Windows. The Mac was new.This does not work as there is no option to "Remove" under the TPM chip.
Here is how I resolved the issue:
Step 1 -- Shut Down the Virtual Machine
In Parallels, go to the top Mac menu bar:
Virtual Machine → Stop
Choose "Shut Down."
Wait until the VM is completely stopped.
Step 2 -- Show the VM in Finder
In Parallels Control Center:
• Right-click the Windows 11 VM
• Choose "Show in Finder"
Step 3 -- Duplicate the VM (Backup)
In Finder:
• Locate the Windows 11.pvm file
• Right-click it
• Choose "Duplicate"
This creates a full backup before making changes.
Step 4 -- Open the VM Package
Right-click the original Windows 11.pvm file and choose:
"Show Package Contents"
Step 5 -- Delete the NVRAM Files
Inside the package contents, move ONLY these files to the Trash:
• NVRAM.dat
• NVRAM.tnvs
DO NOT delete any other files.
Step 6 -- Restart Everything
• Quit Parallels completely
• Restart your Mac
• Open Parallels again
• Start the Windows 11 VM
What This Fix Does
Deleting the NVRAM files forces Parallels to recreate the virtual firmware and Secure Boot security data.
If you don't know if Bitlocker is enabled and you don't have the key then make a copy of the PVM file first. Also check in you Microsoft Account, maybe you actually have the key backed up there.Hello, is that safer? I m scared to use it without bit locker key, I don't have it, but I think I didn't do the bit locker key by the first start of the Windows. The Mac was new.
Also, after you make the PVM copy, don't use your original VM first, add the copy to Parallels as a new VM and try the TMP chip removal on the VM copy first.
This does not work as there is no option to "Remove" under the TPM chip.
Here is how I resolved the issue:
Step 1 -- Shut Down the Virtual Machine
In Parallels, go to the top Mac menu bar:
Virtual Machine → Stop
Choose "Shut Down."
Wait until the VM is completely stopped.
Step 2 -- Show the VM in Finder
In Parallels Control Center:
• Right-click the Windows 11 VM
• Choose "Show in Finder"
Step 3 -- Duplicate the VM (Backup)
In Finder:
• Locate the Windows 11.pvm file
• Right-click it
• Choose "Duplicate"
This creates a full backup before making changes.
Step 4 -- Open the VM Package
Right-click the original Windows 11.pvm file and choose:
"Show Package Contents"
Step 5 -- Delete the NVRAM Files
Inside the package contents, move ONLY these files to the Trash:
• NVRAM.dat
• NVRAM.tnvs
DO NOT delete any other files.
Step 6 -- Restart Everything
• Quit Parallels completely
• Restart your Mac
• Open Parallels again
• Start the Windows 11 VM
What This Fix Does
Deleting the NVRAM files forces Parallels to recreate the virtual firmware and Secure Boot security data.
There is no button called "Remove", you just select the TPM Chip in the list and click the teeny tiny minus ("-") sign at the bottom of the list. That is standard MacOS UI. Very small and easy to miss.