<p>As the docs indicate, you have to create registry keys to tell Avisynth+ where to look. They are</p>

<pre><code>PluginDir+ in Software/Avisynth in HKEY_CURRENT_USER
PluginDir+ in Software/Avisynth in HKEY_LOCAL_MACHINE
PluginDir2_5 in Software/Avisynth in HKEY_CURRENT_USER
PluginDir2_5 in Software/Avisynth in HKEY_LOCAL_MACHINE
</code></pre>

<p>There is no separate key for 32 or 64-bit. Since 32-bit AVS will not load 64-bit plugins, I suggest setting the first key in the above list to the 64-bit plugins folder, and the 2nd to the 32-bit. The 64-bit AVS DLL when loaded will use plugins from the first folder. The 32-bit DLL will skip them and load from the 2nd folder.</p>

CC BY-SA 3.0
2017-02-23T16:01:48.887Z
Thank you again - now **both** `64-bit` and `32-bit` autoload directories are recognized by `AviSynth+', so **all things work**.
MarianD
CC BY-SA 3.0
2017-02-23T05:38:28.677Z
2017-02-23T05:38:28.677Z
Gyan
<p>I installed anew version of <code>AviSynth+</code> and besides solving some problems with its <code>DirectShowSource.dll</code> I discover (from the <code>Setup Log</code> file) that it consider <code>C:\</code> as its autoload directory.</p>

<p>It helped me - I copied <code>DLLs</code> there. But it is neither elegant nor useful solution (as I have installed both 32- and 64-bit versions).</p>

<p>How to change configuration to return to default <code>plugins+</code> and <code>plugins64+</code> directories?</p>

CC BY-SA 3.0
2017-02-22T20:58:29.573Z
Consult the [docs](http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B.27s_Plugin_Autoloader).
Gyan
CC BY-SA 3.0
2017-02-22T22:25:55.307Z
@Mulvya: Thank your for your valuable advice. I followed your link and created appropriate registry keys and for 32-bit **it works**! - If you will write it in the form of an answer, I will accept and upvote it.
MarianD
CC BY-SA 3.0
2017-02-22T22:27:56.237Z
@Mulvya: Do you know, please, what to do with 64-bits plugins? I tried guess the name of the key from 32-bit version name( `PluginDir+`), e. g. `PluginDir64+`, but without success.
MarianD
<plugins><script>
How to change AviSynth plugins directory?
MarianD
# How to change AviSynth plugins directory?

(Asked by: username_0 on 2017-02-22)

I installed anew version of `AviSynth+` and besides solving some problems with its `DirectShowSource.dll` I discover (from the `Setup Log` file) that it consider `C:\` as its autoload directory.

It helped me - I copied `DLLs` there. But it is neither elegant nor useful solution (as I have installed both 32- and 64-bit versions).

How to change configuration to return to default `plugins+` and `plugins64+` directories?

**Tags:** plugins, script

> **Comments:**
> **username_1**: Consult the [docs](http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B.27s_Plugin_Autoloader).  
> **username_0**: @Mulvya: Thank your for your valuable advice. I followed your link and created appropriate registry keys and for 32-bit **it works**! - If you will write it in the form of an answer, I will accept and upvote it.  
> **username_0**: @Mulvya: Do you know, please, what to do with 64-bits plugins? I tried guess the name of the key from 32-bit version name( `PluginDir+`), e. g. `PluginDir64+`, but without success.  

---

## 1 answers

### Answer by username_1 on 2017-02-23. Score: 1 | Accepted answer

As the docs indicate, you have to create registry keys to tell Avisynth+ where to look. They are
PluginDir+ in Software/Avisynth in HKEY_CURRENT_USER
PluginDir+ in Software/Avisynth in HKEY_LOCAL_MACHINE
PluginDir2_5 in Software/Avisynth in HKEY_CURRENT_USER
PluginDir2_5 in Software/Avisynth in HKEY_LOCAL_MACHINE

There is no separate key for 32 or 64-bit. Since 32-bit AVS will not load 64-bit plugins, I suggest setting the first key in the above list to the 64-bit plugins folder, and the 2nd to the 32-bit. The 64-bit AVS DLL when loaded will use plugins from the first folder. The 32-bit DLL will skip them and load from the 2nd folder.

> **Comments:**
> **username_0**: Thank you again - now **both** `64-bit` and `32-bit` autoload directories are recognized by `AviSynth+', so **all things work**.  

---

