I initially added an AppLocker Package app rule rule to allow: Publisher: CN=Adobe Systems Incorporated, OU=Adobe Systems, O=Adobe Systems Incorporated, L=San Jose, S=California, C=US Package name: * Package version: * [and above] But that did not work for me.  The publisher is clearly not correct. The way I found the correct publisher string was to use another PC that didn't have AppLocker applied, install the app, then fire up the local group policy editor, navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Application Control Policies > AppLocker > Packages app Rules, and add a new rule, browsing to the app.  You can then copy and paste the Publisher into your enterprise's Group Policy. Here's what I found: CN=Adobe Systems Incorporated, OU=Adobe Systems, O=Adobe Systems Incorporated, L=San Jose, S=California, C=US, SERIALNUMBER=xxxxxx, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US Not sure if the serial number is unique to us, so I've changed it to xxxxxx. ... View more

Yes, it was resolved a few hours after the post here, but this should not have happened.   The issue raises serious concerns about your license validation method.   The Microsoft method works well for us, with our own internal KMS server that we activate the license key against, after it has been activated once by Adobe. Our management have formally requested a please explain from Adobe through account management and I would encourage other customers to let their account management know they aren't pleased. ... View more

Works now for my install.  This has only started working in the last 35 minutes.  Can we get a formal explanation from Adobe management about this and what steps you are taking to ensure that this doesn't happen again. ... View more

I suspect this issue will cause enterprises to reconsider their use of Adobe software.  We paid for the software and now we can't use it.  We will be speaking with our account manager and arguing for compensation. ... View more

This has NOT been resolved and we're still affected.  See my post here: https://forums.adobe.com/thread/1546687 This is a serious issue for us and we need it resolved now. ... View more

Still doesn't work for us. We're only seeing this since the 11.0.8 patch, but that might just be a coincidence, as we tried our existing package of 11.0.7 and it's not validating either. This only seems to be affecting new installs, not patched installs. This appears to be a change that has happened on the Adobe side.  We're not going to be distributing our Serial Number for end-users to re-enter.  Adobe needs to provide a better fix for sysadmins to deploy silently. ... View more

Please please consider making this available in 11.0.1.  ... View more

I think you're too late and it's now been fixed  The link was at the end of this line: Related Resources This guide is part of an enterprise resource ecosystem designed to help administrators manage Acrobat products across their organizations. All available resources can be accessed from the Enterprise Toolkit for Acrobat Products. It was pointing to http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/www.adobe.com/go/acrobatetk, but now it's been changed to point to http://www.adobe.com/go/acrobatetk.  Thanks to whoever fixed it. ... View more