SysInfo plugin v0.1.2.9

[LeXXuz]

That may be the cause. I have 10.0.40219.325

Any trustworthy source where to get the correct version?
I don't trust all those sites offering dll downloads.

[Reel.Deel]

Here's the official 2010 Redistributable Package: https://www.microsoft.com/en-us/down....aspx?id=26999
However, the AIO package is highly recommended: https://github.com/abbodi1406/vcredist/releases

[LeXXuz]

Originally Posted by Reel.Deel

Here's the official 2010 Redistributable Package: https://www.microsoft.com/en-us/down....aspx?id=26999

I'll give that a try.

[kedautinh12]

Originally Posted by LeXXuz

I'll give that a try.

Why you don't use this package?? I seen you had many error and i hadn't like you with this package
https://github.com/abbodi1406/vcredist/releases

[StainlessS]

abbodi1406's All-In-One package cuts out a lot of the "housekeeping" files supplied with each runtime installer,
only needs 1 set for the whole lot of runtimes, and so is quite a lot smaller in size.
I've never had any problems at all with them.

And very regularly updated (a few days after M$ updates, maybe monthly).

[Emulgator]

Just copying the .dll to system32 will do.
IIRC, I got mine from a choice of shady sites too. I compared, tried the reasonable and it worked.
(Dependecies/walkers will help a bit here, too)
What Abbodi has in its recent package, maybe you just run it and see, it should report before making changes.
BTW, I remember certain later versions of .net 3.5 being a big culprit of incompatibility with (then Sony) Vegas and siblings.

Shit !!!
Just now I ran abbodi 0.64 to test for you guys and it starts all MS installers without asking.
I tried to cancel and stop the modern ones, but in this very moment the old installers run and run and I can not stop them.
Damn. I am fucked. All that countless hours of handmatching those pesky .dlls.
Damage done. Never again, Abbodi. I will hate my helpfulness after I reboot...

Now rstrui to the rescue...Fortunately there are 34 restorepoints, in 11 minutes.
Rolling back as we speak...

[LeXXuz]

Same here. In my desperation I also tried that installer and it installed a shitload of redists I didn't want. Now several other programs and filters stopped working on my system.

[Emulgator]

Writing from my second system now.
LeXXuz, you may try Win+r -> rstrui.
I hope that you can find good restore points.
I went a week back to be safe. Still running---

Once I am back and running I shall post that .dll somewhere for you guys.

And which was the nice runtime installer that reported via GUI what it had found,
and what it offered, and gave room for interaction ?
Sereby, IIRC. Or did earlier Abbodi have a GUI ?

[Emulgator]

I am screwed deeper than I thought. The rollback did not undo the damage.
Of 3 scripts CQTGMC, QTGMC, QTGMCp I had working: none started, all failed.
Reinstalling the Groucho did not help.
Worse: I am locked out of my Vegas 14, it can not start up anymore. Vegas 13 does.
Not trying all my SWs now...,I am down to my knees...
Reversing the rollback now and trying later restore points...

[kedautinh12]

If you want install abbodi build clean. First install need unistall all vc++ already in computer via program -> unistall. After first install abbodi build, second and after abbodi build don't need do it again

[Emulgator]

After first install abbodi build, second and after abbodi build don't need do it again

I fail to see how this suggested sequence could help getting the old matching locks back into their doors...

ked, abbodi just installs the newest builds over the older ones by uninstalling the older ones.
And "undo" is definitely not working as expected, I am still searching for the remnants,
rstrui brings only shiny latest versions up, I can not find my version 10.0.30319.1
Are these destroyed ?
What leaves me with often incompatible versions, all painstakingly matched relations are gone.
I had let in the new locksmith by suggestion, so without further asking he unmounted the old locks from their doors,
took them away

I am left with new locks, old keys, and these old keys can not be updated, because the old locksmith is gone.

[LeXXuz]

Originally Posted by Emulgator

I fail to see how this suggested sequence could help getting the old matching locks back into their doors...
ked, abbodi just installs the newest builds over the older ones by uninstalling the older ones.
What leaves me with often incompatible versions, all painstakingly matched relations are gone.
Old locks unmounted from their doors, taken away by the new locksmith and destroyed.
I am left with new locks, old keys, and these old keys can not be updated, because the old locksmith is gone.

Well said.

[Dogway]

@Emulgator, do you keep backups? Check what VC++ you had before and install back one by one (CCleaner or Geek might keep registries). Another option is to run Everything and check for "vc_redist", often these files are stored along the installed programs, so you can reinstall them back.

On the bright side, think what favor you did to all of us, I was wondering if that package was useful or not, now I know ^^

[Emulgator]

Yes, I have backups of almost everything.
All rstrui attempts did not bring back the structure i had.
So uninstalled all runtimes manually, then let Abbodi 0.64 do its ....rrrrr....work again.
manually copied only x64 10.0.30319.1 into system32.
Got some S/W up (Avisynth and so) and running again,
but Vegas 14 still refuses to start up, tells me Error -59 before splash screen and "You have no license..."
(sheesh, I bought everything from 8 to 16) and won't offer inputting my license data anymore, just closes after that message.
Tonight, tonight, ♫♪♬♩ and I won't eat...

[StainlessS]

Just copying the .dll to system32 will do.
IIRC, I got mine from a choice of shady sites too. I compared, tried the reasonable and it worked.
(Dependecies/walkers will help a bit here, too)
What Abbodi has in its recent package, maybe you just run it and see, it should report before making changes.
BTW, I remember certain later versions of .net 3.5 being a big culprit of incompatibility with (then Sony) Vegas and siblings.

Only update C Runtimes, + VB Runtimes if necessary and Office Runtimes too, no DotNet.

[Emulgator]

Solved.
1. Shift Vegas 14 installations folder somewhere else.
2. Find the Vegas 14 Installer regkey (different for every language it seems), export somewhere else, then delete in Registry.
3. System control -> Programs -> Vegas 14 -> Uninstall -> Ofc. "Could not find installation", but Windows finally deletes orphaned entry.
4. Now a Vegas 14 reinstall is possible.
5. Start Vegas 14: still blocked.
6. Uninstall Vegas 14 as in 3, now successful.
7. Reinstall Vegas 14 again.
8. Vegas finally comes up with License screen.
9. Input License -> accepted, starting to work.
10. Fortunately my settings were still there, no need to copy installation folder content back.