Optional updates on an ASUS laptop live at the intersection of two driver systems that do not always agree: Windows Update’s optional driver offerings and ASUS’s own Armoury Crate/MyASUS driver management. When they disagree — different versions, locked devices, conflicting installers — the optional update fails, sometimes repeatedly, and the entry just sits there daring you to click it again.
ASUS machines add specific wrinkles. Armoury Crate’s services touch power and device management, ASUS often customizes reference drivers for its ROG and TUF gaming lines, and MyASUS may have already installed a newer driver than the one Windows is offering. This guide sorts out which situation you are in and gets the updates you actually need installed.
ASUS’s driver ecosystem is unusually active: Armoury Crate updates itself, MyASUS pushes driver notifications, and Windows Update offers its own versions, all on different schedules. That is three cooks in the driver kitchen, and optional-update failures are what dinner looks like when they disagree. The trick is appointing a head chef — for core hardware, that is ASUS’s own tools — and letting Windows Update handle only the side dishes it is good at.
Why this happens
- Armoury Crate or MyASUS holding device locks that block Windows Update’s driver installer.
- Version conflicts: ASUS installed a newer (or custom) driver, and Windows Update’s older package fails against it.
- Custom ASUS driver builds for ROG/TUF hardware that generic Windows Update packages cannot cleanly replace.
- The optional update was superseded or withdrawn by Microsoft but the stale entry remains.
- Corrupted driver store preventing the new driver package from staging.
- Pending reboot from an earlier install that Windows does not clearly flag.
- Metered connection settings silently blocking optional update downloads.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Check whether you need the update at all
- Open Settings > Windows Update > Advanced options > Optional updates and identify the exact driver offered.
- Check MyASUS — if ASUS already installed an equal or newer driver for that device, you do not need Windows’ version.
- If the device works perfectly, uncheck the update and ignore it. Not every offered update deserves installation.
- Only continue if a device is misbehaving and the optional update targets it.
Fix 2: Update Armoury Crate and MyASUS first
- Open the Microsoft Store, go to Library, and update Armoury Crate and MyASUS to their latest versions.
- Open MyASUS and install any driver updates it offers for the device in question — prefer ASUS’s driver over Windows'.
- Restart the laptop after ASUS’s updates complete.
- Re-check optional updates. In many cases the entry disappears because ASUS’s driver satisfied the requirement.
Fix 3: Stop ASUS background services temporarily
- Press Windows key + R, type
services.msc, and press Enter. - Stop any services starting with Armoury Crate or ASUS (right-click > Stop).
- Open Task Manager’s Startup apps tab and disable Armoury Crate entries temporarily.
- Retry the optional update install now, with ASUS’s services quiet. Re-enable them afterward. The official Windows Update support page covers service-conflict troubleshooting generally.
Fix 4: Install one update at a time after a clean restart
- Do a full Restart from the Start menu.
- In Optional updates, select only the single driver you need and click Download & install.
- Never batch multiple driver updates — one failure masks the others and wastes the whole attempt.
- Restart again after installation before attempting any additional optional updates.
Fix 5: Get the driver from the component maker
- Identify the actual hardware: in Device Manager, check the device’s Hardware Ids under Properties > Details if needed.
- For graphics, download directly from NVIDIA , AMD’s driver download page, or the Intel Driver & Support Assistant .
- Run the manufacturer’s installer as administrator — these packages are more current than Windows Update’s and bypass it entirely.
- After installing, the optional update entry typically clears itself within a day. Related driver-update failures: driver updates failing in Windows Update .
Fix 6: Repair the driver store and update cache
- Open an elevated Command Prompt and run:
net stop wuauserv - Delete the contents of
C:\Windows\SoftwareDistribution\Download. - Run
net start wuauserv, then retry the optional update. - If it still fails, the driver store itself may be damaged — in the same elevated prompt, run
DISM /Online /Cleanup-Image /RestoreHealthfollowed bysfc /scannow, reboot, and retry. See also stuck download repairs .
Fix 7: Hide the stubborn update and move on
- Download Microsoft’s Show or Hide Updates troubleshooter (
wushowhide.diagcab). - Run it, choose Hide updates, and select the failing optional driver.
- Windows stops offering it; install the driver from ASUS or the component maker instead (Fix 5).
- Check back in a few months — updated packages usually appear that install cleanly.
Fix 8: Extract the ASUS driver package and install via Have Disk
ASUS driver installers sometimes refuse to run when they detect a version conflict; extracting the files and installing manually sidesteps the check.
- Download the driver from ASUS support for your exact model and extract it (an archive tool opens most ASUS installer packages).
- In Device Manager, right-click the device > Update driver > Browse my computer for drivers > Let me pick from a list > Have Disk.
- Point at the extracted
.inffile and finish the wizard. - Restart, verify the device, and confirm the optional update entry clears. This is the definitive manual path when every automated route fails.
Closing
On ASUS laptops, optional update failures are usually a turf war between ASUS’s driver management and Windows Update’s. Let ASUS win for core hardware — update Armoury Crate and MyASUS first, quiet their services during installs, and go straight to the component maker for graphics drivers. The optional updates list is a suggestion box, not a to-do list. Once the driver you need is installed by whatever route worked, stop and declare victory — do not keep clicking the remaining optional updates out of completeness. A stable ASUS with one manually installed driver beats a churned one with ten, every time.
