Jamulus
3.8.0 not launching on Windows (VCRUNTIME140_1.dll not found) #1843
-
|
Jamulus was working fine until I installed 3.8. Now I get this message: The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem. I have uninstalled, restarted and reinstalled 3 times. Same message. Any suggestions? I am using Windows 10 |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 31 replies
-
|
I assume something went wrong with the installer or your Windows install is broken. Did you try a new download or 3.7.0? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply. I tried the installer on Github and also Source Forge. Downloaded from both two times. I will go back to 3.7 |
Beta Was this translation helpful? Give feedback.
-
|
Hrm, that's strange, there haven't been any deliberate changes in that area that I'd know of. @jamulussoftware/maindevelopers I noticed that we do not use pinned versions in autobuild either (not sure whether it's possible at all, either). However, this might mean we've ended up building rc2 (for example) with a different toolchain than the final version, which would not be good... I haven't spotted any major updates for Windows Server 2019 virtual environments in the past days though (although a new image was released on 2021-05-31). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I used your runtime link and did a "repair". Downloaded and installed 3.8.0 same result. Where can I find 3.7.0? All the links I've found go to 3.8.0 |
Beta Was this translation helpful? Give feedback.
-
|
I was using Jamulus for an hour when I noticed the update available message. I haven't been able to launch since installing 3.8.0 |
Beta Was this translation helpful? Give feedback.
-
Looks like it isn't: actions/runner-images#2505 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
The installer should handle everything automatically and does it on my PC & clean Windows 8.1 VM. So I think that it‘s a specific issue to @klepto84 ‘s setup. |
Beta Was this translation helpful? Give feedback.
-
|
I have tried new downloads, but can't find 3.7 to download and install.
…On Mon, Jun 7, 2021 at 2:50 PM ann0see ***@***.***> wrote:
I assume something went wrong with the installer or your Windows install
is broken. Did you try a new download or 3.7.0?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1843 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3IN2C6KAPM327Q2TQLTRUII7ANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/jamulussoftware/jamulus/releases/ |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Found it. Will stick with 3.7 for now.
Thanks again for your help. I just tested and my
midi-Focusright-Reaper setup is working again!
…On Mon, Jun 7, 2021 at 3:07 PM Peter L Jones ***@***.***> wrote:
https://github.com/jamulussoftware/jamulus/releases/
You need to scroll down.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3NWYRKXZKSWQKWS3OLTRUKHDANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks again guys for your assistance.
Going back to 3.7.0 was fine. I just had a 90 minute session with a buddy
with no issues.
I used my midi keyboard, bass, and mic during the session.
I am using the Reaper reroute function to send the 3 midi and audio signals
to Jamulus. I can also send recorded backing tracks through Reaper and play
another instrument along with my vocal.
I get the system error message at the end of the install process, when
Jamulus 3.8.0 should open. At that time, my midi keyboard is turned off
and Reaper is not active.
So I don't think my audio routing is impacting the situation. I updated
Runtime as per the previous message. Can you suggest anything else I
should try? I don't want to be stuck in 3.7.0 time warp forever as I
expect Jamulus is here to stay and will only get better!
Thanks again!
…On Mon, Jun 7, 2021 at 4:18 PM ann0see ***@***.***> wrote:
The installer *should* handle everything automatically and does it on my
PC & clean Windows 8.1 VM. So I think that it‘s a specific issue to
@klepto84 <https://github.com/klepto84> ‘s setup.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3PER2BZMS2E35L2S73TRUSSRANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Yes sure! You shouldn’t need to stay on an old version. I still have the impression that something is wrong with your OS/Installation. Maybe we can compare if all necessary files are there. Did you also try to remove and install the runtime again? |
Beta Was this translation helpful? Give feedback.
-
|
Here you go.
…On Mon, Jun 7, 2021 at 5:08 PM ann0see ***@***.***> wrote:
Yes sure! You shouldn’t need to stay on an old version.
I still have the impression that something is wrong with your
OS/Installation.
Could you please take a screenshot of the Jamulus folder im program files?
Maybe we can compare if all necessary files are there.
One option (which is always the last option) might be an implace update of
your OS (with all your data and programs backed up before doing so). This
might install missing files again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3IPQELCSKMLHBRFVYTTRUYOHANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Could you please upload pictures on the web interface (#1843)? I can’t see anything since you sent an e-mail. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I uploaded the screenshot to Github, but the interface looks like 1980's MS
DOS and I'm not sure if you will be able to open the file.
…On Tue, Jun 8, 2021 at 1:02 AM ann0see ***@***.***> wrote:
Could you please upload pictures on the web interface (#1843
<#1843>)? I can’t
see anything since you sent an e-mail.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3JXEBGIM5XG2RILVKDTRWP6XANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
After re-installing 3.6.2 , testing and re-installing 3,8,0 , Jamulus can't launch , giving a different missing Windows components (MSVCP140_1.dll) , Ref. |
Beta Was this translation helpful? Give feedback.
-
Repeat until there are no versions of exactly that Redistributable installed. I had two at one point. Then use the 3.8.0 installer. That then worked for me. |
Beta Was this translation helpful? Give feedback.
-
|
@pljones You may have seen in
Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
@pcar75 , CONCRT140.dll is also part of the Microsoft Visual C++ 2015-2019 Redistributable x64. I have not experienced yet that I need to reboot between any of these steps. EDIT: Forgot to mention, you can remove (or rename) the Jamulus folder in the Program Files folder before installing jamulus. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks All ! Just to be on the safe side, I ran MS support suggestions in a CMD admin window :
Then I
Now , neither Jamulus nor Cakewalk miss anything ; that problem solved ! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks!
…On Tue, Jun 8, 2021 at 12:15 PM Henk De Groot ***@***.***> wrote:
i have noticed this issue myself as well on 1 of my Win10 machines. I
resolved this by manually removing the "Microsoft Visual C++ 2015-2019
Redistributable (x64) - 14.29.30037" from my installed programs. After this
downloaded it from microsoft and manually installed and now it is working.
Jamulus (and possible other programs) just can't find the VCRUN...dll in
any of the paths windows is aware of. After removing and installing again,
the dll is added back into the system32 folder. On my system it was no
longer in that folder. Other programs failed to work as well on my system.
The repair method in the vc-runtime, seems to not work correct and when
jamulus is installed and finds it is already in the installed programs, it
will skip the installation.
More investigation to be done to find the actual cause....but at least
wanted to share a way to resolve the issue and use 3.8.0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3NFNTR67TLSOS3A7V3TRY635ANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
First of all I am the Reaper guy and to make sure we have our facts strait.
I have been routing my midi keyboard M-Audio Hammer88 Pro, and both
channels of my Scarlette through Reaper to Jamulus with no issues. I also
have a backing track channel and multiple midi instruments successfully
ASIO4ALL is not part of the set up. It was working flawlessly until I
installed 3.8.0. For the record Reaper was not involved in the install and
the keyboard was powered down. My routing has nothing to do with this
issue. So to be clear. I am not "trying to connect.....etc" I have been
connecting.
I was unable to launch Jamulus 3.8.0 so I never tested the routing. I
reinstalled 3.7.0 and my Reaper routing is working great!
I plan to hang with 3.7.0 until the bugs are worked out and try again in a
few months.
…On Tue, Jun 8, 2021 at 2:56 PM pcar75 ***@***.***> wrote:
@henkdegroot <https://github.com/henkdegroot> :
Bonjour, I'm thinking of waiting a bit before migrating (from 3.6.2) to
3.8.x ...
1. Two players also mentioned problems with Windows 10 and 3.8.0 , but
one of them was also trying to connect to Reaper through ReaRoute (with
Jamulus and a Focusrite audio interface + ASIO4ALL ?! )
2. Yesterday, our drummer easily installed 3.8.0, but on his Windows
7Pro (64b) laptop (no DAW or MIDI connection)
3. In case VCRUNTIME*.dll is a problem , I wouldn't know where to put
it. On my Windows 10 -regularly updated-
- A CMD/DOS 'dir' shows 33 occurences of VCRUNTIME*.DLL
- An Explorer 'search' shows 35 of *VCRUNTIME*.DLL
- Most have different file size and 32b and 64b are peppered all over
my program drive including \Windows\System32, \Windows\SysWOW64,
\Windows\WinSxS, \Program Files and \Program Files (86), ...
(Aarrgghh ! don't you love bloated software :-/ ... I haven't worked
up the courage yet to low-format and reinstall everything (probably weeks) .
So what would be the best directory to put in in ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3JV5NHFBKSD32HKOALTRZRULANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
@klepto84 |
Beta Was this translation helpful? Give feedback.
-
It should not be a problem at all for you to stick with that version, when it works fine for you. At the moment I don't think this is a Jamulus problem but more a Windows related issue. When I hit the issue, I had previously removed many programs, so not sure which program made my "visual studio runtime" corrupt. Not all programs are as nice when it comes to uninstalling and they remove items they should not. Jamulus only installs/upgrades the runtime during the installation and is not removing it when Jamulus is removed. It would be good to know if your issue can also be fixed by doing a manual remove/install of the visual studio runtime. Even the re-install of Jamulus may have resolved that issue as well and the next upgrade to 3.8.0 might be without any issue. |
Beta Was this translation helpful? Give feedback.
-
|
No worries!
…On Tue, Jun 8, 2021 at 6:21 PM pcar75 ***@***.***> wrote:
@klepto84 <https://github.com/klepto84>
Oopps ! Sorry for the misunderstanding !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1843 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASIGQ3OD4WRLNDWTMWSMXPLTR2JV5ANCNFSM46IG5WMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Bonjour @klepto84 , |
Beta Was this translation helpful? Give feedback.
-
|
I tried to pin this down earlier this evening. My installs had been of release artifacts - not from the autobuilds. I had no problem with 3.8.0 release. I had a problem trying out the PortAudio autobuild. Re-installing 3.8.0 releases didn't fix it - I had to manually uninstall the VC++ Redistributable and then install 3.8.0 again. At that time, installing the PortAudio build immediately caused the problem again. When I tried to pin the issue down, however... I couldn't reproduce it reliably. I had reverted to 3.8.0, tried the PortAudio build, got the error, tried other builds without success. Then uninstalled the VC++ Redistributable and installed 3.8.0 to confirm that still worked. Then the latest PortAudio build worked, too, when overwriting it. What I've not tried again is
It may be some intermittent download error. I've had a Windows Update that's been failing for ages lately:
whereas
|
Beta Was this translation helpful? Give feedback.
-
|
Had a similar problem with a choir member I helped which could be solved by following the instructions by @pcar75
|
Beta Was this translation helpful? Give feedback.
-
|
I've since run one of the Microsoft updater clean up tools (dsim and sfc not having resolved my MS update issue) and not had the problem since, so I think it might have been a combination of a duff install of "Microsoft Visual C++ 2015-2019 Redistributable (x64)" from somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
I am told that there could be an issue with the link below. I did not have an issue with it. Fix #3 did work for me. You can avoid the link by following the directions at the bottom of this message. I had this same problem with 3.9. The solution listed as Fix #3 in this post: https://techloris.com/vcruntime140dll-is-missing/ (Repair Microsoft Visual C++ Redistributed) worked for me. Follow these directions and you will not need to go to the link. The link suggests (in Windows 11) run Control Panel | Programs | Programs and Features | Right-click the Microsoft Visual C++ Redistributable appropriate to your system (32 or 64 bit OS setting) and Select Change | Repair. |
Beta Was this translation helpful? Give feedback.
-
... just to post a link to a site for ResToro... yes, the post here does sound like an ad - I'd be inclined to delete. |
Beta Was this translation helpful? Give feedback.
-
|
No, I wouldn't delete it as @rtrial can also be a normal person. We must stay transparent and not abuse admin powers. Rtrial doesn't promote option 1 which is the program in question. They have just found a somewhat sketchy site. So my suggestion would be that @rtrial, you edit your message and add a disclaimer that the link might lead to a biased article sounding like an ad. If you don't with a reasonable time, we'll add one. If the tip works, it's still ok. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
Thanks again for adding the disclaimer. |
Beta Was this translation helpful? Give feedback.
I tried to pin this down earlier this evening.
My installs had been of release artifacts - not from the autobuilds.
I had no problem with 3.8.0 release.
I had a problem trying out the PortAudio autobuild.
Re-installing 3.8.0 releases didn't fix it - I had to manually uninstall the VC++ Redistributable and then install 3.8.0 again. At that time, installing the PortAudio build immediately caused the problem again.
When I tried to pin the issue down, however... I couldn't reproduce it reliably. I had reverted to 3.8.0, tried the PortAudio build, got the error, tried other builds without success. Then uninstalled the VC++ Redistributable and installed 3.8.0 to confirm that still worked. Then …