Troubleshoot SU-PQR1603 in Epic Games Launcher
What to do first
Record SU-PQR1603, verify the affected product and environment, correct the confirmed prerequisite, and retry once under the same conditions.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Epic Games Launcher
- Versions and conditions
- Windows 10 / 11
- Error codes and identifiers
- SU-PQR1603
Symptoms
- The operation fails with SU-PQR1603.
- The same failure is reproducible in Epic Games Launcher.
Causes and conditions
The official article identifies a product, compatibility, storage, update, network, file, or configuration condition that must be resolved before retrying.
Before you start
- Exit the game and launcher normally; record the account, title, complete error, and occurrence time.
- Before changing local saves or settings, find the developer-documented save location and copy it to another folder.
Precautions
- Launching through a sync warning or conflict can overwrite newer progress with an older save.
- Do not bulk-delete the game, userdata, or save folders without a backup.
Step-by-step instructions
Complete Settings > Windows Update work and pending restarts, close other installers, restart, and run only Epic Launcher.
Exit Launcher and choose Run as administrator once. If that works, investigate folder permissions instead of keeping permanent elevation.
Use the installation log to identify the failed component, then repair or install Microsoft's official matching Visual C++ Redistributable x86/x64. Never download individual DLLs.
Confirm free space and write access for the Epic destination and Temp. Preserve Launcher logs and the failed prerequisite name if the code remains.
Check the result
- SU-PQR1603 no longer appears and the operation completes.
- The selected version and settings remain after restart.
- A second test shows no new display, input, save, or synchronization problem.
If the problem continues
- Restore reversible settings from the notes and escalate without deleting user data.
- Prefer the PC maker or administrator procedure for OEM drivers and managed networks.
- Protect account names, tokens, and save contents before sharing logs.
Scope of this guide
Troubleshooting guide — A general diagnostic guide based on official support. It does not claim a current incident or a version-specific fix.
Frequently asked questions
Is x64 Visual C++ alone enough?
Not always. A 32-bit component can require x86 even on 64-bit Windows; follow the log and vendor requirement.
Should I re-register all of Windows Installer because of 1603?
No. Identify the specific prerequisite, update, or permission failure before broad system changes.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.