The Asus Vivobook S 15 was among the first Snapdragon X Elite laptops to market, and it remains a popular Copilot+ choice. But early-adopter owners report a consistent set of issues: the Copilot key doing nothing, the Copilot app crashing or refusing to sign in, AI features that will not initialize, and performance quirks from first-generation Snapdragon drivers.

Because the Vivobook S 15 launched so early in the Snapdragon X cycle, many of its problems were fixed in later driver and Windows updates — which means the single most effective troubleshooting step is simply getting fully updated through the right channels. This guide covers that plus every other common fix.

Work through these in order. If your whole system feels slow rather than just Copilot, start with our AI PC slow after Windows update guide, and fingerprint-login users should check Copilot+ PC fingerprint reader not working .

Why this happens

  • Early Snapdragon drivers: Launch-era Qualcomm drivers had Copilot, power, and stability bugs fixed in later releases.
  • Copilot app churn: Microsoft rebuilt the Copilot app multiple times, and stale installs break the key and features.
  • Region and account gates: Copilot needs a supported region and Microsoft account; both silently disable features.
  • MyASUS conflicts: Asus utilities occasionally clash with Windows native power and network management.
  • Emulated app drag: x86 apps under Prism feel slower and drain battery faster than ARM64 natives.
  • NPU driver state: AI features need a healthy Qualcomm NPU driver, which Windows updates sometimes break.
  • First-gen firmware: Early BIOS versions had sleep and USB quirks that Asus later patched.

How to fix it

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

Fix 1: Repair the Copilot key and app

The Copilot key is a launcher for the Copilot app, so key problems are app problems. Microsoft’s multiple Copilot app rebuilds left many Vivobook S 15 units with stale or half-migrated installs. A clean repair-or-reinstall of the app fixes the key in most cases.

  1. Open the Microsoft Store, search for Microsoft Copilot, and install any available update.
  2. If the key still does nothing, go to Settings, Apps, Installed apps, find Microsoft Copilot.
  3. Click the three dots, choose Advanced options, and click Repair, then test the key.
  4. If Repair fails, return and click Reset, then sign back in to the app.
  5. As a final step, uninstall Copilot completely, restart, and reinstall it fresh from the Store.
  6. Verify your region is Copilot-supported under Time & language settings, since region blocks disable the key silently.

Fix 2: Update everything through MyASUS and Windows Update

The Vivobook S 15’s early drivers are the root of most remaining issues — Wi-Fi quirks, sleep bugs, NPU failures, and even Copilot instability. Asus-validated updates through MyASUS plus full Windows Updates resolve the majority of complaints in one pass.

  1. Open MyASUS and install all recommended driver, BIOS, and firmware updates.
  2. Restart when prompted, especially after BIOS updates.
  3. Open Settings, Windows Update, and install all updates including optional driver updates.
  4. Restart again and check Task Manager’s Performance tab for a healthy NPU entry.
  5. Test the Copilot key and app after the updates before changing settings.
  6. Recheck MyASUS monthly — Qualcomm platform drivers matured rapidly through the first year.

Fix 3: Fix Copilot sign-in and sync problems

Copilot features that demand sign-in — chat history, personalization, voice — break when the account token goes stale, which happens silently after password changes or long gaps. Refreshing the account connection restores them without reinstalling Windows.

  1. Open the Copilot app and check whether you are signed in; sign out and back in.
  2. In Windows Settings, go to Accounts, Email & accounts, and verify your Microsoft account shows no errors.
  3. If the account shows an issue, remove it and add it again, then restart.
  4. Check that date, time, and time zone are correct — token validation fails with wrong clocks.
  5. Temporarily disable any VPN, since Copilot’s cloud services can be region-sensitive.
  6. If a work or school account is primary, try a personal Microsoft account to isolate policy restrictions.

Fix 4: Get Copilot+ AI features working

Recall, Cocreator, Live Captions, and Studio Effects share prerequisites: 24H2, healthy NPU driver, account sign-in, supported region. On the early Vivobook S 15, the NPU driver is the usual weak link. Walk the chain methodically.

  1. Confirm Windows 11 version 24H2 or later in Settings, System, About.
  2. Verify the NPU appears in Task Manager’s Performance tab without warnings.
  3. Reinstall the Qualcomm NPU driver from MyASUS or Asus support if the NPU shows issues.
  4. Update AI-related apps from the Microsoft Store (Camera, Paint, Photos).
  5. Check that AI features are not disabled in Settings, Privacy & security.
  6. For background on NPU troubleshooting across vendors, see AI Boost greyed out in Task Manager .

Fix 5: Fix performance and battery quirks

A Vivobook S 15 that feels slow or drains fast is usually fighting emulation overhead, startup bloat, or a sleep-blocking driver — not a weak chip. The Snapdragon X Elite is genuinely fast, so diagnose the drag instead of accepting it.

  1. In Task Manager, add the Architecture column and identify heavy x86 (emulated) apps; replace with ARM64 versions where available.
  2. Trim startup programs in Task Manager’s Startup apps tab.
  3. Set power mode to Balanced in Settings, System, Power & battery.
  4. Run powercfg /sleepstudy in an elevated Command Prompt to find sleep blockers if standby drain is the issue.
  5. Update the Qualcomm Wi-Fi driver, the most common sleep and drain culprit.
  6. If problems began after a Windows update, check Microsoft’s Windows support hub for known issues with that build.

Fix 6: Tame MyASUS and background software

Asus utilities add value but can also cause the exact symptoms owners blame on Windows: network prioritization weirdness, fan behavior changes, and update conflicts. When troubleshooting stalls, simplify by reducing MyASUS’s footprint.

  1. Open MyASUS and review enabled features; disable network optimization if Wi-Fi behaves oddly.
  2. Check Task Manager for Asus background services consuming CPU constantly.
  3. Disable Asus startup entries you do not actively use.
  4. If issues started after a MyASUS update, uninstall and reinstall MyASUS from the Store.
  5. As a diagnostic, uninstall MyASUS entirely for a day — Windows 11 handles the Snapdragon platform well alone.
  6. Reinstall only the features you missed; a minimal install causes the fewest conflicts.

Closing

The Vivobook S 15 rewards owners who keep it updated: MyASUS plus Windows Update resolves most early-driver issues, the Copilot app usually just needs a repair or reinstall, and ARM64-native apps eliminate the emulation drag. With current drivers and a lean startup list, this first-generation Snapdragon laptop still feels modern and fast.

Frequently asked questions

Why does the Copilot key do nothing on my Vivobook S 15?
The key needs the Microsoft Copilot app installed, a supported region, and a signed-in Microsoft account. Update the app from the Store, check region settings, and restart the laptop — the key should then launch Copilot.
How do I fix Copilot app crashes on the Vivobook S 15?
Repair or reset the Copilot app in Settings, Apps, Installed apps, Advanced options. If crashes persist, uninstall and reinstall it from the Microsoft Store, and make sure Windows is fully updated.
Where are Asus drivers for the Vivobook S 15 Snapdragon?
Use the MyASUS app or Asus’s support site for your exact model. Qualcomm platform drivers are validated by Asus — avoid generic driver tools that install wrong versions on ARM laptops.
Why is my Vivobook S 15 slow despite the Snapdragon X Elite?
Slowness usually comes from emulated x86 apps, startup bloat, or power saver mode. Replace heavy apps with ARM64 versions, trim startup programs, use Balanced power mode, and update Qualcomm drivers.