Asus VivoBook Backlight Not Working: What's Actually Different Between the 15, 16, and 17 Inch Models

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your VivoBook backlight is almost certainly disabled at the firmware level, not broken at the hardware level. Asus ships several VivoBook SKUs with the backlight defaulting to off after every cold boot, controlled by an ASUS System Control Interface driver that Windows Update routinely overwrites with a generic HID version that drops that functionality entirely. On the hardware side, the backlight circuit runs off a dedicated PWM line from the embedded controller; if that EC firmware is mismatched with the BIOS version, the PWM signal never fires even when the OS thinks it has toggled the light.

Model Differences That Actually Affect Backlight Behavior

Not every VivoBook has a backlit keyboard. This is the first thing to confirm before spending time on software fixes. The presence of a backlight depends on the exact SKU suffix, not just the screen size.

Series Common SKUs With Backlight Common SKUs Without Backlight Key Toggle
VivoBook 15 (X1504, M1503) X1504ZA-NJ, M1503QA upper tiers X1504ZA base i3 configs Fn + F7
VivoBook 16 (M1603, X1605) M1603QA-MB, X1605ZA mid/high X1605ZA entry Celeron Fn + F7
VivoBook 17 (M1703, X1704) M1703QA-AU, X1704ZA-AU mid+ X1704ZA base Pentium Fn + F7
VivoBook S16 / V16 (K3605) K3605ZC, K3605ZV all tiers None in this sub-line Fn + F7

To confirm hardware presence: shut down completely, remove the bottom panel (seven Phillips PH1 screws on the 15, eight on the 16 and 17), and look at the keyboard ribbon connector on the motherboard. A backlit keyboard will have a second, narrower ribbon cable running alongside the main 26-pin data cable. If there is only one ribbon, the keyboard assembly has no backlight LEDs and no software fix will change that.

The asus v16 keyboard backlight not working complaint is disproportionately common because the K3605 series shipped with BIOS version 301 which has a known EC mismatch with the MyASUS app backlight API. That specific fix is covered below.

Software and Driver Fixes in the Correct Order

Do these in sequence. Skipping to step four without completing step one wastes time because Windows will re-break the driver on the next quality update.

  1. Verify the toggle first. Press Fn + F7 three times. The backlight cycles through off, low, and high. If nothing happens at all, hold Fn for two full seconds before pressing F7. Some EC firmware versions require the hold. Test your key response at Keyboard Test to confirm the key is registering at the OS level before assuming a backlight fault.
  2. Reinstall ASUS System Control Interface v2. Open Device Manager, expand System Devices, locate ASUS System Control Interface v2 or v3. Right-click, Uninstall Device, check the box to delete driver software. Do not reboot yet. Go to the Asus support page for your exact model number, download the ASCI driver package (filename typically contains ASUSSystemControlInterfaceV2 or V3 and a build number like 3.1.6.0 or newer). Install it, then reboot.
  3. Set the MyASUS backlight preference. Open MyASUS, go to Customization, then Keyboard Backlight. Set brightness to Medium or High. Apply. This writes the preference to the EC NVRAM so it persists across reboots. If the Keyboard Backlight option is greyed out or missing, the ASCI driver is still wrong.
  4. Update BIOS and EC firmware together. On the asus vivobook 15 keyboard backlight not working cases involving BIOS versions below 309, the EC firmware shipped at a revision that misreads the PWM duty cycle register. Download the BIOS update from Asus support. Run it through MyASUS Update or the standalone EZ Flash utility (hold F2 at POST, go to Advanced, EZ Flash 3, point it at the .CAP file on a FAT32 USB drive). Do not use a USB hub. After flash, the EC resets and the backlight default is restored to the last MyASUS-written value.
  5. Windows power plan interference. Navigate to Control Panel, Power Options, Change Plan Settings, Change Advanced Power Settings. Expand the ASUS section if present. Set Keyboard Backlight Timeout to a value other than zero. A zero value here overrides MyASUS and tells the EC to cut the PWM line immediately on idle.

For the asus vivobook 16 keyboard backlight not working and asus vivobook 17 keyboard backlight not working cases, the fix path is identical, but those models use a slightly wider EC chip (ITE IT8625E on the 16/17 versus IT8613E on most 15-inch boards) which means the BIOS .CAP files are not interchangeable. Always pull the update file using your exact model number, not just the series name.

Hardware-Level Diagnosis When Software Fixes Fail

If you have completed all five steps above and the backlight still does not respond, the fault is physical. These are the components to check in order of failure frequency.

Frequently Asked Questions

Why does my VivoBook backlight turn off every time I restart?

The EC NVRAM is not retaining the brightness value set by MyASUS. This happens when the ASUS System Control Interface driver is the wrong version or when a Windows quality update replaced it with a generic HID driver. Reinstall the ASCI driver from the Asus support site using your exact model number, then reapply the brightness setting in MyASUS. After that, the value survives reboots because it is stored in EC memory, not in the Windows registry.

Does the VivoBook 15 have a different backlight controller than the 16 or 17?

Yes. Most VivoBook 15 models use the ITE IT8613E embedded controller. The 16 and 17 inch models predominantly use the IT8625E. Both use PWM-controlled LED backlight circuits, but the register addresses differ, which is why BIOS files and EC firmware are not cross-compatible between screen sizes even within the same product generation.

My Fn + F7 key registers in software but the backlight does not change. What does that mean?

It means the keypress is reaching the OS but the ASCI driver is not translating it into an EC command. Confirm the key is registering correctly using Keyboard Test, then focus on the driver reinstall and BIOS update steps. The hardware path from keypress to EC is working; the software translation layer is broken.

Can I control VivoBook backlight brightness on Linux?

On kernels 5.17 and later, the asus-wmi kernel module exposes the backlight interface at /sys/class/leds/asus::kbd_backlight/brightness. Write 0, 1, or 2 to that file to set off, low, or high. If the file does not exist, load the module manually with modprobe asus-wmi and check dmesg for errors. Some early K3605 units require the asus_wmi.fnlock_default=0 kernel parameter to release the Fn key mapping.

Is the VivoBook backlight issue related to the keyboard keys themselves malfunctioning?

No, the backlight circuit and the key switch matrix are electrically separate. A backlight fault will never cause keys to stop working and vice versa. If you are seeing both problems simultaneously, you likely have a damaged ribbon cable that carries both the key matrix data and the backlight enable line, which share the same physical cable on some models. Run a full key check at Keyboard Test to map exactly which keys are affected before opening the machine.

Why is the asus v16 keyboard backlight not working even after a BIOS update?

The K3605 V16 series had a period where Asus published BIOS version 305 which updated the main firmware but did not bundle the corrected EC microcode. The fix requires BIOS version 309 or later, which includes the EC revision 106 that corrects the PWM register initialization sequence. If MyASUS shows your BIOS as current but you are on 305 or 306, check the Asus support page directly for a newer standalone BIOS package, as MyASUS update detection lagged behind the file availability for several months on this model.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester