none
"ALL APPLICATION PACKAGES" account default object permissions RRS feed

  • Question

  • I had an issue with some third-party Windows 8 metro apps crashing recently when they were opened. The culprit was that the "ALL APPLICATION PACKAGES" account didn't have access to the regkey "HKEY_CLASSES_ROOT\Wow6432Node\Interface" because of a GPO setting enforcing specific permissions on the key for application compatibility purposes in Windows 7. I found a bit of information about the account here: http://technet.microsoft.com/en-us/library/hh832040.aspx#BKMK_AccessPermsGP

    A lot of forums have posted fixes to these types of issues relating to app crashes and this account by giving full permissions to entire registry keys and file system objects. This is very bad security practice.

    Is there any information about what objects this account has access to by default to troubleshoot these types of issues in the future, and enforce good security practices?

    Tuesday, December 11, 2012 5:08 AM

Answers

  • We do not have related information you required. However you can change permission settings if it is needed.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, December 12, 2012 7:41 AM
    Moderator

All replies

  • We do not have related information you required. However you can change permission settings if it is needed.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, December 12, 2012 7:41 AM
    Moderator
  • 'We do not have related information you required' is not an answer, so why mark it as one? The culture on these forums of marking useless information as answers is infuriating. What if someone has the information required in future but chooses not to engage in the thread due to it showing as already having an "answer".
    Wednesday, May 10, 2017 11:38 AM