How-to · Launch

A hung wps.exe is not a reason to install a second WPS.

Splash screen forever, immediate close, or a shortcut that does nothing. Work the boring list: disk space, official update, end leftover processes, cache, reboot, then reinstall from Kingsoft or a store. Search-ad “repair packs” are how a launch problem becomes a security problem.

Laptop that fails to launch the office suite

Name the failure

Does the splash appear and freeze? Does a window open and vanish? Does Windows say the app is already running? Those are different. A freeze after splash is often a locked process or a smashed cache. A vanish can be a crash on a full disk or a broken update. “Already running” is the leftover wps.exe you will end in Task Manager. Write down the last thing you did: Windows update, antivirus quarantine, installing a second office suite, or a cleanup tool. That sentence is the clue.

If you never got a clean install — you clicked a search ad — this may not be Kingsoft’s binary. Confirm the publisher. Uninstall mystery copies. Fetch only from wps.com/download or Microsoft Store 9NSGM705MQWC. Read is it safe and download.

Disk space is the quiet killer

Kingsoft’s own help still talks about modest hardware: a few gigabytes free is not optional when Backup Centre, cache, and the updater all want to write. If C: shows hundreds of megabytes, the suite can fail in ugly ways. Empty Recycle Bin only after you decided you do not need a deleted DOCX — or copy Recycle Bin out first. Move videos. Then see clear cache for WPS-specific folders. Do not run a “one-click booster” from an ad.

A full disk is also why recovery failed last week. If you need the unsaved file, copy %AppData%\kingsoft to another drive before you delete cache.

Update, then kill the leftover process

If the suite opens far enough for an update tile, take the official update. Store installs update through Windows. Website installs update through Kingsoft’s updater — allow it only after you trust the source. Over-eager firewalls sometimes block that updater; adding an allowlist is reasonable after you verified the path. Adding an allowlist for a blog EXE is not.

Open Task Manager (Ctrl+Shift+Esc). On the Processes tab, end wps.exe and other obvious Kingsoft office processes that are using CPU and showing no window. Do not end random Windows processes because a forum said so. Then launch from the Start menu shortcut once. If it works, you had a zombie. If it fails the same way, continue.

Cache and a single reboot

A corrupted cache can loop the splash. If Settings is reachable: Advanced → Cache, clear it. If Settings is not reachable, reboot once — locked files often release — then try again. A second reboot is superstition. After reboot, if it still fails, you are in reinstall territory, but copy AppData first if you need drafts.

Graphics glitches (blank ribbon, black window) sometimes improve if you update the GPU driver from the PC or GPU vendor, not from a driver-pack site. Try a Windows restart after a GPU update before you blame WPS alone. HiDPI and remote-desktop sessions produce their own paint bugs; test on the local console.

Reinstall: official only

Settings → Apps → WPS Office → Uninstall. If you used the Store, remove that listing. Reboot if Windows asks. Install again from the same official channel you trust. Do not “upgrade” by dropping a second installer from a mirror on top of a half-dead tree. After install, set file associations on purpose so you do not discover later that PDF now belongs to a Store stub — file associations.

If you intended to leave WPS and only wanted Word back, stop. You are in Office after uninstall, not in a third WPS install.

Linux and Mac, briefly

On Linux, a package that will not start is often a missing library or a Wayland quirk, not a Windows-style wps.exe. Try an X11 session. Prefer the current Deb/RPM from Kingsoft’s Linux page over a 2021 PPA. Fonts that look like a crash are usually tofu boxes — Linux fonts. On Mac, Trash the app and reinstall from the vendor download; do not grab a DMG from a video description.

Antivirus quarantine and the look-alike installer

Security tools sometimes quarantine a Kingsoft updater DLL after a signature change. The suite then fails at splash with no useful dialog. Open the antivirus quarantine list. If the file is from a path under official WPS Program Files and you installed from wps.com or the Store, restore it and add an allowlist for that path — after you re-checked the publisher. If the quarantined file is WPS-Office-Setup-2026.exe from Downloads and you do not remember fetching it from Kingsoft, delete it. SmartScreen on a freshly signed vendor installer is not automatic proof of evil; “allow anyway” on a blog button after a hard block is a delete. See safety.

Two WPS icons in Start is a clue you stacked a website install on a Store install, or the reverse. They can fight over services and look like “it will not open.” Uninstall both from Settings, reboot, install one channel. Then set associations so you know who owns DOCX. If you only wanted Microsoft Office back, stop stacking WPS and go to Office after uninstall.

Numbered launch steps

  1. Check free space on the system drive. Free several gigabytes if you are near empty. Copy Kingsoft AppData out if you need recovery.
  2. Confirm you are running a vendor or Store build, not a forum “full” installer.
  3. Apply an official update if the UI allows it.
  4. Task Manager: end hung wps.exe and related WPS processes. Launch once more.
  5. Clear cache from Settings if you can; otherwise reboot once and retry.
  6. Uninstall from Windows Settings. Reinstall only from wps.com or the Microsoft Store listing.
  7. Set DOCX, XLSX, PPTX, and PDF defaults. If Microsoft Office looks broken, use the uninstall-repair guide rather than another download.

Related: clear cache, ads (a nag is not a failed launch), troubleshooting, download, Windows notes.