Software Microsoft Visual C++ problems

Hermann Oberth

New member
Joined
Jan 30, 2010
Messages
25
Reaction score
0
Points
0
It is actually a Windows problem. But since weeks I don't get this right.

Can anybody tell me wich Visual C++ files I have to install?
Currently I've deleted both 2015 (x86) files, but he don't want to eat the 2015 (x64) files.
 

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
1,486
Reaction score
18
Points
38
NONE of them should be deleted!
Any add-on (or other program) might depend on any of those.
You should never have to delete (uninstall) any redistributeable!

What add-on (or program) depends on what version of the runtimes is not always clear, sorry.
 
Last edited:

Hermann Oberth

New member
Joined
Jan 30, 2010
Messages
25
Reaction score
0
Points
0
Well, Microsoft Visual C++ 2015 Redistributable (x64) - 14.0.23026 told me to uninstall this version first, befor I can install it! Now I uninstall the x86 version and x64 still don't want.
Anyway, there is more of this missing since my reinstallation.
Some got in by win-update. Some not.

I actually have no problems with orbiter, but with windows "drivers".
...
- I reinstall Microsoft Visual C++ 2015 Redistributable (x86) - 14.0.23026 now!
 
Last edited:

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
35,548
Reaction score
64
Points
138
Location
Wolfsburg
Its important to know, that the runtimes for 2017 don't replace the runtimes for 2015. They are better treated as distinct entities, even if you can sometimes run a C++ program for 2015 with a 2017 runtime. Usually it doesn't.

And if you need a 32 bit runtime or a 64 bit runtime depends on the application that you run. A 32 bit runtime can't run a 64 bit program.
 

Hermann Oberth

New member
Joined
Jan 30, 2010
Messages
25
Reaction score
0
Points
0
I think you're right:
https://pastebin.com/Gd8BB2Cw
This protocoll say so.

Should I uninstall the 2017 version? And then install 2015?

---------- Post added at 09:37 PM ---------- Previous post was at 09:27 PM ----------

Yeah, 2017 out - 2015 in, was working! I missunderstood this with x86/x64.
Now my 2010P1 is just jelling for GenericCamera.dll.
Any suggestions for that problem?
 
Last edited:
Top