After Roxio disappointed me for the last time, I tried trial versions of both Premiere Elements 11 and Premiere Pro 6.0.3. Both gave me similar problems when launched as a non-administrator on Windows 7 Pro. After initially launching either application with "Run as Administrator," presumably to get any initial post-setup setup done (yes I meant to say that), the application would launch precisely once as a non-admin, present me with a pop-up window with the Error 213:11 code, then exit. Subsequent launches would present me with the pop-up without actually launching.
If this is related to whatever copy protection Adobe uses, does this issue go away once the products are paid for?
Welcome to the forum.
As to your question, I can't answer with certainty. I'm admin on all my systems. I will say that I have never received the error you describe when using any version of any Adobe software.
That's actually encouraging. Steven, are you still using a trial or is this a paid copy? Downloaded or installed from DVD? And on what version of Windows? If it's paid for, then this answers my question.
I run Windows 8 Pro 64-bit now, but I have access to Windows 7 64-bit SP1 still and I get the same error with the trial. A lot of the non-admin issues I run into on complex apps are corrected by launching them once as an admin, I guess so it can do any post-setup stuff as I explained, and then it works for non-admins afterward.
Mine is from my wife's subscription to the Creative Cloud since we share a PC. So it is paid for. But I can't imagine that is the problem. It sounds more like a firewall issue is keeping the program from getting the permission it needs to run.
Edit: Scratch that last comment. I found the following page: http://helpx.adobe.com/creative-suite/kb/error-store-does-not-allow.ht ml
Edit: And this comment elsewhere:
I was able to solve this for my users, buy giving them full permisions for two locations:
C:\Program Files\Common Files\Adobe
C:\Documents and Settings\All Users\Application Data\Adobe
This is NOT a trial problem. You should not get this error simply because you're on a trial, nor should you have to Run as Admin (with a right click)* for Premiere Pro. Something is definitely wrong with your system.
*You should generally be using an Admin level account under Windows. Don't run Adobe software under a Standard user account.
I'm sorry, but at the risk of sounding like I'm from space, I must point out that standard user accounts are the first and best defence against malware and other abuse. It's a best practice on Windows since Windows XP, and it's been available since NT 3.1:
Tools, Best Practice and Guidelines
Steven's advice is working. Granting Modify permissions to what %allusersprofile%\Adobe and %programfiles%\common files\Adobe point to for non-admins got me past the Error 213:11. I got a one-time complaint that it couldn't find some user interface DLL, but it hasn't happened after subsequent launches.
standard user accounts are the first and best defence against malware and other abuse.
Wholly unnecessary if you know what you're doing. (Even more so with Windows 7 and now 8.) And there are times when things in the Adobe suite simply won't work without an Admin level account.
I stand by the advice to run Adobe software with an Admin account as standard practice. (I'd wager the majority of users do.)
>times when things in the Adobe suite simply won't work without an Admin level account
I have not had any PPro CS5 problems, but my personal experience with Encore is that is will NOT create a dual layer DVD without doing the "Run as Admin" step at this link http://forums.adobe.com/thread/969395
Wholly unnecessary if you know what you're doing
I've been in IT for 20 years, with the largest client having 200+ desktops including two Macs, 500+ users, all on Active Directory and all with non-admin access, including me when I'm not actually administering something, and including the graphic artists on the Macs.
I know what I'm doing. Non-admin access is still wholly necessary.
I still get harrassed with fake anti-virus vendors trying to install things behind my back. They fail only because of my non-admin use. I suggest you don't press me on this matter. Besides, my question is answered here.