Recently, a scary rumor has been circulating among PC builders and gamers that "the old Secure Boot certificate (Microsoft Corporation UEFI CA 2011) will expire in June 2026, causing PCs to stop booting due to graphics cards."
We have been conducting verification on this blog, and after extracting the VBIOS of the "RTX 3060" that I use and performing binary analysis, we discovered that the rumored old certificate was being used.
"If this continues, will my PC not be able to start up in 2026?"
To clarify this question,I contacted Microsoft directly through their official support chat to find out the truth.
In conclusion,RTX 3060 users, rest assured. However, those using some older graphics cards, especially the early GTX 16 series, should be very careful.
Summary of answers from Microsoft Support (quick reference)
I have compiled a table showing the "impact of each graphics card generation" that I discovered during my lengthy discussion with the support staff.
| Item | A modern GPU (such as an RTX 3060) | Older GPUs (GTX 600 to early GTX 16, etc.) |
| Launch date: June 2026 or later | Can be started without any problems | Secure Boot initialization may fail |
| Worst-case scenario | No impact | Black screen before BIOS and completely unbootable |
| Effects of the NVIDIA DisplayPort 1.3/1.4 Firmware Update Tool | (Not applicable or not affected) | Invalid(UEFI GOP and signatures are not updated at all) |
| Future measures | No need to replace or change anything | Check with the manufacturer for firmware updates, or consider replacing the device. |
Three key facts revealed
We'll explain the specific technical answers we received from Microsoft support professionals.
1. The RTX 3060 won't become "unbootable"
In response to my most concerning question, "Will RTX 3060s with old certificates become bricked in 2026?", support gave me a clear, safe response: "No, your RTX 3060 will not become unbootable," and "Your RTX 3060 is not included in that group, so there is no need to replace anything."
The catastrophic Secure Boot violation scenario only applies to "certain older NVIDIA GPUs," as described below.
Additionally, a reader reported (March 6, 2026) that Microsoft support has responded that the Palit RTX 3050 6GB, released in February 2024, is not affected by Microsoft UEFI CA 2023 and does not require verification.
2. The real danger lies in the "GTX 600 to early GTX 16 series"
After 2026, cards that Microsoft classifies as "older NVIDIA GPUs" are at serious risk of experiencing a black screen and other "boot failure" issues. According to a support response, specifically: GTX 600 series to early GTX 16 series falls into this category.
It makes sense that the 10 series, including the GTX 600, 900, and the famous GTX 1060, are included, but the most important thing to be wary of here is"The initial lot of the GTX 16 series" is also included.The GTX 16 series (GTX 1650, 1660, 1660 Ti, 1660 SUPER, etc.) was released around 2019 and is a huge hit model with many active users, still ranking highly in Steam's hardware survey.
At this point, one question may arise: "My RTX 3060 also has an internal signature from 2011, so why is it safe?"
According to Microsoft, "modern GPUs" like the RTX 3060 are exceptionally protected (no replacement required) because of their new hardware design. However, the GTX 16 series, "products manufactured at the beginning of its release," still use the old firmware (UEFI GOP) from that time, and therefore fall outside the scope of this new protection.
Late-production models and those with VBIOS fixes already applied by the manufacturer may be safe. However, for those who bought early models immediately after release and have continued to use them, unless the manufacturer provides new firmware, they run the risk of losing access to the BIOS in June 2026 due to a Secure Boot violation.
It is important to note that there are cases where manufacturers explain that "old certificates will continue to be recognized, so it's okay," but this does not include the pitfall of "registration to the DBX (ban list)."
In addition to the list of allowed signatures (DB), Secure Boot also has a forbidden list (DBX) that clearly states, "This signature will no longer be trusted." The real horror of the update scheduled for 2026 is that Microsoft will forcefully update this DBX through Windows Update.
Even if the signature inside the graphics card is technically "valid," once that signature (Microsoft Corporation UEFI CA 2011) itself is registered in DBX, the PC's boot process (UEFI) will immediately block it as an "invalid device."
In other words, the following worst-case scenario becomes a reality:
- Windows Update will be performed: The DBX (ban list) in the PC will be updated.
- Reboot: UEFI checks the GPU signature but rejects it because it is registered in DBX.
- Video output stops: The GPU firmware (GOP) does not work, and the screen turns completely black, with not even the BIOS screen displayed.
Even if the manufacturer says it will continue to recognize the device, if Microsoft, which controls the OS, decides to reject it with DBX, early lots of devices such as the GTX 16 series, which rely on old signatures, run the risk of being physically unable to boot (becoming bricked).
If the manufacturer does not provide a workaround VBIOS and you are faced with a black screen when updating in 2026, there is only one last resort.
The option is to disable Secure Boot, completely disconnect the PC from the network, and continue using it in a "standalone (offline)" environment.
If you turn off Secure Boot, the UEFI (BIOS) will skip the DBX (ban list) check, and even the GPU that was supposed to be rejected will be able to display the screen again. However, this means that you are throwing away the fundamental protection of the OS, which means that you will be vulnerable to viruses and rootkits.
Therefore, if you take this measure, the golden rule is to cut off all internet connections and use it as a "dedicated machine that is out of the reach of external threats." "Use your beloved old hardware until it physically breaks, regardless of the lifespan of the OS or changes in Microsoft policy." This is literally the last and strongest self-defense measure available to users who have been abandoned by the manufacturer.
3. The official "DisplayPort 1.3/1.4 Firmware Update Tool" is not a solution
If you wonder if you can update the firmware of your old graphics card, and search for "GTX 1060 UEFI firmware update" or "NVIDIA BIOS not displaying update" on Google, you will find the official "DisplayPort 1.3/1.4 Firmware Update ToolYou should find a page titled "
However, when I asked Microsoft directly, they completely dismissed the issue, saying, "No, this tool only updates the DP firmware and does not change the Secure Boot certificate signature." In other words, even if using this tool appears to temporarily fix the screen problem, it does not fundamentally solve the 2026 problem (updating the digital signature), and it cannot prevent Secure Boot violations.
What people with old graphics cards should do now
If you or someone you know is using a graphics card such as the GTX 1060 or the original GTX 1660, will they have no choice but to buy a new PC by 2026?
According to the support response, it is not necessarily necessary to immediately purchase a new one.The best way to check compatibility is to check with your PC or motherboard manufacturer."It seems that
If your graphics card manufacturer (such as ASUS or MSI) or your build-to-order PC manufacturer provides a firmware update that includes the new certificate for your system, you can survive by applying it.
However, if the manufacturer's support has already ended and you are unable to update the firmware, you will be forced to choose between turning off Secure Boot to lower security or replacing your graphics card by June 2026.
Here, please note thatThe option to "turn off Secure Boot" comes with a significant cost (risk) that goes beyond simply reducing security.Specifically, the following three fatal problems may occur:
- Popular games become unplayable Powerful anti-cheat systems (such as Riot Vanguard) used in games like VALORANT and League of Legends require Secure Boot to be enabled in a Windows 11 environment. The moment you turn it off, these games will not launch at all, which is a real blow to gamers.
- Excluding Windows 11 system requirements Enabling Secure Boot is a mandatory requirement for Windows 11. If you continue to operate with it disabled, it may cause problems with the OS, such as preventing future major updates (24H2, 25H2, etc.) from being applied properly or displaying a warning watermark on the screen.
- Become a target for malicious malware You will lose your strongest defense against "bootkits" and "rootkits," viruses that infect before the OS boots and are extremely difficult to remove.
In other words, the solution of "extending life by turning off Secure Boot" is not available in the modern PC environment.It's not a realistic optionIf you are unable to get an update from the manufacturer, the safest and most reliable solution would be to simply replace your graphics card.
[Risks of turning off Secure Boot]
What is a rootkit?
It means a "kit (toolbox)" for seizing "root (root = administrator privileges)."
- What to do?: It penetrates deep into the core of the system (kernel, etc.)"Invisible" and conceal the presence of yourself and other viruses international success.
- Specific damage:
- It creates a "backdoor" that allows hackers to break into your PC at any time.
- Secretly steals passwords and credit card information as you enter them (keylogger).
- It bypasses or disables the detection of normal antivirus software (such as Windows Defender).
What is a Bootkit?
This is a more vicious "evolution" of rootkits. As the name "Boot" suggests,Before Windows (OS) starts upand it starts moving.
- What to do?: It infects the motherboard firmware (UEFI/BIOS) and the boot area of the hard disk.
- Specific damage:
- Boot before the OS: It takes over the system before Windows or antivirus software wakes up, fooling the security software into thinking that "everything is normal" and leaving the infection completely unaware.
- Reinstalling the OS doesn't fix it: Even if you format (initialize) the C drive containing Windows and reinstall the OS, the virus will reappear because it has infected the motherboard or other parts.
Why do we need "Secure Boot"?
Secure Boot is the most powerful gatekeeper that Microsoft has developed to prevent infection by this boot kit at the very border.
If Secure Boot is turned on, it checks at startup, asking, "Do you have a legitimate signature (identification)?" and blocks the startup of mysterious programs (bootkits) that do not have a signature.
In other words, to continue using your old graphics cardTurning off Secure Boot is like firing the gatekeeper and opening the door wide to the most vicious viruses.
Summary
This direct interview with Microsoft provided a clear answer to the vague concerns on the Internet.
- RTX 30 Series and later users: You can continue to use it with confidence.
- For GTX 16 series and earlier users: Check the support page of your PC/graphics card manufacturer to see if there are any firmware updates (especially if you are using the early lot GTX 16 series).
There are only a few months left until the June 2026 deadline.
We hope that the answer from support this time will be of some help to you. Please check your PC environment and manufacturer's support status now so that you don't panic in an emergency.
