probllem about microsoft visual c

users
#1

you're right; I was wrong.

       These updates are quite necessary if one is on-line with the program.

#2

Hi :slight_smile:
If something is working well for you it is difficult NOT to recommend it to
others!

However it is better to use more current versions and try to stick to
either the current "Fresh" or "Still" branches. There seems to be about 1
genuine security issue per year (rather than the handful per month of the
main competition's suite). Although these are usually dealt with before
becoming rampant out in the wild it is still probably better to avoid
potentially putting yourself at risk. "Security through obscurity" is only
kinda good when it's one of many strands keeping you safe.

A quick google search for "microsoft visual c runtime library runtime
error. 6025 pure virtual function call." gave me a couple of links on the
Microsoft.com website and a few others. Interesting to see at least a
couple refer to it potentially being due to missing libraries and a quick
glimpse suggested the processes for fixing the problem looked very
similar. I'd take each suggestion "with a pinch of salt" but they seem to
build-up to, potentially, a better understanding.

Errr, apparently "6025" was a 'name' of a member of the band "The Dead
Kennedies" and the number appears to have been used as a reference number
for quite a lot of very dissimilar things too.
Regards from
Tom :slight_smile: