Strange. What percentage of Windows users are running Vista or 7? A small number of them. 

from our statistics 21% of windows users are on VISTA and another 21% on W7 (constantly growing) - but hey, there are also 6 users of windows NT ;-)

besides the end-of-life of XP64 the major and increasing problem since the past year is that more and more companies are no longer providing working drivers for XP64.

your specific problem might be related to a VST2/VST3 loading issue (save VST2 but trying to load a VST3 plugin?)

as far as i can see you still have not provided the information about wich plugin we are even talking, your message to support was just a copy & paste ...

christian

I don't know how to be any more specific than "NI Kontakt 3.5.0.25," what else do you need?

I know some people using Windows 7 for their web surfing computers but not many who run it on their DAW machines. 

@Another User said:

I can start up from a cold boot and see my VSTi plug-ins. I can load some instruments and save that as a metaframe. But if I close VE Pro, open it again and open that metaframe, it gives me the error message "Missing Plug-in: xxx."

now i'm understanding this not as *kontakt missing* but as *plugin-xxx missing* so i'm asking which plugin ...

did i miss something? christian

@synthetic said:

I know some people using Windows 7 for their web surfing computers but not many who run it on their DAW machines. 

I know quite a lot of people running W7 for slave machines and even some for DAW machines. Even though I'm currently using XP64 (for one more day, yay.....!) I can't think of a single DAW developer who has ever supported XP64. However, I do know of some who support Vista 64 and W7 64.

DG

I have a stable GigaStudio 4 rig running on x64. I'm hesitant to make a change since I can't rely on VE Pro in this state and have to keep working. But I'll buy a copy of W7 Ultimate and put it on a different (swappable) startup drive for testing. 

Here's how I recreate the bug: 

1. Boot up computer and start VE Pro Server (32-bit) 

2. Delete default instrument, add Kontakt 3.5

3. Load a few sounds then save the Mframe

4. Quit VE Pro

5. Launch VE Pro and open the Mframe

6. VE Pro reports "Missing plug-in: Kontakt 3." When I right click in the left column I no longer have a VSTi option that lists my plug-ins. I have to reboot the computer to see my plug-ins again. 

I've tried the above with GVI 3 and GVI 4 with the same result. 

I can't reproduce your problem here with Kontakt 2. It works just as expected. I'm assuming that you clicked "add" to get the VEP instance, and then named it, as this wasn't mentioned in your repro, BTW.

I think that there is something wrong with your setup, and assuming that you set W7 up the same way, then there is no guarantee that it will work there either. Unfortunately I don't have Kontakt 3, so I can't check that here.

DG

One of my VE Pro slaves is X64. I don't have that problem. I have K3.5 on it and it loads the Mframe every time. The only problem with that one is that it stalls out for a long time between loading instances of Kontakt. It will load the first one (rather large) then it pauses for about 4 minutes before it will begin loading the second one. 

I also have Win7 on another VE Pro Slave. I have had some occasional issues were the Mframe wouldn't load at all on that one. I would end up having to open an empty VE Pro and then load the project from there. But the Win7 slave doesn't stall out between Kontakt instances. 

cm, any ideas for me to try? 

unfortunately not, and more unfortunately i can't free up the XP64 machine currrently for having a closer look (it is only a dual boot config)

christian

Tonight I discovered another clue. If I open VE Pro Server and choose File > Open then I can open my mframe project. It is only if VE Pro is not running and I double click the mframe file that I see the bug.

So to reproduce: Start up computer, double click an mframe file > VE Pro errors and says "Missing plug-in: Kontakt 3" or whatever VSTi you were using.