The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →If Steam remains on “Launching — Running install script (Microsoft VC Redisutable)” and never opens the game, restart Windows, manually run the correct Visual C++ installer from the game’s _CommonRedist folder, install or repair both x86 and x64 packages when appropriate, then verify the game files. The message does not prove that Visual C++ is missing: Steam retries a prerequisite whenever its installer returns a nonzero exit code, even if a usable runtime is already installed.
If the manual installer displays an error, fix that Windows Installer or Visual C++ error first. If the installer completes successfully but Steam keeps repeating the script, the problem may be Steam’s prerequisite bookkeeping rather than the runtime itself.
As an Amazon Associate I earn from qualifying purchases.
Steam Stuck on “Running Install Script (Microsoft VC Redistributable)”? Fixes That Work
What the Steam message actually means
Steam is trying to run a prerequisite installer before starting the game. The status text is Steam’s description of that phase, not the name of a missing DLL and not conclusive evidence that Visual C++ is absent.
The actual file is usually one of these:
VC_redist.x86.exeVC_redist.x64.exe- An older installer such as
vcredist_x86.exeorvcredist_x64.exe
That installer installs shared Microsoft C and C++ runtime libraries. Games built with Visual Studio commonly depend on those libraries, but different games can require different runtime families and CPU architectures.
#1 Best Overall
- Officially licensed M.2 SSD for PlayStation 5 consoles[4] so you can easily install and play with no concern of compatibility. [4]For PlayStation 5 system software compatibility, please visit the official WD_BLACK site.
- With capacities ranging from 1TB to 4TB[1], your PS5 console has the additional space to store up to 200 games[3] (8TB model) [1]1GB = 1 billion bytes and 1TB = one trillion bytes. Actual user capacity may be less depending on operating environment. [3] Number of games based on a 36GB average per game. The number of games will vary based on file size, formatting, other programs, and factors.
- Experience uninterrupted gameplay with a brand-new, optimized heatsink designed especially for the PS5 console for an easy, worry-free installation into the M.2 slot.
- Play directly from the drive and eliminate the need to transfer or delete games from your console with tested and approved storage for your PS5 console[4].
- Push the envelope of PCIe Gen 4 technology with read speeds up to 7,300MB/s[2], giving you seamless gameplay and incredibly short load times. [2]1 MB/s = 1 million bytes per second. Based on internal testing; performance may vary depending upon host device, usage conditions, drive capacity, and other factors.
Steam may use a prerequisite bundled specifically with the game, or it may use Steamworks Common Redistributables. Valve’s shared package can contain Visual C++, DirectX 9, .NET, OpenAL, XNA, and PhysX installers. See Valve’s documentation for the distinction between shared redistributables and game install scripts: Steamworks Common Redistributables.
Steam’s install-script behavior explains why the same message can appear repeatedly. Valve documents that Steam runs the prerequisite and records its completion state when the process exits successfully. A nonzero exit code tells Steam that the prerequisite did not complete, so Steam tries it again on a later launch: Valve’s InstallScripts documentation.
That creates two different possibilities:
- A genuine installation problem: the runtime is missing, the wrong architecture was installed, Windows Installer is busy, permissions are insufficient, the package is damaged, or security software blocked it.
- A bookkeeping loop: the runtime is already usable, but the bundled installer returns a nonzero result—for example, because it detects a newer package—and Steam keeps retrying it.
Is the behavior normal?
| What happens | What it usually means |
|---|---|
| The script runs briefly once and the game launches | Normal first-run prerequisite setup. |
| It takes several minutes and then launches | The installer may be slow, waiting on Windows, or being checked by security software. Investigate if it happens on every launch. |
| It remains indefinitely or repeats every time | Likely an installer failure, permission problem, corrupted package, pending Windows Installer operation, or Steam bookkeeping loop. |
| Many unrelated games show the same message | More likely a system-wide Visual C++, Windows Installer, permission, update, or security-software problem. |
| Only one old game shows it | More likely that title’s legacy runtime or game-specific install script. |
Reports of this affecting multiple unrelated games—particularly after a fresh Windows installation—are anecdotal examples, not proof of one universal Steam client bug. The useful distinction is whether the supplied installer succeeds when you run it directly.
Recommended Free Tools
Before you start: identify the scope of the failure
- Does the problem affect one game or several?
- Is this the game’s first launch, or has it worked before?
- Are you running 64-bit Windows? Most Windows 10 and 11 PCs are, but the game’s architecture still determines which runtime it needs.
- Does a UAC prompt appear when the game launches?
- Does a manually launched installer show an error code?
- Did Windows Update, another game launcher, a driver utility, or another application installer recently run?
Do not launch several games or installers while troubleshooting. Windows Installer operations can block one another, and that can create a second problem while you are diagnosing the first.
The fastest safe repair procedure
1. Restart Windows completely
Exit Steam, close other game launchers and installers, and choose Restart in Windows. Do not merely sign out. After Windows starts, allow any visible Windows Update, driver installation, or application setup to finish before opening Steam.
This is especially important for 0x80070652, which generally indicates that another Windows Installer operation is already in progress or that Windows is waiting for installation work to finish. Microsoft lists the related Windows Installer conditions in its Windows Installer error messages.
2. Open the game’s installation folder
In Steam, right-click the affected game, select Properties, choose Installed Files, and select Browse. Look for a folder named _CommonRedist, vcredist, or another prerequisite folder.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The usual game-specific path is:
<Steam library>steamappscommon<Game Name>_CommonRedistvcredist<year>The year folder may be named 2010, 2012, 2013, 2015, 2019, 2022, or something similar. The exact folder depends on what the game developer bundled.
If the game does not contain the installer, inspect Steam’s shared prerequisite folder:
<Steam installation>steamappscommonSteamworks Shared_CommonRedistvcredistYour Steam installation may not be C:Program Files (x86)Steam. Use the real library or Steam installation path shown by Steam. Valve’s support article on secondary installers explains that they are normally stored in the game’s installation directory or a subfolder: Steam Support: secondary installers.
3. Run the supplied installer manually
Open the relevant year folder and run the supplied Visual C++ installer. If both VC_redist.x86.exe and VC_redist.x64.exe are present, run both on 64-bit Windows. Right-click each file, select Run as administrator, approve the UAC prompt, and let the graphical installer finish.
- If it offers Repair, choose Repair.
- If it offers Install, complete the installation.
- If it asks to restart Windows, restart before testing the game.
Repeat the same process in Steamworks Shared_CommonRedistvcredist if that is where the relevant package is stored. Manually launching a secondary installer is also the normal recovery step Valve recommends when it was canceled or prevented from running during first launch.
This test is important because it separates Steam’s status screen from the actual failure. If the installer shows an error, you now have a Windows installer problem to solve. If it completes successfully, Steam may simply need its game files or prerequisite state refreshed.
4. Verify the game files
After the runtime installation or repair completes, close and reopen Steam, then:
- Right-click the game and select Properties.
- Open Installed Files.
- Select Verify integrity of game files.
- Wait for verification to finish, then restart Steam and try the game again.
Steam says verification can take several minutes. It is also normal for one or more files to fail verification when they are local configuration files that Steam does not replace. The official procedure is documented in Steam’s file-verification guide.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Video Game Box: The storage box measures 12.75x6.9x4.25 inches. This video game storage case is designed to fit Nintendo Switch games.
- Large Capacity: Each box can storage 28 cases. Easy to storage and organize your collections.
- Store Games with The Titles Showing: 4.25 inches tall. You can see video games with titles upward, easier to find and pick your game collections.
- Strong Magnetic Closure: The black storage box has a concealed and sturdy magnetic closure that allows the flip-top storage box to be easily open and closed repeatedly.
- Sturdy and Quality: The game case holder has a thick, sturdy board construction with a water-resistant laminate. Cardboard but very rigid, tough. The storage box is sturdy enough to stack on each other.
Install the correct Visual C++ package
Modern Visual C++ v14 packages
For games built with the modern Visual C++ family, Microsoft groups the Visual C++ 2017, 2019, 2022, and 2026 runtimes under the v14 family. Microsoft updates the current package over time, so use its permanent architecture-specific links rather than downloading a fixed build from an unofficial site:
- Microsoft Visual C++ v14 x86 Redistributable
- Microsoft Visual C++ v14 x64 Redistributable
- Microsoft Visual C++ v14 ARM64 Redistributable
On a conventional 64-bit Intel or AMD Windows PC, install the current x86 and x64 packages when the game’s installer supplies both or when you are repairing a system-wide issue. The operating system’s bitness does not determine the game’s bitness: a 32-bit game needs the x86 runtime even on 64-bit Windows. Installing only x64 is not sufficient for that game.
On Windows running on ARM64, follow Microsoft’s architecture guidance. The x64 package can contain x64 and ARM64 binaries when installed on an ARM64 device, but an application’s architecture and the package supplied by the game should still guide the choice. Microsoft’s compatibility and download guidance is in its latest supported Visual C++ Redistributable documentation.
Older games may need legacy runtimes
The latest v14 package does not replace every older Visual C++ runtime. Visual C++ 2013 and earlier remain side by side because older games can depend on their specific libraries. For example, a game that needs MSVCR100.dll may require Visual C++ 2010 rather than the latest v14 package.
| Runtime family | Microsoft-listed latest package version |
|---|---|
| Visual Studio 2013 / VC++ 12.0 | 12.0.40664.0 |
| Visual Studio 2012 Update 4 / VC++ 11.0 | 11.0.61030.0 |
| Visual Studio 2010 SP1 / VC++ 10.0 | 10.0.40219.325 |
| Visual Studio 2008 SP1 / VC++ 9.0 | 9.0.30729.5677 |
| Visual Studio 2015 / VC++ 14.0 | 14.0.24212.0 |
These are legacy, unsupported Visual Studio releases. Prefer the copy bundled with the game or the Microsoft-hosted download identified in Microsoft’s supported Redistributable list. Do not use random DLL-download websites or third-party “all-in-one” Visual C++ archives.
Do not uninstall every Visual C++ entry in Apps and Features. Different games and applications can legitimately require different legacy packages, and those packages are designed to coexist. Remove or repair a specific package only when an installer error or Microsoft’s troubleshooting guidance calls for it.
Fix the installer according to its error code
0x80070652: another installation is already in progress
Close Steam, other launchers, driver utilities, and application installers. Restart Windows, check Windows Update, and try the Visual C++ installer again.
If it still fails, open Task Manager, select the Details tab, and look for msiexec.exe only after you have closed legitimate installers. An orphaned Windows Installer process can be involved, but do not blindly terminate system processes or delete Windows Installer registry data. If you are unsure whether a process belongs to an active installation, restart again or obtain support rather than killing it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems0x80070666: another version is already installed
This usually means the bundled installer is older than the same-architecture Visual C++ package already installed. It does not automatically mean Visual C++ is broken.
For the modern v14 family, keep the newer package. Download the current Microsoft package for the same architecture and choose Repair if it is available. Do not downgrade simply to satisfy an old bundled installer.
This is a plausible explanation for a Steam loop: the old installer returns a nonzero result because it detects a newer runtime, and Steam retries the prerequisite according to Valve’s documented rules. That connection is an inference from Microsoft’s newer-version behavior and Valve’s retry behavior, so confirm it by checking the installed runtime and the affected game rather than assuming every loop has this cause.
1603: generic installation failure
Error 1603 is not a complete diagnosis. Microsoft says the Visual C++ installer log is needed. First restart Windows, run the installer as administrator, install pending Windows updates, and retry.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteOther possible contributors include locked files, a damaged installer cache, insufficient permissions, antivirus or endpoint protection, and a pending restart. If appropriate for your security policy, temporarily test with real-time blocking disabled, then immediately re-enable protection. Never leave security software disabled as a permanent fix.
Error 5: access denied
Run the individual Visual C++ installer as administrator. If the error continues, check antivirus or corporate endpoint protection, group policy, and permissions on the temporary and installation folders. Microsoft associates this error with permissions problems in its VC Redistributable troubleshooting guide.
Error 32: file is locked
Close the game and other applications, restart Windows, and retry. Antivirus scanning or another process may be holding a file open. Microsoft also lists corrupted files as a possible contributor.
Rank #3
- Video Game Box: Case internal size is 12" x 6.7" x 5.3". This video game storage case is designed to fit most video games and Blu-ray cases, please measure your item before purchase to ensure a correct fit.
- Large Capacity: Each box can storage 20 PCS of Steel Book Boxes. Easy to storage and organize your collections.
- Store Games with The Titles Showing: 5.3 inches tall. You can see video games with titles upward, easier to find and pick your game collections.
- Strong Magnetic Closure: The steel book storage case has a concealed and sturdy magnetic closure that allows the flip-top storage box to be easily open and closed repeatedly.
- Sturdy and Quality: The game case holder has a thick, sturdy board construction with a water-resistant laminate. Cardboard but very rigid, tough. The storage box is sturdy enough to stack on each other.
Error 1620, 0x80091007, or 0x80070654
These errors point toward a damaged, invalid, or unusable installer package or cache:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →1620: Windows Installer could not open the package.0x80091007: payload verification or hash mismatch.0x80070654: the MSI package failed to run.
Replace the package with an official Microsoft download, or let Steam reacquire the game’s shared prerequisite files. Do not attempt to repair a corrupted executable by downloading a DLL or MSI from an unrelated website.
Error 1714: corrupted Windows Installer cache
Microsoft associates 1714 with a corrupted cached installer that prevents an older Visual C++ version from being removed or updated. Do not immediately delete registry keys or manually remove Visual C++ folders. Use Microsoft’s Program Install and Uninstall troubleshooter where applicable, and collect installer logs before attempting an invasive repair.
Get useful installer logs
Use the normal graphical installer while diagnosing the problem. Silent installation can hide the message that explains the Steam loop.
Microsoft documents these Visual C++ Redistributable switches:
/install Install
/repair Repair
/uninstall Uninstall
/passive Show progress with limited interaction
/quiet No user interface
/norestart Suppress restart
/log file.txt Write to a specified logFor example, from the folder containing the actual installer:
VC_redist.x64.exe /install /passive /norestartVC_redist.x64.exe /repair /passive /norestart /log "%TEMP%vcredist-repair.log"Replace the filename with the installer you actually have. Use x86 for a 32-bit package. Microsoft says the Redistributable also creates a log in %TEMP% by default, and the /log switch lets you choose a specific file. Details are in Microsoft’s Redistributing Visual C++ files documentation.
For a more complete collection, Microsoft’s troubleshooting procedure uses the Visual Studio and .NET Log Collection Tool:
- Download the tool from the link in Microsoft’s VC Redistributable installation troubleshooting guide.
- Run
Collect.exe. - Extract
%TEMP%vscollect.zip. - Inspect files with names similar to
dd_vcredist_<arch>_yyyyMMddHHmmss. - Search the logs for
Error,Failed, andSystem Error.
Windows Installer also supports detailed msiexec logging, but typical users should not extract or alter the Visual C++ installer’s internal MSI. Use that level of troubleshooting only when the logs or support staff specifically require it. Microsoft documents the command-line logging options for msiexec here.
Repair Steam’s prerequisite files
Verify Steamworks Common Redistributables
Some Steam installations expose Steamworks Common Redistributables as a library tool. If it appears in your library, right-click it, open Properties, choose Installed Files, and select Verify integrity of tool files. Restart Steam afterward.
This is a practical Steam-client workaround, not a universally documented consumer repair procedure. If the tool is not visible in your library, use the game’s own file verification and the shared-folder steps instead.
Reacquire missing or damaged shared files
If Steamworks Shared_CommonRedist is missing or its installer is visibly damaged:
- Exit Steam completely. Use Steam > Exit, then confirm Steam is no longer running.
- Back up important Steam configuration and save data.
- Verify the affected game’s files.
- Verify Steamworks Common Redistributables if the tool is available.
- If Steam cannot download or refresh the files, clear the download cache and allow Steam to reacquire them.
Valve maintains the common redistributables and can update their install scripts when patches are available, as described in its Common Redistributables documentation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Clear Steam’s download cache only when it fits the symptom
Use this when Steam cannot download, refresh, or start the prerequisite files:
- Open Steam > Settings.
- Select Downloads.
- Choose Clear Download Cache.
- Confirm and sign in again when prompted.
Steam says clearing the cache does not remove installed games, but it does sign you out. It is not a direct repair for a broken Windows Visual C++ installation, so perform the manual installer test first when possible. See Steam’s download-cache instructions.
Rank #4
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Rebuild Steam client files only as a last resort
If several Steam features are malfunctioning—not just one game’s prerequisite—Steam provides a broader client repair:
- Exit Steam.
- Open the Steam installation directory.
- Preserve
steamappsand back upuserdata. - Remove Steam client files other than
steam.exeand the preserved game data. - Start
steam.exeand allow Steam to update itself.
This repairs Steam client files, not a broken Windows VC runtime. Do not use it as the first fix for one game. Follow Steam’s client-file repair instructions precisely before removing anything.
When the runtime works but Steam keeps looping
Suppose the correct x86 or x64 package installs or repairs successfully, the game’s files verify, and the game still stops at the same message. At that point, Steam’s install-script bookkeeping may be stuck. The runtime may already be usable, but the prerequisite script is returning a nonzero result.
Rename the relevant installscript.vdf as an advanced workaround
Some Steam community reports say that renaming the affected installscript.vdf lets a game launch when its Visual C++ runtime is already installed. Possible locations include:
<Steam library>steamappscommonSteamworks Shared_CommonRedistvcredist2022installscript.vdf<Steam library>steamappscommon<Game Name>_CommonRedistvcredist<year>installscript.vdfDo not start here. First confirm that the required runtime is installed and that the manual installer completed. Then, with Steam closed, rename—not delete—the relevant file to:
installscript.vdf.bakRenaming may stop the loop, but it can also bypass prerequisite execution and bookkeeping. Steam may recreate or redownload the file, and the workaround can hide a genuinely missing runtime or another prerequisite. This is a community-reported workaround, not a normal consumer repair step documented by Valve. Examples include reports for Geometry Dash and No Man’s Sky.
Do not routinely edit CommonRedist registry keys
Valve documents deleting CommonRedist registry keys for developers testing prerequisite installation on clean operating-system images. That is not a general consumer fix. Registry editing can make Steam lose prerequisite state without repairing the underlying installer, so do not use it routinely.
Rebuild appinfo.vdf only for a stale metadata problem
Some community users report that renaming Steam’s appcacheappinfo.vdf while Steam is fully closed causes Steam to rebuild its application metadata and stops repeated prompts. This is not a documented repair for a Visual C++ installer failure. Treat it as an unsupported, advanced cache workaround:
- Exit Steam completely.
- Back up the file or rename it to
appinfo.vdf.bakrather than deleting it. - Restart Steam and allow it to rebuild the metadata.
Only try this after verifying that the runtime itself installs and the Steam client is otherwise healthy. Community reports about this method are available here.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Repair Windows Installer or Windows components
Do this branch when the Visual C++ installer itself fails, other applications cannot install or uninstall, or the error logs indicate Windows servicing or component corruption. Do not begin every Steam prerequisite problem with system repair commands.
Free tools Windows power users keep installed
One-click scans. No signup required.
If these Windows Installer or component errors affect other programs too, Outbyte PC Repair is an optional tool for an additional diagnostic and repair pass; it is not required for the Microsoft steps above.
Check for pending updates and restarts
Open Windows Update, install pending updates if appropriate, and restart. Close other setup programs before retrying. A pending reboot can leave Windows Installer unable to start the Visual C++ package cleanly.
Use Windows’ program-installation troubleshooter
For broken uninstall or cached-product entries—especially error 1714—use Microsoft’s Fix problems that block programs from being installed or removed tool. Do not manually delete registry entries or Visual C++ program folders unless a documented repair procedure specifically instructs you to do so.
Repair an installed Visual C++ entry when Windows exposes the option
Windows may expose an application repair path under Settings > Apps > Installed apps. Find the relevant Microsoft Visual C++ Redistributable entry, open its additional options, and choose Repair if that option is available. The exact controls vary by Windows version and package. The standalone Microsoft installer’s own Repair button is the preferred test for this Steam problem. Microsoft describes the general Windows app-repair paths in its app and program repair guide.
Run DISM, then SFC
Open Command Prompt as administrator and run:
DISM.exe /Online /Cleanup-Image /RestoreHealthWhen DISM completes successfully, run:
sfc /scannowRestart Windows and retry the Visual C++ installer. Microsoft recommends this order because DISM can repair the component store and provide the files SFC needs to repair protected system files. These commands repair Windows components; they are not a guaranteed fix for every Steam install-script loop. Follow Microsoft’s DISM and System File Checker guidance.
Security software, permissions, and unusual paths
Antivirus and endpoint protection
Antivirus software can quarantine game files or block a prerequisite installer. Steam acknowledges this possibility, and Microsoft also lists antivirus or corporate endpoint protection as a contributor to Visual C++ installation failures: Steam’s antivirus guidance.
Best Value
- 12-CASE PS5 GAME HOLDER – Holds up to 12 standard retail game cases in individual upright slots, keeping the collection organized and the title spines easy to read.
- FOR PS5, PS4 & XBOX GAME CASES – Designed for cases compatible with PS5, PS4, Xbox Series X, and Xbox One. Also fits many standard DVD and Blu-ray cases. Not for loose discs or cartridges.
- UPRIGHT SPINE-OUT ORGANIZATION – Divided slots keep each game box standing separately so titles remain visible and easy to select without stacking cases or searching through drawers.
- DURABLE ABS DESKTOP RACK – Made from sturdy ABS plastic for a lightweight, stable organizer that requires no assembly and fits desks, shelves, TV stands, offices, bedrooms, and game rooms.
- SPACE-SAVING VIDEO GAME STORAGE – The compact horizontal design organizes 12 cases without using tall shelf space. A practical PS5 game storage rack, video game holder, and tabletop game organizer.
Do not permanently disable protection. If safe and allowed by your security policy, perform one short diagnostic test with real-time blocking disabled, retry the trusted Microsoft installer, and immediately re-enable protection. On a managed PC, contact the administrator instead. If the security product identifies a false positive, use only its documented exclusion process for a verified, trusted location.
Run the installer elevated, not Steam permanently elevated
Running the individual installer with Run as administrator is a targeted way to test permissions. Running Steam as administrator permanently changes its security context and can create ownership or permissions inconsistencies in game folders. It should not be the standard fix.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteMove a manually downloaded installer out of a complex path
Microsoft documents a Visual C++ installation failure under some language configurations when the temporary extraction path contains double-byte characters, including certain Japanese or Chinese characters. This is less likely with a normal Steam library path, but it can affect a manually downloaded installer extracted to an unusual folder.
If the log points to this issue, move the installer to a simple folder such as:
C:TempVCRun it from there as administrator. See Microsoft’s documentation on Visual C++ runtime installation failures involving extraction paths.
Architecture and Windows-version edge cases
64-bit Windows may need x86
Many older and independent games are 32-bit applications. They require x86 Visual C++ libraries even when Windows is 64-bit. The application’s architecture—not simply the operating system—determines the required runtime. Valve’s Common Redistributables documentation describes installing both 32-bit and 64-bit packages on 64-bit systems where applicable.
The latest v14 runtime does not satisfy every old game
Visual C++ 2017 and later share the modern v14 runtime family, but Visual C++ 2013 and earlier remain side by side. If the game’s _CommonRedist folder contains a 2010 or 2013 installer, use that bundled version rather than assuming the latest v14 download will replace it.
Windows 10 support has a separate date from runtime compatibility
Microsoft’s current Visual C++ documentation lists the latest v14 Redistributable for Windows 10 and Windows 11, along with specified Windows Server releases. Microsoft also states that general Windows 10 support ended on October 14, 2025. Runtime compatibility does not mean the operating system remains supported or receives security updates. If the PC is still on Windows 10, consider the OS support implications separately from this Steam repair.
When the problem is the game rather than Steam
A one-game-only failure, particularly in an old title, points toward that game’s bundled legacy runtime or its own install script. Install the exact prerequisite in that game’s folder, check the game’s support page, and contact the developer or publisher if the installer fails only for that title.
Launching the game’s executable directly from its installation folder can be a diagnostic test: it may reveal a missing DLL, another prerequisite, or an anti-cheat error that Steam’s status screen hides. It is not a permanent replacement for launching through Steam and may not work for games that require Steam authentication, overlays, anti-cheat, or launch parameters.
Recommended Free Tools
Also remember that the status can be associated with a prerequisite phase broader than Visual C++ in some games. Steamworks Common Redistributables can include DirectX 9, .NET, OpenAL, XNA, and PhysX. If Visual C++ installs successfully but the game still does not launch, inspect the other prerequisite folders and the game’s own error message. Anti-cheat software, missing DirectX components, .NET, PhysX, permissions, and corrupted game files can produce similar launch symptoms.
A practical decision tree
- One old game is affected: run the exact legacy x86 or x64 package bundled with that game, then verify the game files.
- Many games are affected, especially on a new Windows installation: restart Windows and repair or install Microsoft’s current v14 x86 and x64 packages as appropriate.
- The manual installer shows an error: follow the matching error-code branch, inspect logs, and address Windows Installer, permissions, package corruption, updates, or security software.
- The installer succeeds but Steam repeats the script: verify the game and Steamworks Common Redistributables, then consider renaming the relevant
installscript.vdfas a backed-up advanced workaround. - Nothing installs and other programs also fail to install or uninstall: use Microsoft’s program-installation troubleshooter, then DISM followed by SFC if the evidence points to Windows component corruption.
- Steam itself is broadly corrupted: clear the download cache or perform Steam’s last-resort client-file repair while preserving
steamappsand backing upuserdata.
Frequently Asked Questions
Does this message mean Visual C++ is missing?
No. Steam runs the prerequisite installer and retries it when the process returns a nonzero exit code. The runtime may already be installed, but the bundled installer may be failing, detecting a newer package, or not updating Steam’s completion state.
Why install x86 Visual C++ on 64-bit Windows?
The runtime architecture must match the game. Many Steam games are 32-bit and therefore need the x86 package even on 64-bit Windows. If the game supplies both x86 and x64 installers, run both on a 64-bit PC.
Should I delete every Visual C++ Redistributable entry?
No. Older Visual C++ runtimes remain side by side because different games may need them. Repair the relevant architecture and version instead of removing all packages.
Is renaming installscript.vdf safe?
It is a community-reported workaround, not an official general repair. Use it only after confirming that the correct runtime installs successfully, rename the file to keep a backup, and understand that it can bypass prerequisite execution or hide a missing dependency.
The Bottom Line
Bottom line
Start with the least destructive test: restart Windows, run the game’s supplied Visual C++ installer manually as administrator, repair or install the correct x86 and x64 packages, restart again, and verify the game files. If the installer fails, its error code and log matter more than Steam’s stuck status. If the installer succeeds but Steam still loops, repair the Steam prerequisite files and only then consider the backed-up installscript.vdf workaround.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
