Until there's a separate discussion for Product Center

[ceez]

Cakewalk Product Cente 1.0.0.93 was working for me, and I was able to Sign In.

I was prompted to upgrade to 1.0.0.94 on the same machine, upgraded and immediately get this.

 

 

I've tried several things.    Completely uninstalling the Center, rebooting, installing 1.0.0.94 directly.
Same result every time.    

Next steps to debug this?
 

[Superclown]

I'm having the exact same issues no matter what computers I'm on.  I did exactly what you described several times. It's all dead in the water, no way to even get Sonar, Next, or anything at all from Cakewalk because Cakewalk Product Center is not working. I tried it using both Windows 10 that is up to date and my home computer that previously had no issues with the Product Center. Not only that, now Product Center won't even open because I get this error "entry point not found'. Oddly enough I can sign in on the Product Center website but after downloading the "update' as they required and running it. Everything came to a screeching halt. 

[Noel Borthwick]

Looks like you have an old version of windows 10. Min requirements for that API are build 1709 of win 10

https://learn.microsoft.com/en-us/windows/win32/api/wow64apiset/nf-wow64apiset-iswow64process2

[Paul Brian Bell]

I have same issue., Windows 11. Everything worked fine when I first downloaded product center last week and reactivated bandlab after it wouldn't let me activate. 

Now after it updated, I can't login to the product center at all. Same screen as OP. 

Infuriating. 

[ceez]

Noel, this is most definitely a Windows 11 box, 

[ceez]

And like Paul it seems to have activated my Sonar instance, the very first time.     It was only after exiting and re-enter the Center that the issue started

 

[ceez]

I have a cumulative update pending (KB5062553) will apply it and see if this changes anything.

[User 905133]

I didn't get the WOW64 warning, but I got the Sign-in Failed message multiple times yesterday without getting the Product Center to work.

My Windows 10 Pro PC is as updated as far as Microsoft allows given my configuration: Feature update to Windows 10, version 22H2, with the 2025-07 Cumulative quality update.   

Edited 15 hours ago by User 905133
edit

[Noel Borthwick]

Sorry for the sign in troubles with CPC folks. I've identified the problem with the sign in for CPC.

It's caused because we cache state related to the sign in for the current product. However, if you change the product and exit the next time it fails to auto sign in.
We'll be releasing an update for CPC momentarily. Please update it asap and check if your sign in problem is resolved. 
 

Here is a link to the update if you want to try it before its posted.

Note: that the first time you run the update, it may force you to sign in but on subsequent launches it should now work correctly.

Please let me know if this solves your sign in problems asap.

[AntManB]

Thanks Noel!  The update did the trick for me.

AMB

 

[Bristol_Jonesey]

Thanks Noel. Works now

[andre villeneu]

Thanks a million Mr. Borthwick.

[Brian Barton]

Yes, this worked for me! Thank you!

[User 905133]

Thank, Noel.  Worked for me, too, on my main music PC.

[Maria P]

Thank you Noel. It works!

[Superclown]

Thanks Noel, worked for me also on my Windows 10 studio machine. The wow64process2 error was from my Windows 8 (yes Windows 8 🙉) machine that up until the CPC update had been using Cakewalk Product Center and CbB just beautifully.  No longer able to use Cakewalk products on that machine or after the 1st of August. 

Thanks for the update link!

 

[ceez]

Thanks Noel.

Wish I had seen your post before I went through the In-Place update.  

 

 

[Jim Fogle]

The test release lets CPC display updates and downloads and installs.

However, the continue with Google issue I was also experiencing and described +++ here +++ is still present and has not been addressed.