Most boards give you two doors into the same room: a flasher built into the BIOS, and a utility that runs inside Windows. They write the same firmware - but what can go wrong on the way differs a lot. Here is the honest grading of both routes, and the one route that is never acceptable.
Ask experienced technicians which route they trust and the answer comes fast: flash from inside the BIOS whenever the board offers it. Not because Windows utilities are evil - the makers ship them - but because a firmware write deserves the simplest possible environment, and Windows is the opposite of simple. This page explains what each route actually does, so the preference makes sense instead of sounding like habit.
Every retail motherboard carries a small flashing tool inside its own setup screens. You restart into the BIOS, open the tool, point it at the file on a USB stick, and it verifies and writes - with no operating system, no drivers, no background tasks anywhere near the process. The environment has exactly one job and nothing competing for it.
The maker's Windows tool downloads or accepts the file and flashes after a restart or directly from the desktop. On many laptops and branded desktops it is the ONLY route offered, and used carefully it works - millions of machines are updated this way. Its risks are environmental: it shares the machine with everything else you run.
Many mid-range and better boards add a hardware feature - a dedicated USB port and button (sold under names like BIOS Flashback or Q-Flash Plus) that flashes with the PC powered off and even with no CPU installed. It exists for fitting CPUs the old BIOS cannot recognise, and it doubles as a recovery route. It is a maker feature, not a workaround - where your board has it, it is fully legitimate and covered in the new-CPU and recovery pages of this series.
Third-party 'universal' flashing tools, modded firmware from forums, and any method whose selling point is bypassing the maker's model checks. Those checks are the safety net that refuses wrong files; a tool that removes the net is not advanced, it is dangerous. The same goes for flashing another model's file because 'the boards look similar'. Similar is how boards die.
The video demonstrates the built-in flasher from entering the BIOS to the finished update, step-by-step.
Watch Full VideoManuals usually list both routes; the Windows tool is shown first because it is easier to describe, not because it is safer. If your board has the built-in flasher in its setup screens, using it follows the manual too - it is the maker's own tool. Choose it, and keep the Windows utility for machines that offer nothing else.
The built-in flasher runs inside the BIOS setup and needs a working, booting board with a CPU it recognises. Flashback is a small hardware circuit that writes the firmware with the machine off - no CPU, no RAM, sometimes no successful boot at all. That is why Flashback is the tool for brand-new CPU support and for recovering from some failed flashes.
Almost certainly not - flashing tools use low-level drivers that write to firmware, which is exactly the behaviour security software is trained to distrust. Treat the block as information: the environment is interfering. Rather than fighting the antivirus or whitelisting blindly, restart and use the built-in flasher in the BIOS, where no antivirus exists to argue with.