Quick fix (3 steps)
- Do not press the power button for 15 to 30 minutes if there is any fan or light activity. Keep the charger connected.
- Try your brand's recovery key combination or USB recovery, then a CMOS reset.
- No luck? Save your BitLocker key if you know where it is, stop trying random files, and read when to call a pro.
Should you update the BIOS at all? A decision table
Update the BIOS only when a specific, documented problem or security fix applies to your machine. "A newer version exists" is not a reason. Firmware is the one piece of software that cannot be repaired by reinstalling Windows or macOS. When a normal software update fails, you reboot and retry. When a firmware update fails, the machine may not even show a logo, which is why the risk profile is different from every other update you run.
That said, ignoring firmware forever is also a mistake. Vendors ship BIOS and UEFI updates for CPU microcode, security flaws (including Secure Boot and System Management Mode issues), memory compatibility, battery and charging behaviour, and support for new processors. The right answer depends on what is wrong today. Use this table before you touch anything.
| Your situation | Update? | Why |
|---|---|---|
| Machine works fine, no known problem, release notes mention only "improved stability" | No, wait | Nothing to gain, small but real risk. Revisit in a few months. |
| Vendor security advisory names your model and the fix is in the new BIOS | Yes, plan it properly | Firmware flaws live below the operating system, antivirus cannot see them. |
| New CPU you are installing is listed as needing a minimum BIOS version (desktop) | Yes, before swapping the CPU | Without it the board may not post. Use BIOS Flashback if the board has it. |
| Laptop battery drains in sleep, fans spin at full speed, or the dock fails, and the release notes mention exactly that | Yes, after a backup | This is the classic case where a BIOS fix really helps. |
| Windows 11 upgrade blocked on "TPM or Secure Boot not available" | Maybe, check settings first | Often it is only a setting (fTPM, PTT, Secure Boot) and not a missing version. See the section on settings below. |
| You are 2 or more versions behind and the vendor says "update sequentially" | Follow the vendor order | Some models require an intermediate version. Skipping can fail the flash. |
| You are in a thunderstorm area with an unstable grid, or on a laptop with a swollen or dead battery | No, fix power first | Power loss during the write is the number one cause of bricked boards. |
| Machine is under a business warranty or managed by an IT department | Ask IT first | Fleet tools (Dell Command, HP Image Assistant, Lenovo Vantage and similar) update safely and keep records. |
The three questions that settle it
- Can I name the problem this update fixes? Read the release notes on the vendor support page for your exact model and service tag or serial number. If you cannot match a line in the notes to something you live with, skip it.
- Can I afford to lose this machine for a week? If the answer is no (work laptop, thesis, accounting machine), do the update only when you have a backup and a recovery path from the list in this guide.
- Is the power rock solid? A laptop at 80 percent and plugged in beats a desktop on a flickering wall socket without a UPS.
Myth: "BIOS updates make the computer faster"
Almost never. A BIOS update can fix a bug or add compatibility. It will not raise benchmark scores in a way you notice. The occasional exception is a microcode update that fixes a CPU boost or power-limit bug on one specific model, and the release notes say so in plain words.
How a BIOS update actually bricks a machine
A BIOS lives on a small flash chip (usually 8 to 32 MB, soldered to the board) that the processor reads at the very first moment of boot. An update erases sectors of that chip and writes new code. If the write is interrupted or the image is wrong, the first instructions the CPU fetches are garbage, and the machine cannot start the code that would let it fix itself. Nothing is physically broken, the chip simply holds unusable data. That is why firmware "bricks" are often fully recoverable, as long as someone can write the chip again.
| Cause | What happens | How common | Prevention |
|---|---|---|---|
| Power loss or battery cut-off during the write | Half-erased flash, no POST | Most common | AC adapter plugged in, battery above the vendor minimum, UPS on desktops |
| Wrong file (other model, other board revision) | Valid file, wrong hardware, no POST | Common on desktop boards | Match the exact model and revision printed on the board |
| User force-shuts the machine because the screen is black "for too long" | Interrupts the flash | Very common | Wait. Many updates take 5 to 15 minutes with several reboots and a blank screen |
| Corrupted or partial download, or an unsigned or modified image | Verification fails, or flash corrupts | Occasional | Download from the vendor only, check size or hash when given |
| Flashing from inside a Windows session with security software or sleep interfering | Update tool is killed mid-write | Occasional | Close apps, disable sleep, pause nothing critical, let the tool finish |
| Failing flash chip, bad battery or bad board | Update fails at a random point | Rare | Do not update a machine that is already unstable |
What a normal update looks like (so you do not panic)
On most laptops, after you start the update from Windows, the machine restarts, shows a vendor logo or a progress bar, may go black for a few minutes, fans may run at maximum, the power light may blink, it may restart once or twice more, and then Windows loads. Dell, HP and Lenovo all warn against interrupting this. The practical rule: if there is any sign of life (fan, LED, disk light, a beep pattern), give it a full 15 minutes before doing anything. If after 20 to 30 minutes there is no change, move to the symptom table further down.
Before you flash: the 10-minute safety routine
Ten minutes of preparation removes most of the risk. The routine below applies to every brand. Do not skip the backup step: firmware does not touch your files, but a failed update can leave you with a machine that needs a lab visit, and storage encryption can make that visit harder than it needs to be.
Pre-flash checklist (print or copy)
- ☐ Exact model and revision written down (service tag on Dell, product number on HP, machine type on Lenovo, board revision on desktop boards)
- ☐ Current BIOS version noted (Windows: run
msinfo32, line "BIOS Version/Date") - ☐ Release notes read, and the fix you want is listed
- ☐ Backup of important files done, and verified by opening one file from the backup
- ☐ BitLocker or device encryption recovery key saved somewhere other than this computer (Microsoft account page, printout, or USB)
- ☐ Laptop plugged into its original charger, battery at 50 percent or more (Dell asks for 25 percent minimum for recovery, vendors vary)
- ☐ Desktop on a UPS, or at minimum a stable outlet, nobody tripping on the cable
- ☐ Update file downloaded from the vendor support page only, not from a "driver site"
- ☐ USB stick (FAT32, 8 to 32 GB) ready in case you need a recovery file
- ☐ No other updates or installs running, sleep and hibernate disabled for the duration
- ☐ Time set aside: 30 minutes with no interruptions
Why the BitLocker key matters here
Windows 11 on many new laptops turns on device encryption automatically. When firmware changes, the TPM measurements change, and Windows can ask for the recovery key at the next boot. That prompt is normal after a BIOS update, but if you cannot find the 48-digit key you are locked out of your own files. Check your Microsoft account recovery key page (or your work or school account) before you update. Our guide on data recovery versus data backup explains why a backup copy is the only real safety net.
Suspend BitLocker first when the vendor tells you to
Some vendors tell you to suspend BitLocker before the update, and some tools do it automatically. Suspending is not decryption: it pauses protection for the next restart only. If your vendor's instructions mention it, follow them. If they do not, still have the recovery key ready.
Safer ways to update than "downloading an .exe and running it"
Prefer the vendor's own updater, or the update path inside the BIOS setup screen, over third-party tools. The ranking below is from safest to riskiest for a typical user.
| Method | Risk | Notes |
|---|---|---|
| Windows Update or LVFS/fwupd on Linux (firmware delivered as a system update) | Low | Vendor-signed capsule updates. Many Dell, HP and Lenovo business laptops use this. Keep the laptop plugged in. |
| Vendor utility (Dell Command Update, HP Support Assistant or Image Assistant, Lenovo Vantage or System Update) | Low | Checks model, battery and AC before flashing. |
| Standalone vendor .exe run from Windows | Low to medium | Fine on laptops with the AC connected. Close everything else first. |
| Flashing from inside the BIOS setup (Dell one-time boot flash, ASUS EZ Flash, MSI M-Flash, Gigabyte Q-Flash) | Low to medium | Runs without Windows in the way. Needs the file on a FAT32 USB. |
| BIOS Flashback or Q-Flash Plus with no CPU installed | Low, by design | Dedicated controller flashes the chip. See the recovery section. |
| Third-party flash tools, modified BIOS images, "unlocked" BIOS for hidden options | High | Not for anyone who cannot reflash the chip with a programmer. |
Step by step: a safe update on a typical Windows laptop
- Find your exact model: press the Windows key, type
System Information, note "System Model" and "BIOS Version/Date". - Go to the support page of the manufacturer (not a search result ad), enter your serial or service tag, and open the BIOS or firmware category.
- Compare the listed version with yours. Read the notes. Note any "must update from version X first" line.
- Plug in the original charger. Save and close all documents. Disable sleep: Settings, System, Power, set screen and sleep to "Never" temporarily.
- Run the installer. Accept the restart prompt. Do not touch the keyboard, close the lid, or unplug anything.
- Wait at least 15 minutes if the screen stays black. Watch for fan noise or LED activity.
- When Windows loads, re-enter BIOS setup (usually F2, F10, Del or Enter then F1 on Lenovo) and check that your boot mode (UEFI), Secure Boot and storage mode (AHCI) are as before. Updates can reset settings to default.
- Restore your sleep settings and note the new version in a text file for next time.
What not to do
- Do not update on battery alone, even at 100 percent.
- Do not update on a machine that has been randomly shutting off, freezing or showing disk errors: fix that first.
- Do not update from a Windows installation that is crashing, or inside a virtual machine.
- Do not run two firmware updates back to back (BIOS plus embedded controller plus Thunderbolt) without letting each finish and reboot.
- Do not press the power button because "nothing is happening".
Boot failure symptom table: is it the firmware or something else?
A dead-looking machine after an update is not always a bad flash. Many "bricked" cases are a drained battery, a reset setting or a display that needs a nudge. Match what you see below, then follow the first action. The tests are ordered from free and safe to specialist.
| What you see | Most likely cause | First action | Firmware suspected? |
|---|---|---|---|
| Update running, black screen, fan on, LED blinking, under 20 minutes | Normal update in progress | Wait. Do not touch. | No |
| Black screen for 30+ minutes, fan stuck at max speed, no logo | Interrupted or failed flash | Try the vendor recovery key combo (next section) | Yes |
| Power light on, fans spin once then stop, repeats | Boot loop from failed POST | Hard reset: unplug, hold power 30 seconds, then CMOS reset | Possible |
| Beep codes or blinking LED pattern (count them) | Memory, CPU or BIOS fault, depending on the vendor's table | Look up the pattern in the manual for your model, reseat RAM | Possible |
| Machine starts, logo shows, then "No bootable device" | Boot order or storage mode reset to default, or a real disk problem | Enter setup, check boot order and SATA/NVMe mode | Setting, not a brick |
| Machine boots, but asks for the BitLocker recovery key | Firmware changed the TPM measurement | Enter the key, then let Windows reseal | No, expected |
| Screen shows "BIOS recovery" or "BIOS corrupted" message | Self-healing triggered | Follow the on-screen steps, AC connected | Yes, and it is working |
| CMOS checksum error, wrong date and time on each boot | Dead CMOS (coin) battery | Replace the CR2032 battery | No |
| No power at all, no LED even with a known good charger | Charger, DC jack, battery or board power fault | Test another charger. See our laptop not charging guide | Unlikely |
| Power on, fans spin, but external monitor works and the laptop panel stays dark | Display or cable problem | Connect an external monitor and see the laptop black screen guide | No |
| Machine worked before a liquid spill, then died | Board damage from liquid | Power down, do not retry. See our water-damaged laptop guide | No |
A 5-minute decision tree
- Any sign of life at all? No: test the charger and outlet, then stop and go to "When to call a pro". Yes: continue.
- Did a firmware update run in the last hour? No: this is probably not firmware, read the Windows boot after update guide. Yes: continue.
- Did it show a recovery or corruption message? Yes: let it finish. No: continue.
- Do the vendor recovery keys do anything (new screen, fan change, USB light)? Yes: you are in recovery, prepare the USB. No: continue.
- Did a CMOS reset (below) change the behaviour? Yes: go to setup, reapply settings. No: the flash chip likely needs rewriting, which is a bench job.
CMOS reset: the free first step that fixes more than you expect
A CMOS reset clears the stored settings (boot order, overclock, memory profile, Secure Boot keys) back to defaults. It does not erase the BIOS code itself. That makes it safe, and often enough to revive a machine that fails to post after an update left a broken setting behind.
Desktop
- Shut down and unplug the power cable. Switch off the power supply at the back.
- Hold the case power button for 10 seconds to drain residual power.
- Remove the flat CR2032 battery from the board for 5 minutes (or use the CLR_CMOS jumper or button as in the board manual).
- Put the battery back with the plus side up, plug in, boot, and enter setup to set date, boot order and any needed options.
Laptop
Laptops vary. Some have a small CMOS reset pinhole, some require disconnecting the internal battery connector, and some (many thin models) have no user-accessible reset and rely on a key-combo power drain: unplug the charger, remove the battery if it is user-removable, hold the power button 30 seconds, then reconnect and try. Opening a laptop may void a warranty or be risky on glued battery models. If you are unsure, stop at the power drain.
Do not confuse the two kinds of battery
The coin-cell CMOS battery keeps the clock and settings. It is not the main laptop battery. A dead coin cell causes date resets and "CMOS checksum" errors, and it costs a few dollars. A swollen main battery is a safety issue: stop using the laptop and have it handled professionally.
Recovery paths by brand: what the machine can do to save itself
Most modern machines can restore their own BIOS from a backup copy or a USB stick, if you trigger the right mode. The key combos below come from vendor documentation. Always read the page for your exact model first, because laptops differ even inside one brand.
| Brand | Trigger | Needs | Notes |
|---|---|---|---|
| Dell (systems from about December 2015, Intel 6th gen or newer) | Hold Ctrl + Esc at power on. On laptops, unplug the AC first, hold the keys, then plug the AC back in. | Self-healing from the on-disk backup, or a USB with the file named exactly BIOS_IMG.rcv in the root, FAT32. Laptop battery at 25 percent or more, AC connected. | Desktops need a wired USB keyboard. Laptops must use the built-in keyboard. Do not power off during recovery. |
| HP (many models) | With the machine off, hold Windows + B, press and hold power for about 3 seconds, release power but keep the keys until you hear a beep or see the update screen. | Emergency recovery from a copy kept on the drive, or a recovery file on USB depending on model. | Some models use Windows + V for a different recovery mode. Check HP's page for your model. |
| Lenovo (ThinkPad and IdeaPad vary a lot) | Often Fn + R held while pressing power on some models. ThinkPads may recover from a flash image on USB using a vendor-supplied recovery ISO. Others use a pinhole reset. | Model-specific recovery package from Lenovo support, USB stick. | Procedure differs between models, and forum posts for older machines do not apply to newer ones. Use Lenovo's own page. |
| ASUS desktop boards | USB BIOS FlashBack: file renamed per ASUS rules, placed on a FAT32 USB in the marked port, hold the dedicated button for about 3 seconds until the LED flashes. | PSU powered, no CPU or RAM needed. | Use the exact filename from the manual. LED behaviour tells you progress and success. |
| MSI desktop boards | Flash BIOS Button with file renamed to MSI.ROM on the marked port. | PSU powered, no CPU needed. | Not all models. Check the manual. |
| Gigabyte boards | Q-Flash Plus button with the file renamed per manual. Many boards also have Dual BIOS with a backup chip that takes over on failure. | PSU powered. | Dual BIOS can auto-recover, but a bad update can sometimes overwrite both. |
| Other brands and older machines | Check the manual for "BIOS recovery", "crash free", "boot block" or "emergency recovery". | Varies. | If no mode exists, the chip needs an external programmer. |
Features worth knowing by name
- Dual BIOS: two chips on the board, one main and one backup. If the main one fails its check, the board boots from the backup and offers to repair the first. Common on Gigabyte and some other desktop boards.
- BIOS Flashback / Q-Flash Plus / Flash BIOS Button: a small controller that writes the chip from a USB file with no CPU, memory or graphics card installed. It is the best tool when a new CPU needs a newer BIOS.
- Crash Free BIOS (ASUS): a boot block that looks for a recovery file on USB or an optical drive when the main image is damaged.
- Self-healing and A/B images: many business laptops store a golden copy of the firmware and restore it automatically at the next start.
Making the USB stick correctly
- Use a plain USB 2.0 or 3.0 stick of 8 to 32 GB. Large sticks may need FAT32 formatting by command line: in PowerShell,
format /FS:FAT32 X:where X is the stick letter (this erases the stick). - Download the BIOS from the vendor, extract it if it is an archive, and rename it exactly as the vendor says (Dell uses uppercase
BIOS_IMG.rcv). - Copy it to the root of the stick, not in a folder.
- Eject properly, plug the stick into the port the manual specifies (desktop Flashback features use one specific port), and trigger the recovery.
- Do not touch the machine until the recovery finishes: fans calm down and the screen returns or the machine restarts by itself.
Mac firmware: revive and restore with Apple Configurator
Macs do not have a user-flashable BIOS. Apple silicon and T2 Macs have firmware that Apple can reinstall through DFU mode from a second Mac using Apple Configurator. According to Apple's support page, this applies only to Macs with Apple silicon or the Apple T2 security chip. Older Intel Macs without T2 have a different recovery path (the firmware password or internet recovery routes) and do not use DFU.
What you need
- A second, working Mac with Apple Configurator installed (free from the Mac App Store) and a recent macOS.
- A USB-C to USB-C cable that supports data and charging. Apple says to avoid Thunderbolt 3 cables for this.
- The correct DFU port on the dead Mac. Apple publishes a guide to which port to use per model.
- An internet connection for the host Mac.
Revive first, restore only if revive fails
| Action | What it does | Data | When to use |
|---|---|---|---|
| Revive | Reinstalls the firmware and recovery environment | Does not erase your Mac, per Apple | First attempt, always |
| Restore | Erases the Mac and installs a fresh macOS | Everything on the internal storage is erased | Only if revive fails and you have a backup, or accept the loss |
Entering DFU mode (from Apple's instructions)
- Apple silicon laptops: connect to the host Mac, press the power button, then hold left Control, left Option and right Shift together with Power for about 10 seconds. Release all except Power and keep holding Power for up to 10 more seconds.
- T2 laptops: same combination, but the four keys are held for about 3 seconds.
- Desktops: unplug power, hold the power button, plug in while still holding, hold for up to 10 seconds.
When the target Mac appears in Apple Configurator as "DFU", choose Revive. If the revive fails repeatedly, Restore is the next step. Because Apple silicon storage is encrypted and tied to the chip, a restore means your local data is gone, so a Time Machine or cloud backup is what saves you. Read our data recovery versus backup guide and the Mac sleep and wake guide if the Mac is merely misbehaving and not dead.

When the machine has no recovery mode: SPI programmer reflash (lab-level)
If no key combo, Flashback button or USB recovery works, the last resort is writing a clean firmware image straight onto the flash chip with an SPI programmer. This is a bench procedure done by specialists, and it is guidance and referral territory, not something IT Cares performs. We explain it so you can judge a quote and recognise an honest shop.
How the job is done
- The technician opens the machine and locates the SPI flash chip (an 8-pin chip, often labelled with a 25-series number).
- A test clip (SOIC8 clip) is attached to the chip, or the chip is removed with hot air if the clip cannot reach it.
- A programmer (CH341A class budget tools, or professional units) reads the existing content first. A backup of the dead image is kept.
- A clean image for the exact model is written, verified by reading it back, and in many laptops the Intel Management Engine region or the machine's serial and licence data must be preserved or rebuilt.
- The board is tested, then reassembled. If the chip itself has failed, it is replaced.
Why a casual attempt goes wrong
- Writing 3.3 V logic to a chip that runs at 1.8 V can destroy the chip and sometimes the board. Many modern laptops use 1.8 V flash and need an adapter.
- Clips can back-power the board. The battery and charger must be disconnected.
- Generic images erase the machine's unique data (serial number, UUID, Windows licence or OEM flags, network MAC). The machine may boot, but with missing features.
- Some systems with locked platform security (Intel Boot Guard, AMD firmware protection, vendor signing) will refuse or fail to boot an image that was not prepared for them.
| Option | Typical result | Rough cost in CAD (estimate) | Who |
|---|---|---|---|
| Self-healing, USB recovery or Flashback | Works if the machine supports it | 0 to 25 (USB stick) | You |
| Diagnostic with an independent shop | Confirms or rules out firmware | 40 to 120 | Shop or technician |
| SPI reflash at a specialist bench | High success rate on supported boards | 100 to 300 for the job in many shops, more if parts are needed | Specialist |
| Flash chip replacement and programming | Needed when the chip is dead | 200 to 450 | Specialist |
| Motherboard replacement (laptop) | Works, expensive, data may or may not remain | 350 to 1,000 and up, model dependent | Brand service or shop |
| Desktop motherboard replacement | Simple and often cheaper than diagnosis | 110 to 400 for the board, plus labour | You or a shop |
All amounts are IT Cares estimates for typical Canadian independent shops in 2026 and not published price lists. Quotes vary by model, parts availability and workload. Ask for a written, itemised quote that separates diagnostic fee, labour, parts and tax (TPS and TVQ in Quebec).
What it costs: do it yourself versus paying a technician
Most firmware problems cost nothing or very little if you act in the right order. The expensive path is making the situation worse before asking for help, for example repeated forced power-offs, opening a glued laptop, or trying a random BIOS file.
| Scenario | DIY cost | Pro cost (estimate, CAD) | Verdict |
|---|---|---|---|
| Reset after a failed setting or CMOS checksum error | 0 to 8 (coin cell) | 40 to 80 | Do it yourself |
| Dell or HP laptop with built-in recovery and a copy of the BIOS | 0 to 20 (USB) | 60 to 120 (diagnostic) | Try yourself once, then call |
| Desktop board with Flashback or Dual BIOS | 0 to 20 | 60 to 150 | Do it yourself carefully |
| Laptop with no recovery mode, dead after a flash | 50 to 150 for a programmer and clip, high risk | 100 to 450 | Send out |
| Apple silicon Mac dead after macOS or firmware update | 0 with a second Mac and a cable | Apple or an authorised service quote, varies | Try revive yourself first |
| Machine still under warranty or business support | 0 | 0 to a fee, vendor | Use the warranty |
Three realistic scenarios
Realistic scenario 1 (illustrative): a Dell Latitude after a Windows Update firmware capsule. A bookkeeper in Laval starts a laptop update and the machine reboots into a black screen with the fan at full speed. After 12 minutes she gets worried and nearly holds the power button. A relative reminds her to wait. At minute 17 the update screen appears, the laptop restarts, and Windows loads. Total cost: zero dollars, 20 minutes. The lesson: the black screen was normal. If it had stayed black past 30 minutes, her next step would have been Ctrl + Esc on the built-in keyboard with the AC reconnected.
Realistic scenario 2 (illustrative): a desktop board and a new CPU. A student in Gatineau buys a newer processor for his existing board. The board's release notes state a minimum BIOS version for that processor. He has no old CPU to boot. His board has a Flashback button, so he downloads the exact file, renames it, uses a FAT32 stick in the marked port, and waits for the LED to stop blinking. The board then posts with the new CPU. Cost: a USB stick he already owned. The lesson: check the CPU support list before buying, and use the flashback feature when it exists.
Realistic scenario 3 (illustrative): a thin laptop with no recovery mode. A small-business owner in Sherbrooke cancels an update by closing the lid. The laptop never shows a logo again. The Win+B and Fn combos do nothing, the CMOS drain changes nothing, and the vendor lists no USB recovery for that model. A specialist bench reads the chip, finds a damaged image, writes a clean one and preserves the serial data. The quote in this example is 180 dollars CAD and 5 days. The lesson: stop after the free steps, and do not buy a clip and try it on a board whose voltage you do not know. If the machine holds the only copy of your accounting files, mention that when you book, so the specialist knows that data preservation comes first.
Data safety: what firmware failures do and do not do to your files
A BIOS or UEFI failure does not erase your files. It stops the machine from reaching them. The drive is usually intact. The real risks are accidental data loss from the wrong "fix" (reinstalling Windows, formatting, a macOS Restore) and encryption that makes the drive unreadable without the key.
- Windows with BitLocker or device encryption: without the recovery key or a working TPM, the drive cannot be unlocked on another computer. Save the key before any firmware work.
- Apple silicon and T2 Macs: internal storage is encrypted and tied to the machine. A dead logic board can mean unreadable data, and a DFU Restore erases the Mac.
- Older unencrypted PCs: the SSD or hard drive can often be read in another computer or a USB enclosure. See SSD versus HDD recovery difficulty and data recovery in Canada.
If the machine holds files you cannot replace, stop and talk to a technician before trying more than the free steps in this guide. For costs, our data recovery cost guide lists what to expect.
Often it is a setting, not a new version: TPM, Secure Boot and boot mode
Many people update the BIOS to fix a Windows 11 or boot problem that only needed a setting changed. Before you flash, check the following in the setup screen.
| Symptom | Setting to check | Where it hides |
|---|---|---|
| Windows 11 says TPM 2.0 not found | Intel PTT or AMD fTPM | Security or Advanced, often under "Trusted Computing" |
| Secure Boot not enabled | Secure Boot toggle and boot mode must be UEFI, not Legacy/CSM | Boot or Security tab |
| Drive not detected after the update | SATA mode (AHCI versus RAID/Intel RST) | Storage or Advanced. Changing it on an installed Windows can prevent boot, note the original value first. |
| USB stick will not boot | Boot order, USB boot support, Secure Boot signature | Boot menu (F12, Esc or F9 depending on brand) |
| Memory runs at wrong speed or the machine will not post with new RAM | XMP or EXPO profile, memory frequency | Overclocking or Tweaker tab. Reset with CMOS clear if posting fails. |
Our Windows 11 blue screen guide covers the software side if the machine boots but crashes after a firmware change.
Myths about BIOS and firmware, corrected
- "A failed BIOS update means the motherboard is dead." Usually false. The chip holds bad data, the hardware is fine. A rewrite of the chip often brings the board back.
- "Resetting the BIOS means losing my files." False. Settings reset, files stay.
- "Removing the CMOS battery wipes the BIOS." False. It clears settings in the volatile memory. The firmware itself sits in non-volatile flash.
- "Newer is always safer." False. A bad release does occasionally appear. Wait a week and read the vendor page and user reports if the release is brand new.
- "Any USB stick works." False. Format, filename, root folder and port can all matter.
- "A black screen after 5 minutes means it failed." False. Updates can take longer, with several restarts.
- "A Mac can always be restored from DFU." It can be reinstalled, but Restore erases data and a hardware fault will still fail. Revive does not erase, so try it first.
When to call a pro
Stop and get help when the free steps fail, when you are not sure about the model, or when the data matters. The line is simple: you can do the vendor recovery key, a USB recovery, a CMOS reset on a desktop and a Mac revive. You should not do chip-off or SPI work without the right voltage tools, and you should not open a glued laptop for fun.
- You tried the vendor key combo and the CMOS reset, and nothing changed.
- The machine holds the only copy of important files and is encrypted.
- You smell burning, see swelling or feel heat from a battery: power off and call.
- The machine is under warranty (opening it can void it).
- You are not sure which BIOS file matches your board revision.
IT Cares offers remote diagnosis, guidance on recovery steps, data-safety advice and on-site visits in Quebec since 2014. We do not do board-level soldering or SPI chip reflash ourselves. If your machine needs that, we explain what the work involves, help you compare quotes and point you to Apple, the manufacturer or a trusted specialist. You can book a remote session or call 1 (888) 711-9428. For general PC problems, see our computer repair page.
Official resources
- Apple Support: How to revive or restore Mac firmware
- Dell Support: Recover the BIOS after boot or POST failure
- Lenovo Support (search by machine type for BIOS recovery)
- HP Support (search by product number for BIOS recovery)
- Office de la protection du consommateur du Québec (warranty and repair rights)
Still stuck? Get a technician on it now
Remote support from IT Cares: we connect to your device, fix it with you watching, and explain what happened.
Frequently asked questions
Related guides
- Windows won't boot after an update: fix
- Laptop black screen fix
- Laptop not charging fix
- Water-damaged laptop data recovery guide
- Data recovery vs data backup
- Data recovery cost in Canada 2026
- SSD vs HDD data recovery difficulty
- Fix blue screen in Windows 11
- Mac won't wake from sleep: fix
- Intel Mac vs Apple silicon in 2026
- Computer repair
- Data recovery in Canada
Sources and official references
Last verified: October 4, 2026
- Apple Support: How to revive or restore Mac firmware (opened 2026-10-04)
- Dell Support: Recover the BIOS on a Dell computer or tablet (opened 2026-10-04)
- Apple Support: Revive or restore a Mac with Apple silicon using Apple Configurator (search result, not opened)
- ASUS: How to use USB BIOS FlashBack (search result, not opened)
- Lenovo Support
- HP Support
- Office de la protection du consommateur du Québec
