Alex Ruben
How To Resolve OriginThinSetup.exe Error Caused by MSVCP140.dll or VCRUNTIME140.dll Compatibility Issue
If you’re messing around with Origin and suddenly get hit with that annoying “Code Execution Cannot Proceed” error pretty much out of nowhere while launching OriginThinSetup.exe, it’s usually due to missing or corrupted DLL files like MSVCP140.dll or VCRUNTIME140.dll. These are part of the Visual C++ Redistributables, which are like the runtime packages Windows needs to run certain apps. Sometimes, they get outdated, corrupted, or just not installed properly. The good news: fixing this often means a straightforward install of the latest or specific versions of these redistributables. Still, it can be a bit of trial and error, depending on your system and the specific error details.
Following these steps should help you get rid of that error — whether by installing missing libraries or updating the runtime environment. Keep in mind, on some setups, the error pops up only after a Windows update or if you’ve messed around with system files. So, patience is key. Anyway, here’s how to give those DLL files a proper boost.
How to Fix OriginThinSetup.exe Code Execution Errors
Download and Install Visual C++ Redistributables 2015-2022
This is the main fix. Basically, getting the latest Visual C++ runtimes ensures your system has the correct DLLs. Download from Microsoft’s official page:
- Visual C++ 2015-2022 Redistributable
- On that page, scroll down until you see options for both x86 and x64 versions. You’ll want both — some apps are 32-bit, some are 64-bit, and Windows prefers the right library.
- Click those links to download the installers. You’ll get separate files like
vc_redist.x64.exeandvc_redist.x86.exe.
Why this helps? Because these packages contain the DLL files missing or corrupted. When installed, they replace or add the DLLs your problematic app calls for. If you’re having issues, just install both, even if your system’s 64-bit — some DLLs are still 32-bit, so it’s safer to do both.
On some machines, these installers might fail the first time or give you warnings. Don’t stress — just run them again as administrator if needed. That’s often enough to get Windows to accept the new libraries.
Install the x64 Version
Deployment order can matter sometimes — installing the x64 version first might make things smoother:
- Head over to your Downloads folder.
- Right-click on the
vc_redist.x64.exefile, choose Show in Folder. - Double-click to run it. You might see a User Account Control (UAC) prompt — click Yes.
- Check the box to agree to the license, then click Install.
- Once it’s done, select Close.
Note: Sometimes, the install sticks after a reboot, so don’t worry if it doesn’t seem like it did much. Restarting can help Windows recognize the DLLs properly.
Install the x86 Version
Now, do the same for the 32-bit version:
- Locate
vc_redist.x86.exein your Downloads. - Double-click and follow the same process: agree, install, close.
This is useful because some older or specific software might still rely on 32-bit libraries, even on a 64-bit OS. Having both installed usually covers all bases.
Install Visual C++ Redistributables 2013 — Just in Case
If the error still persists, sometimes the DLLs are from a slightly older runtime. Microsoft still offers the 2013 versions, and they’re often a needed extra:
- Visual C++ 2013 Redistributable
- Choose your language, then download both x86 and x64 installers, just like before.
Again, install both by double-clicking, accepting license terms, and hitting Install. Because of course, Windows seems to keep you guessing which DLLs are missing—I mean, seriously, nothing about this is straightforward.
Complete the Setup by Restarting
After installing, a system restart isn’t a bad idea. It’s kinda weird, but sometimes Windows doesn’t fully load new libraries until rebooting. That’s the part where some errors vanish magically after a quick restart—seems to be a recurring theme in troubleshooting.
Extra Tips & Common Pitfalls
Make sure your Windows is up to date before doing all this. Outdated OS can cause DLL conflicts or prevent proper installation. Also, if you’ve messed around with your system files or registry, that can make things more complicated. Sometimes, running the Visual C++ installer as administrator helps if you hit permission issues. And if the DLL errors keep coming back, try repairing the Visual C++ redistributables via the Programs & Features control panel, or consider re-installing the problematic app completely.
Wrap-up
Basically, installing or updating the Visual C++ Redistributables tends to fix those missing DLL issues most of the time. The trick is ensuring you get the right versions—both 2013 and 2015-2022, x86 and x64—and rebooting afterward. Sometimes, the fix is as simple as re-installing a handful of runtimes, and other times it’s more about verifying system updates. Either way, it’s usually fixable without tearing your hair out.
Summary
- Download the latest Visual C++ redistributables for 2015-2022 and install both x86/x64.
- If needed, grab the older 2013 versions too.
- Reboot your PC after installations.
- Update Windows and check for system issues if problems stick around.
Fingers crossed this helps
If this gets one update moving or fixes the DLL errors, then mission accomplished. Just something that worked for a lot of folks. Hopefully, it saves some frustration and gets you back to using Origin normally.