Fully uninstalling AviSynth

[TCmullet]

I've used Avisynth for about a decade, though not being an expert. I think I have numerous versions on each PC I have. What is a sure-fire way to fully uninstall all traces of all versions of Avisynth so that I can start from scratch with the current version? Yes, old scripts may break, but in most cases, I won't ever run them again. I want to write new scripts for new video projects, yet all my "skeleton" scripts have lots of stuff (now junk code) that was special or tailored for special versions or situations.

[StvG]

1. If you installed any version from installer use the uninstaller.
2. Search in C: for avisynth.dll and delete any result.
3. Open the Registry Editor. Navigate to Computer\HKEY_CURRENT_USER\Software and delete any Key with name AviSynth.
Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE and delete any key with name AviSynth.
Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node and delete any key with name AviSynth.
4. Make backup of all avs plugins then delete them (including any AviSynth/plugins(+)(64)(64+) folder).

[TCmullet]

Thanks, StvG. The steps you gave mostly fit with the kind of things I expected one would need to do. But I didn't want to do guesswork about the registry stuff.

However, I'm a bit puzzled by step 4. Those folders are various avsi and dll plugins I've acquired (or in a few cases written) over the years. What is the reason those should be deleted? After I install the most current Avisynth, I'll be using a lot of them again, so why delete? Does it have to do with WHERE the more current Avisynth version will be expecting them?

[StainlessS]

Delete them and then once re-installed, add them back (from the backup you made) as and when you need them.
(maybe one of them will break the install, so best to find out which)

[Emulgator]

BTW, TCmullet, you don't need to delete any scripts and plugins.
StcG just responded to your demand to "fully uninstall all traces".

And you can have some AviSynth versions as you like side-by-side,
being 2 (one 32 and one 64bit) at the same time.
See Groucho's Universal AviSynth installer.
https://forum.doom9.org/showthread.php?t=172124

Later you may swap your plugins and scripts in and out of these installations manually with Windows Explorer,
they are loaded next on invocation of that particular AviSynth Installation(s) you decided for.

This gives room on your side to keep anything as-is and on demand flipping over to a new install on the fly, just by calling the Groucho script.

There is no real "install" of plugins in registry to be cleaned,
just the path(s) to plugins folder(s) to be parsed on any invocation of installed (yes, these are installed) AviSynth(s) (32 or/and 64).

[TCmullet]

This all worked on the machine I was targeting when I started this thread. But now I'm "upgrading" another PC. I don't prefer to totally uninstall avisynth this time, but thought I could simply remove all copies of avisynth.dll, copy the two correct Avisynth.dll files to the \windows\system32 and \windows\sysWOW64 folders respectively (being careful to get the right version in the right folder), and delete all references to "avisynth" from the registry. (And reboot.)

But version.avs STILL reports 2.60, instead of 3.7.3 which is the version of the dlls now present. What could possibly be "keeping this at 2.60"?

[poisondeathray]

If you recall, you had a similar problem before with a rogue avisynth.dll version hiding in a vdub directory on a non C drive . So when using vdub to open avs script , it loads the rogue avisynth.dll version

Again, clean out all avisynth.dll versions. All of them, in all paths . You're likely have another rogue avisynth.dll that you missed

http://forum.doom9.org/showthread.php?t=185489

[TCmullet]

If you recall, you had a similar problem before with a rogue avisynth.dll version hiding in a vdub directory on a non C drive . So when using vdub to open avs script , it loads the rogue avisynth.dll versionYeah, thanks. I had forgotten. (Hazard of being 70.) What's even funnier was that my current Agent Ransack HAD found the Vdub, but I forgot that Vdub merely executes from where I have the file copied, rather than getting installed. Therefore by executing Vdub from the folder I downloaded it to (which also had an avisynth.dll), it loads the rogue dll. Sorry. And again, thanks! Correct version number shows now that the 2 sys versions are the only ones accessible.