ALL RESTRICTED APP PACKAGES again

Question

Lets try this one more time.

I want to repair my system, but without having access to ALL RESTRICTED APP PACKAGES permission I cannot give complete access to do so. How do I add it myself in file permission?

Answer 1

Hi @Nick B,

I'm glad to hear you solve the problem, and thanks for your sharing. If you have any issue, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

[ALL RESTRICTED APP PACKAGES again]

Issue Symptom:

I want to repair my system, but without having access to ALL RESTRICTED APP PACKAGES permission I cannot give complete access to do so. How do I add it myself in file permission?

Solutions:

Launching separate manufacturer, supplier image on boot that is windows pre installation environment and renaming, naming folders, and moving files or colliding those folders which already have those permissions. Since ACL-COPY has been removed.

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 2

I figured it out. Launching separate booting of Windows pre installation environment and renaming, naming and moving files to directory already with that permission to put those permissions more forward to root directory, so that it can always be managed and I have full access.

Answer 3

I figured it out. Launching separate manufacturer, supplier image on boot that is windows pre installation environment and renaming, naming folders, and moving files or colliding those folders which already have those permissions. Since ACL-COPY has been removed.