This seems possibly due to a recent Windows 11 version 25H2 update? I don’t know, but I can’t understand the operation I have to perform to get WLPro 13 to let the plugin accept a Preset. This is something that used to happen automatically. See picture:
Try the following. In File Explorer, right click on the VST3 Folder to open the local menu, and select Properties. Then select the Security tab. Then make sure that all permissions are enabled.
PG, thanks for the response. All the permissions are enabled except for a line I haven’t seen before,‘Special Permissions’, and this seems a tough nut to crack, and, to what end, I don’t know. However, my other plugins from the same vendor (that I installed year(s?) ago that I keep updating) let me perform a Preset via the same File Explorer folder - and - their Properties Security tab does not contain the slot “Special Permissions”. This could be all a MS Defender thing, but perhaps something changed with the vendor? I’ll contact them both.
Too, let me say this, thank DOG that the vendors are writing programs that - although MS/Windows tells me that I should not load the particular plugin - the PC and the DAW programs continue to work fine. My issues here could all be a Windows Security issue.
The recent plugins that are blocking the Preset in the File Explorer folders are ‘StCompressor’ by SIR Audio Tools and ‘Soothe3’ by oeksound. Both of these plugins offer (via the program’s ‘internal’ Save option) to save Presets, but they list the User Presets among the Factory presets and it’s much easier to open the File Explorer and see just the User Presets by themselves. Am I just lazy? :\
This is not so clear from your message. Did you solve the problem?
No, PG, in these newer 2 plugins I cannot save a Preset in the File Explorer. I even went so far as to manually add a Preset folder within the File Explorer for those particular plugins. My thinking here was that the plugin was not able to create this folder and that if there was a folder there I could then save a Preset. No, this didn’t work either, although the message changed. See screen picture.
For this line, what do you see? “Deny” ?
Note that this is WaveLab that can create the preset, not the plugin. The plugin doesn’t intervene for the saving of the preset.
It doesn’t say ‘Deny’, instead it is just grayed out. That’s in the SirAudio StComp. Actually the Oeksound does not have this grayed out line, it looks like all the other previous Security tabs.on my other plugins.