Service Host: SysMain pinning your ASUS laptop’s disk at 100% is a familiar sight — whether it’s a VivoBook with a spinning drive or a ROG machine where the preload storm collides with game launchers at boot. SysMain, the service formerly known as Superfetch, preloads frequently used applications into memory. On fast NVMe SSDs it’s harmless background noise; on HDDs and during ASUS’s heavy startup sequence, it’s the disk hog in Task Manager.

ASUS laptops add their own wrinkle: Armoury Crate services, MyASUS background tasks, and Aura components all generate disk I/O in the same post-boot window where SysMain is most aggressive. This guide disables SysMain properly and trims the ASUS-specific competition. For the Dell take on this problem, see SysMain high disk usage on Dell ; for general disk issues, fixing 100% disk active time .

Why this happens

  • Preload storm after boot: SysMain’s heaviest work hits in the first 10–30 minutes — exactly when you’re launching things.
  • Armoury Crate background I/O: Crate services and Aura components adding disk load in the same window.
  • Game launchers updating at startup: Steam, Epic, and others patching games while SysMain preloads.
  • HDD or nearly-full SSD: Slow or cramped storage can’t absorb the combined load.
  • MyASUS scheduled tasks: Background update checks and diagnostics competing for disk.
  • Windows updates re-enabling SysMain: Feature updates resetting the service to Automatic.
  • Failing drive: A degrading disk turning heavy I/O into 100% active time with nothing to show.
  • Antivirus scanning preloads: Real-time AV multiplying the I/O cost.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm SysMain is the top disk consumer

Verify with Task Manager.

  1. Task Manager > Processes, sort by Disk — confirm Service Host: SysMain leads.
  2. Performance > Disk: check drive type and whether 100% active time comes with real throughput (overload) or ~0 MB/s (possible drive failure — check wmic diskdrive get status).
  3. Note the timing — post-boot storm easing within 30 minutes is the classic pattern.
  4. Identify co-offenders: Armoury Crate services, Steam/Epic updaters, antivirus — note the top three.
  5. If SysMain is idle and something else leads, target that instead.

Fix 2: Disable SysMain via Services

The standard method.

  1. Win + R > services.msc > SysMain > double-click.
  2. Startup type: Disabled > Stop > OK.
  3. Restart and observe a full boot cycle in Task Manager > Performance > Disk.
  4. Launch your usual apps and games — note whether the disk stays responsive during startup now.
  5. Keep a before/after mental note: boot-to-usable time is the metric that matters.

Fix 3: Alternative disable methods

Command line and registry options.

  1. Elevated terminal: sc stop "SysMain" and sc config "SysMain" start=disabled.
  2. Registry alternative: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysMain > Start = 4.
  3. Verify: sc query "SysMain" shows STOPPED; services.msc shows Disabled.
  4. Re-enable: sc config "SysMain" start=auto + sc start "SysMain".
  5. Use whichever method you prefer — they all flip the same switch.

Fix 4: Tame ASUS background disk load

The ASUS-specific companion fix.

  1. Open Armoury Crate > Settings — disable automatic updates and any background features you don’t use (you can update manually monthly).
  2. In MyASUS, reschedule automatic checks to overnight or switch to manual.
  3. Task Manager > Startup apps — disable ASUS entries you don’t need at boot; keep function-key/hotkey utilities if you rely on them.
  4. If you don’t use Armoury Crate’s gaming features, consider uninstalling it — it removes a whole category of background I/O (reinstall from ASUS anytime).
  5. Update remaining ASUS drivers via MyASUS — current drivers are generally more I/O-efficient.

Fix 5: Stagger game launchers and cloud sync

Stop the startup pileup.

  1. In Steam: Settings > Interface > uncheck Run Steam when my computer starts; do the same for Epic Games Launcher, EA App, and other platforms.
  2. Launch game clients manually only when you want to play — not at every boot. Each launcher you prevent from auto-starting removes both its update checks and its background services from the disk queue.
  3. Pause OneDrive/Dropbox sync during gaming sessions — sync I/O plus game loading is a bad combination.
  4. In Task Scheduler, look for launcher update tasks scheduled at logon and stagger them.
  5. The goal: at boot, the disk serves Windows and your immediate app — nothing else.

Fix 6: Check drive health and free space

Don’t tune around failing hardware.

  1. wmic diskdrive get status must report OK — otherwise back up immediately.
  2. SSD users: run the manufacturer’s toolbox for health % and firmware updates.
  3. Keep 15–20% free on C: — use Settings > System > Storage > Cleanup recommendations.
  4. Run chkdsk C: /f if you suspect file-system issues.
  5. On ROG laptops with dual drives, consider moving games to the secondary drive to split I/O load.

Fix 7: Prevent re-enablement and consider hardware

Long-term thinking.

  1. After Windows feature updates, recheck services.msc — re-disable SysMain if resurrected.
  2. A desktop batch file with the sc config command, run as admin post-update, makes this trivial.
  3. If the laptop still has an HDD, the SSD upgrade is the definitive fix — NVMe on supported ASUS models transforms the entire experience; clean-install via the Windows 11 download .
  4. With a fast SSD, SysMain’s on/off state becomes unnoticeable — stop worrying about it.
  5. For official service behavior details, Microsoft’s Windows support hub documents SysMain’s role.

Closing

On an ASUS laptop, SysMain’s disk hunger is worst when combined with Armoury Crate, game launchers, and slow storage all waking up together. Disable SysMain, stagger the startup pileup, trim ASUS background services, and check the drive’s health. The 100% disk era ends — and the SSD upgrade, when you’re ready, ends the entire category of problem. Your games and apps will thank you every single boot, with faster launches and none of the old grinding delays that made the laptop feel broken.

Frequently asked questions

Why does SysMain cause problems on ASUS gaming laptops?
Even on capable ASUS machines, SysMain can spike disk usage after boot while it preloads large game libraries and creative apps — exactly when you’re trying to launch a game. On ASUS laptops with HDDs or small SSDs, this preload storm collides with Armoury Crate’s own background services and game-platform updaters (Steam, Epic) that also hammer the disk at startup. The result is 100% disk precisely when you want responsiveness.
Will disabling SysMain affect game loading times on my ASUS laptop?
Minimally. SysMain preloads frequently used apps, but games load primarily from storage speed and are so large that preloading barely dents their load times — an SSD determines game loading far more than SysMain ever could. What you gain is a disk that isn’t saturated when you double-click the game, which matters more for perceived responsiveness than any preload optimization.
Does Armoury Crate conflict with SysMain?
Not directly — they’re independent services. But they compete for the same disk: Armoury Crate’s background services, Aura lighting control, and update checks generate I/O at the same time SysMain preloads. Disabling SysMain removes the biggest single disk consumer, which gives Armoury Crate’s legitimate background work room to complete without pushing the disk to 100%.
Is SysMain the same as Superfetch in Task Manager?
Yes — Task Manager and services.msc on Windows 11 show SysMain, which is the renamed Superfetch service (renamed in Windows 10 version 1809). If you’re following an older guide that says to disable Superfetch, you’re looking for SysMain. Same service, same function, same disable procedure.