Omnisphere won't authorise - when check for challenge response I get a code "W", rather than a 32 didgit code, whatever. Licensor won't accept W as a valid code.

PC - W7/64. FL studio.

Any ideas? I've tried deleting every registry entry I could find.....but same result.

TIA

 

did you place the challenge code / serial correctly into the keygen?

and I have a feeling you need to install some updates before authorizing

 

the problem is probably that the keygen and the omnisphere version you use do not match each other....

 

Thanks for response, but all installed and updated - it worked previously. But it timebombs, presumably, and then needs a reinstall. At which point, the reinstall generates useless challenge code.

There's no uninstaller - so I suspect it's writing to somewhere or leaving some files if you simply delete obvious traces. I've tried cleaning the registry......

 

It has worked previously though - same config.

And the keygen doesn't get a use - because the challenge code - generated by Omni not the KG - is duff. It just says "W" and the KG won't accept it.

 

If you have already authorized it on your pc then the challenge code Omni generates is going to be different, hence the wrong error,

you probably need to go fishing inside the registry and see if you can locate and remove the original

 

Already done - several times. Same result. There must be something I'm missing in the search.

I can't be the only person having this issue. ;)

 

removed everything from your folders?

program, appdata, my docs, local, roaming, steam, vst, etc

With some types of authorizing you need to actually type the codes in manually rather than copy/paste, can't remember though if Omni needs the same

 

There was an issue originally when the new AIR keygen came on the scene.

The earlier versions still needed to be registered with the old keygen.

Only after that had been done could you go ahead with the updates and the new gen. Sorry I can`t be more specific, this was a few years back and memory doesn`t recall.

Try and find the old keygen with an early release and give it a go.

Best of luck with it, no Omnisphere simply aint a JOKE!

 

Thanks for replies.

I have the older KG - and updates - upto 1.02e, I think. Air KG.

It worked before. I don't want to clear space for the library, install it all over again, just to get same results. I have the recent updates and (new?) KG - I shall try that route, and report back.

 

Hence the name Pilzy to many little felows backin the day, and spending time at lower ford street

 

install everything, latest patches, new KG - works. Why didn't I just f*ing try it ? lol

[Because I had to make 40Gb space for possibly useless libraries]

Ah well, whatever - it works. Woo.

Thanks for replies, and sorry for wasting the world's time.

Mods - delete this thread at your leisure. Ta.

 

must remember that tip, try using it first

 

I will make another pinned topic, but due to the variety of omnisphere troubles it will have to be a pinned topic i regularly edit with new info in the top post. As there isnt one specific issue with omnisphere it makes it difficult. I have never had a problem with it, updating or installing or using.

I will start a new topic and send you (articstorm) and catalyst the link. It will be a open ended topic where people post their questions and we link old solution or new solutions and write out the tutorial kind of like my Kontakt one was done.



HOWEVER,

Where should this Omnisphere topic go? It doesnt have an exactly designated section...yet. Until AudioSex v2.0...

 

did you run the daw you are trying to authorize omnisphere in administration mode ...that is the only way to authorize