Msvcp140_atomic_wait.dll Was Not Found
Sanora Ngueyn
Errors related to msvcp140_atomic_wait.dll can arise for a few different different reasons. For instance, a faulty application, msvcp140_atomic_wait.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.
In the vast majority of cases, the solution is to properly reinstall msvcp140_atomic_wait.dll on your PC, to the Windows system folder. Alternatively, some programs, notably PC games, require that the DLL file is placed in the game/application installation folder.
Do you have information that we do not?
Did our advice help or did we miss something?
Our Forum is where you can get help from both qualified tech specialists and the community at large. Sign up, post your questions, and get updates straight to your inbox.
Download msvcp140_atomic_wait.dll file for free for the Windows platform. This DLL is produced by Microsoft Corporation. There are currently 2 versions available and the latest version is v14.29.30037.0.
If a program or game requires msvcp140_atomic_wait.dll, then Windows will check for the .dll file before launching the program. If any issue is detected, it will display an error and the program won't launch. A few examples of the errors are:
- This application failed to start because msvcp140_atomic_wait.dll was not found.
- The program can't start because msvcp140_atomic_wait.dll is missing from your computer.
- There was a problem starting msvcp140_atomic_wait.dll. The specified module could not be found.
- The file 'msvcp140_atomic_wait.dll' could not be loaded or is corrupt. Setup cannot continue.
- The code execution cannot proceed because msvcp140_atomic_wait.dll was not found. Reinstalling the program may fix this problem.
- msvcp140_atomic_wait.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vender for support.
These errors are displayed when this DLL file is missing from your PC, has issues, or that it is corrupted. In such cases, the solution is to reinstall the DLL file on your computer or place it in the program or game that requires it.
There are two ways in which you can install this DLL file on your computer. You can either copy the file to the installation folder of the application that requires the DLL or register it using Microsoft REGSVR. Here are the instructions for both the methods:
Yes, you should re-distribute the CRT redistributable with the application in addition to the Swift runtime. The reason for this is that there is an implicit dependency on the VC runtime (that is the equivalent of libSystem or glibc on macOS or Linux respectively). Although, you could always redirect the user to install that from Microsoft if you wanted. The local packaging or dependency addition in winget packages avoids the need for the user to manually install that dependency.
Update: There is an inaccuracy in the above paragraph: Within a given installation of Visual Studio you could install different C++ Runtime versions, so at least to some degree they are independent of the Visual Studio versions, and we talk about the C++ Runtime versions of course.
Unfortunately, there is no "simple" way, at least in the sense of "here is a one liner". It is generally quite straight-forward, if tedious. link -dump -imports findstr \\.dll should identify the imported DLLs, but this needs the transitive closure technically. That will give you full set of DLLs that are in use, and reducing that down the msvcrt/msvcprt should be straightforward.
Hi all, summoning @compnerd and @sspringer to see if anything has changed DLL-wise with 5.8. I see dynamic ICU has been removed. Has anything else changed dependency-wise if loading a compiled swift DLL side by side with copied VCRedist and Swift DLLs (copied from "C:\Program Files\swift\runtime-development\usr\bin")
I'm running into an issue loading my swift 5.8 compiled DLL with side by side swift 5.8 dlls and vcredist (loaded via LoadLibraryEx) with only LOAD_LIBRARY_SEARCH_DLL_LOAD_DIR set, when my 5.7.3 DLL loaded just fine. Getting a generic "The specified module could not be found." error.
Just as a disclaimer: I am not involved in the development here but have only given some info. ICU has been changed to static linking as reported in the according blog entry. Concerning the error maybe @compnerd can give some answer. Maybe it is because the vcruntime module has been renamed to visualc (also mentioned in the blog entry).
What about licensing issues, I think ICU uses the Unicode license so I think this license file should be part of the Swift distribution (?) and then what about Swift programs using static linking (not yet ready on Windows).
I like the idea of including the license file in the packaging. Would you be willing to help with arranging this? We should be able to install the file into usr\share\docs. We should be able to do this with the runtime which would mean that anyone using the runtime redistributable implicitly gets it redistributed, which might make it easier?
IANAL, so this is definitely stretching my knowledge (quite) a bit. I think that because the dependency is indirect and the runtime could package the license file, so it should be just a matter of the application bundling up all the files in the redistributable. Please apply a generous helping of salt, this is not my area of expertise.
I cannot read a crash log beyond skimming it for info I recognize to follow up on, but I do have some pointers that may help. First, you'd probably find more help if you posted in the specific game forum for help -welcome/ whether it be SE. LE, etc. You will find more people with the specific game knowledge. I just 'happened' to see this myself. There is a lady member there that can read a crash log and helps any poster she finds, that is for the SE forum, as I don't use anything else so not sure if she is in other areas or not.
Next, a CTD is usually a sign that the pc cannot find info it needs, hence a missing master or patch. IDK what you are using for a MM, but some warn if you are missing a master. If a patch in LO is placed before any of the mods it patches, that will cause a CTD. Search through your LO and verify all patches come after every mod they patch, UNLESS the mod author specifically says to put it before said mods. Verify that on the mod page and in its posts section.
Another is sometimes having X mods require a patch or they will crash, not just not display X or allow Y. Usually, and again, this will be covered on the mod page and or in its posts section. The next check to recommend is to run LOOT. If that combo is known about and not in your LO, LOOT will flag it for you to review.
I'd also suggest you verify your skse plugins' status to the wiki log here -plugins Do note though, I have found some discrepancies in that list. Meaning, some it says are incompatible, I found worked.
You gave no history of your situation like if you had the mod build working or not; did you download 1200 mods without testing and turn it all on; OR did you even test if skse is working, so if you didn't do that, and can get to the load screen, do so also for a check.
If none of that proves fruitful, start at the bottom of your LO and turn mods off in groups of 5 to 10 and test. If the problem still exists, do not turn that group back on. Proceed to turning off the next batch and test again. Eventually you will turn off the group the problem is in. Once that happens, one by one, turn each of that group's mods back on testing after activating each. When the problem returns, that is a point to the problem. It could just be an out of date mod, etc or that could be the last in X amount of mods that needs a patch, OR various other reasons the more one has to go down the rabbit hole. Those possibilities usually cover a greater percentage of the possibilities though. Once you identify the mod, follow up on it as said above. Read the mod page, its posts, AND all related mods to it. If nothing turns up, then don't use said mod, OR learn how to make it work
Also, good idea to post long logs, load orders, etc. either inside a spoiler ("" button on the post box) or linked on another site (e.g., Pastebin). Either way, it's less to scroll past if someone is skimming the thread before they dig into it.
I just recently got Adobe Photoshop and with that i need to have Creative cloud to download it but when i download creative cloud and try to open it up all it says is "The code execution cannot proceed because MSVCP140.dll was not found. Reinstalling the program may fix this problem." but i tried reinstalling and the same message came up and it keeps telling me this. I do not know what i am doing wrong or how to fix this error.
Do you have all the latest upgrades for Windows 10? I ask because the latest Visual C++ runtime is usually pushed out by Microsoft when you upgrade your Windows operating system. If not, then you'll need to install Visual C++ manually from the link John T Smith posted above.
Find the lastests install for Microsoft Visual C++ and repair them. It should do the trick, but I'm not sure if repairing only the lastest version is enough so, don't hesitate to repair one or 2 previous versions too.
Just had the Same issue a few hours ago. Found this thread but just to be on the safe side i uninstalled and reinstalled all the x64 versions. It doesnt take long to do them all at all as the programmes are small. 5mins for all 3. Then i rebooted the system and then reinstalled Adobe. All works fine now.
Thank you! Deleting all of the x64 versions and reinstalling the latest one worked for me too. It wouldn't allow me to uninstall Adobe originally and repairs for the x64 versions made no difference. I'm so glad you made this suggestion!
03c5feb9e7