Installed DW Soundworks with the latest 1.4 Team R2R system already installed. I get a "not valid AAX" notice in PT12 and stand alone opens to just a white screen. Any suggestions?

 

Hi ...

Did you get past this ? I'm facing the same with Pro Tools 2021.7 (R2R) and Cockos REAPER (latest) not detecting neither vst or vst3 .
1.4 Team R2R system installed here, as well . as well as network block runtime and root certificate latest installed .
Not even the stand alone version of DW Soundworks seems to open . Tried to run as administrator as well as normal / standard user, no differ .

Root certificate and R2R system test show as, "good" .

 

Yeah, that is the exact problems I am having.

Same here. Got to be some smart person on here that has figured it out already.

 

Not such problems with me, Windows 10 Standalone/VST but I don't have bank expansions installed (I was lazy and hesitant due to using system partition for XPs and I hate that), but I will do try one as I am writing this just for the purpose of seeing if there is any issue. PS. If you wanna to resolve your problem please add to it system you have installed so people may help and figure where is the problem. Maybe Windows 11 if you use it there have blocked TEAM R2R system as I have already seen under security settings, APPLICATION VERIFICATION or similar. Or install Kaspersky if you use Windows defender and you'll be good to go always and secure 101.


UPDATE: everything works as it should so there is no error on my side, recheck If Windows defender is blocking program itself because it is bypassed so that may be the case also if not then try to turn off that authenticity app if you are on windows 11.

 

Last edited: Apr 29, 2026 at 9:58 AM

Hey Hennessey, thanks for the tips. On my system its Windows 10 PT12. No windows defender or any AV on. Just using tiny wall for firewall. I installed Pulsar P44 Magnum v1.1.2 which uses the new system and it works fine. Everything checks out in WitchDiag v1.4.0 and TEAM R2R Root Certificate is in the right place. Very strange...

 

Same here. And I can´t see GUI instruments and/or expansions. All previous requisites OK.

 

OK ...

Got the standalone as well as AAX working, but no libraries found (tried using a Symlink installer) .
I have the expansions on a separate HDD, rather than the system drive for I have run out of space on it .
The Symlink installer part went smoothly, but yet no libraries found (tried the standalone version, so far) .

HELP needed here .

/ Z .

 

 

Last edited: Apr 29, 2026 at 5:11 PM

My fix / solution was this ... after running the Symlink.cmd I went to here C:\ProgramData\Drum Workshop\Soundworks\Packs
and I noticed the Symlinks shortcuts were point to the correct location, which in my case was D:\ ...
BUT I happened to notice, that they'd need to be located under a folder named Packs ... so I created this folder, and copied / moved the library folders to this Packs - folder and there it was, all the libraries are no working, at least with the standalone version, I have not yet tested in Pro Tools or REAPER .

Hope this helps someone .

/ Z .

 

What did you do to get it working? I'm still get the white screen on stand alone. Do I just put the library ex:DW Maple Mahogany folder in the Packs folder? Nothing needs to go in the parent folder?

 

Last edited: Apr 29, 2026 at 8:27 PM

I believe that expansions that default to the system drive (which is dumb. no idea why devs do that) can be moved anywhere else simply by use of symlinks. I would only use the command line to assign those not some .cmd thing.

 

Doesn´t work. Really tired.

 

works here win 10 reaper. very nice

 

Did you just put the library ex:DW Maple Mahogany folder in the Packs folder? Nothing needs to go in the parent folder?
I am either putting the files in the wrong place and it can't see them or the software needs AVX2 which my cpu doesn't have. Still trying to figure this out.

 

When using symlinks with persnickety apps that must use a specific path you need to place the link at the end of given OEM path so that link mimics exactly what the app wants to see - only the actual files will be somewhere. Maintaining that specific illusion for the calling application is key to successful symlinks while making certain the files are moved and stored off the system drive.

 

I'm not even to the point of making symlinks yet saccamano. I'm still trying on the C: drive "C:\ProgramData\Drum Workshop\Soundworks\Packs". Needed to check if everybody put the library ex:DW Maple Mahogany folder in the Packs folder and that nothing else needs to go in the parent folder?