When I get issues like this I always reach for Sysinternals Suite ProcMon.
 
The first time one uses it, it is painful; but the more you use it the more you might want to use it for other purposes.
 
You need to learn how to filter out stuff, because you will see something like 20,000 system calls per second.
 
Then you begin to see why Windows runs so slowly. There may be a few thousand calls just to find a file name.
 

Well, we un/re-registered it with no luck. They sent me a new installer and also no luck. Grrrrr!
 

...wicked
...installing 32 and 64 bit Rapture DXi (1.2.1) from an older purchase alongside 32 and 64 bit Rapture VST (1.2.2) from a more recent install...

I'm just wondering whether having two different version numbers installed side by side may be causing problems.  Would it work better if both VSTi and DXi were 1.2.1?

I wouldn't think so. DX only goes to 1.2.1 and I've got so many other projects now using the VST 1.2.2 I'm not certain downgrading wouldn't produce an even larger apocalypse.
 

Old thread, I know, but I have to say this just saved my bacon on an old project - I had the same problem as Wicked, I have reinstalled everything (at least once) since I produced the track originally, but really need to get back into it now to tweak / remix / develop / otherwise pick up where I left off. I had no idea what to do as Rapture was fully installed as far as I could tell but the project wasn't seeing it and wouldn't tell me anything about the patch setup. Anyway the DXi version solved it for me and I'm off and running... except that Alchemy has decided it also doesn't want to play nice in the same project. The joys of software...