Kore Sound Pack Urban Arsenal 2 Refuses to Install

Hey all,

So here's the run down of what I've done and what is going on.

I've installed Kore Player lastest version and have ran the updates and registration etc..

I've taken the default options for install locations.

After Kore Player is installed I try to install Urban Arsenal 2 and am getting an error "Please run the Kore 2 or Kore Player product installer before running this installer"

I've tried the following:

Re-downloaded Kore Player and installed
Re-downloaded Urban Arsenal 2 and installed

Reinstalled Kore Player, rebooted, Reinstalled UA2 no luck
Reinstalled Kore Player, ran Kore Player, rebooted, Reinstalled UA2 no luck

No Files were modified
No Directories were modified
No Files or Directory names were changed.

Even as im administrator on the machine, I also tried right-click and install as Admin on both packs and no luck.

I'm on an AMD Phenom Quad on 64-bit Windows Vista

If anybody has any ideas, because im clearly out of them as I tried just about everything to get this to work.

Thanks in advance,

-K

 

Welcome =)

It's the default location that's the problem. The default's C:\Program Files, which is the x64 program folder on 64 bit systems. Install to Program Files (x32).

ew

 

I should have been a bit more clear, I tried both locations

C:\Program Files
and
C:\Program Files(x86)

Neither works, still get the same error.

 

I've got the same problem. Did you get any help yet?

I tried:

- Desktop
- C:\Program Files
- C:\Program Files(x86)

Might be a problem directly related to vista 64bit..

 

Nope, I have called NI support around 5 times and they just tell me to install and keep track of where the files are being placed however, I've done just about everything I can on my side to install the soundpack and nothing is working, I think its an issue with either Kore Player or the soundpack not finding the files it needs to install. My Sequencer finds the Kore Player just fine and I can use it to create sounds so im not sure what is going on with the soundpack. Something is broken obviously, when it will be fixed *throws hands up in the air* no idea.

 

Hm,

did they sound like they would look into it further?

 

*shrug* they took my email address and said they would get back at me with information but I've yet to hear back and its been quite a while and I'm over calling and getting the same instructions over and over again. Obviously there's an issue but nothing has been done, even the person on the phone was like "I dont know how you got version 2.1.0.9". I'll probably be more reluctant of purchasing anything else from NI after this whole ordeal.

 

I got 2.1.0.0.9 too...

Isn't this the latest version? I downloaded it just recently. Maybe that's where the problem lies?

 

No clue, person on the phone didn't ask just said "I dont know how you got that version" which seemed a bit strange since I got it from the link in the email where I had to register for a copy so I could activate it. But yeah, who knows, moved on.

 

I just opened a ticket regarding this issue.

 

That's the best thing to do. If you haven't heard from them in a week or so, PM me your ticket number and I'll rattle some cages.

ew

 

Cool, hope you have better luck. Maybe relay the information on here if you ever get a resolution.

Cheers,

-K

 

I've had a ticket (#2009082410004483) running for about a week now...

Same problems, but I'm installing essential bass. Could be a Vista related issue. I used to have a dual boot seup with xp32 and vista64. I didn't have any problems installing in in XP but since I cleaned up the hole thing and went vista 100%, I can't install it.

 

Did you get any response on your ticket yet?

 

Nope, I'm pretty sure its a Vista64 related issue. I've had some problems with other NI plug-ins regarding this. I had to update Battery 3 with the latest beta patch and Reaktor 5 only works when loaded in a host that has VST bridge technology. I'm hoping NI will release official updates that fullly support 64bit OS for these 2 products, since both of them are included in the Komplete 6 bundle.

As for Akoustic Piano, Electric Piano and BII, they also only work as plug-ins inside a host with VST bridge. I've worked around this by using Kontakt 3.5 to access the AP and EP libraries, but as for BII, I'm stuck with VST bridge.

The Steinberg FAQ on VST bridge for Cubase 5 clearly states that users should only realy on the VST bridge as a last resort. I've tried it and it's very unstable and tends to crash frequently.

So, in light of this, I'm not that surprised that some Kore soundpacks (or Kore player) aren't Vista64 ready at 100%.

When I was running under XP I never had any of these problems.

Guess we'll have to wait...

 

That's strange, those apps work fine with my Vista 64, even in stand alone mode.

Since I openend the ticket I did get no feedback, hope they will help me out soon.

If I can not use this soundpack, I feel like I should get my money back, really.

 

I called a few times to see if I could get some resolution, they just told me to reinstall (everytime I called) and note where the installation was set. I think around the 4th call I got a hold of somebody that said there was an issue with some file recognition on one of the binaries not sure if it was Kore Player or the SoundPack. He said he would send me an email after he took my email address down when he finds something out. That was a month ago. My guess is that the issue is with Vista 64. I'm not sure whether its the Kore Player or the Sound Packs. Obviously this issue is widespread probably with all 64 bit users and my guess is that this will never be resolved and we will never see a refund. If it is finally resolved my guess is that the sound packs will have a revision by then and be out-of-date. It would be nice if an NI employer could shed some light on this or atleast give us acknowledgment that an issue exists.

Hello......... hello .................*echoes* :angry:

 

How much RAM have you installed ?

 

8 Gigs

 

Try reinstalling the latest player version again; there was an "interesting" glitch on some systems that should be fixed.

ew