MFreebundle (new) not registering in DAW

[goldglob]

Another longshot possibility.
My understanding:
Sometimes REAPER 'blacklists' a plugin. I don't know why or what this involves but sometimes this blacklisting is due to a glitch and not actually necessary. Trouble is that once blacklisted REAPER won't load it, even after a Clear cache/re-scan.
The blacklisted plugin displays in a certain way in REAPER's resource path.
Options > Show REAPER resource path in explorer/finder
Close REAPER.
In the resource path find the file 'reaper-vstplugins64.ini'. This is actually the 'cache' that gets cleared and re-populated when you 'clear cache/rescan' in preferences.
Open it (usually just in the same way you'd open a text file).
Find a Melda plugin in question, let's say MTremolo.vst3
If the plugin has not been blacklisted it will appear as:
MTremolo.vst3=657CEBECA4E6D501,1326722673,MTremolo (MeldaProduction)
The actual string of digits might be different to what you see, doesn't matter, the relevant thing is that if the text after the digits is missing then the plugin has been blacklisted.
Check this for all plugins in question.
Delete those entries (make a copy of 'reaper-vstplugins64.ini' first and put it somewhere safe to be moved back if necessary).
Open REAPER. The usual startup scan might now pick up the plugin.
You might think, hang on, wouldn't clear cache remove all entries anyway? I've got a feeling that it only removes entries that make sense to it? Anyway, I have solved problems similar to what you seem to be having by doing the above.
If all this seems too complicated I wouldn't blame you!
EDIT: Thinking more about it, I'm wondering whether just removing the 'reaper-vstplugins64.ini' would achieve the same thing...a subsequent scan would re-create a populated file (hopefully without the glitch)?
I'd be interested to hear what others think of this as well.
DarkStar?
Vojtech?

[DarkStar]

Nope, I'm stumped.

[goldglob]

Nope, I'm stumped.

Me too, ah well, back to the global meltdown.

[WarBeer]

@goldglob...I did as you suggested on all accounts. No change...but it did raise a question for me. How should the VST3 vs VST look in that list? The Melda stuff was listed with the (x86) suffix. I "thought" I remembered the Melda install putting the VST in the "Program Files" tree and the VST3 in the "Programs Files (x86)" tree by default. Just curious as to how this relates to Reaper recognition?

[goldglob]

VST starts with Plugin.dll
VST3 starts with Plugin.vst3
"Program Files" is for 64 bit, "Programs Files (x86)" is for 32 bit. Both can contain VST and VST3.

But I have an idea.
Before the computer re-build was your old version of REAPER 32 bit?
And your new REAPER is 64 bit?
And you've installed Melda stuff leaving the paths default?
Melda always installs both 32 bit and 64 bit (unless you specify invalid paths...forget that for now).
Bear in mind that (x86) indicates 32 bit.
But did you know that 64 bit REAPER doesn't recognize 32 bit VST3 plugins? (It bridges 32bit VST but not 32 bit VST3.)
I'm guessing your old plugins were 32 bit VST3?

You'll probably find them in C:\Program Files (x86)\Common Files\VST3\
but they won't be any good to you if REAPER is 64 bit.
Let me know if I've guessed right.
If so, there might be a way to get your settings back.