Rebornbuddy won't let me use plugins/botbase

Hi, first I wanted to say that because of my own stupidity I bought a license for 1 year, although I had already one going for 3 sessions. xD But I totally forgot about it, but that's beside the point: I will gladly support you guys evern further since the price is still a steal for a bot like this.

Anyway: I've been having issues on my second machine running the bot (win 7), every time I start the bot, the log tells me in red letters that it can't access a particular .dll (in my case: Lisbeth, ATB and cyril). And it tells me said function was possible in prior versions of .net framework yadayadayada.

What I've done to try to fix it: Win 7 + all updates are up to date. I installed the wizzard and checked if the rest was up to date as well. I ran as admin, I copied the bot on my Win drive, I disabled Bitdefender Internet Security 2016 etc.

Nothing, it completely refuses to run Lisbeth, ATB (botbase) and cyril. On a side note: Agil was disabled as well, however, I somehow managed to make it work, I just dunno how.

Here is the log for ATB btw (sorry, it's in German):

[10:41:39.952 D] System.IO.FileLoadException: Die Datei oder Assembly "file:///C:\Users\Molli\Desktop\RB\BotBases\ATB\ATB.dll" oder eine Abhängigkeit davon wurde nicht gefunden. Der Vorgang wird nicht unterstützt. (Ausnahme von HRESULT: 0x80131515)
Dateiname: "file:///C:\Users\Molli\Desktop\RB\BotBases\ATB\ATB.dll" ---> System.NotSupportedException: Es wurde versucht, eine Assembly von einer Netzwerkadresse zu laden, was in früheren Versionen von .NET Framework zum Ausführen der Assembly als Sandkastenassembly geführt hätte. In dieser Version von .NET Framework wird die CAS-Richtlinie standardmäßig nicht aktiviert, dieser Ladevorgang kann daher gefährlich sein. Wenn Sie nicht beabsichtigen, durch diesen Ladevorgang eine Sandkastenassembly zu erstellen, aktivieren Sie den loadFromRemoteSources-Schalter. Weitere Informationen finden Sie unter "http://go.microsoft.com/fwlink/?LinkId=155569".
bei System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
bei System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
bei System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
bei System.Reflection.Assembly.LoadFrom(String assemblyFile)
bei ATBLoader.ATBLoader.LoadAssembly(String path) in C:\Users\Molli\Desktop\RB\BotBases\ATB\ATBLoader.cs:Zeile 117.

--> System.NotSupportedException: Es wurde versucht, eine Assembly von einer Netzwerkadresse zu laden, was in früheren Versionen von .NET Framework zum Ausführen der Assembly als Sandkastenassembly geführt hätte. In dieser Version von .NET Framework wird die CAS-Richtlinie standardmäßig nicht aktiviert, dieser Ladevorgang kann daher gefährlich sein. Wenn Sie nicht beabsichtigen, durch diesen Ladevorgang eine Sandkastenassembly zu erstellen, aktivieren Sie den loadFromRemoteSources-Schalter. Weitere Informationen finden Sie unter "http://go.microsoft.com/fwlink/?LinkId=155569".

 

It's me again with a "small" update. I spent the last two days with this Problem, so here we go with my approaches:

1) I completely wiped my hdd and reinstalled Win 7 + all updates. It didn't help.

2) I bought a new Win 10 license, I swapped HDD's (i had one left with old backup files from 2012), swapped ram, installed my newely bought copy of Win 10, updated everything et voila the issue is still there. At this Point I've literally given up. Maybe it's my CPU or GPU but I just don't know what to do anymore since I won't be buy a new graphic Card just to solve this issue.

Anyway, here is a screenshot + log (attached):



And the log is attached.