Unprotect files from Sensitive Data Shield

Thank you, Dinesh.  That's exactly the information I was looking for.  My searches of the user help were not turning it up

Several years ago I reported a problem on Windows 7 with Services For Unix where the awsidagent service would eat memory and CPU after running certain Python scripts on the Unix side.  AVG is a great product, but it doesn't always play well with Microsoft's Unix & Linux supplemental services.  I fully understand that:  folks running Unix on top of Windows are a weird edge case.  But you're great at helping with workarounds in those cases.

If I uncheck "Block other accounts…" the following:
jlcop> explorer.exe addresses.docx
correctly opens the Word file addresses.docx
jlcop> gs -sDEVICE=pdfwrite -sOutputFile=/tmp/out.pdf foo.ps
throws the error **** Could not open the file /tmp/out.pdf . because the file /tmp/out.pdf has been protected.  The command
jlcop> cd /tmp; Acrobat.exe out.pdf
displays the PDF file in Acrobat once it is written.  

In short, I can open and write a protected file from the Windows side, and can open a protected file for reading from the Linux side.  I cannot open a file for writing from the Linux side.  

To repeat my initial question:  Other than turning file protection off altogether, how can I UNPROTECT individual files which have been protected.  I don't want to temporarily unprotect them, but to turn off protection on those particular files completely.

Alternately, it's not clear how to add all of WSL to the Allowed Apps list.

I am running Windows Subsystem for Linux.  When I allow Sensitive Data Shield to protect files such as PDFs and DOCXs, I can no longer access them from inside Linux.  I have tried setting Data Shield to allow access from other accounts on the computer, but that only goes so far.  How do I unprotect files permanently.  I don't want to completely turn off Data Shield, but I do want to unprotect files that are protected.  There doesn't seem to be an obvious way to unprotect a file that I've previously protected.

Hello Jeffrey,
Thank you for the response. I am happy that the knowledge base helped you with the required information to check with a fix.
If you have any other queries, please feel free to contact us.
Thank you.

Hello Jeffrey,
Thank you for the reply.
You have stated it partially solves the prblem but not completely.
Please let us know what exactly happes after uncheking  "Block other user accounts on this PC from accessing protected documents" 
If you are experiencing any issues with our apps, please provide some additional information and I will be more than happy to help you out.
Awaiting your response.

Thank you for writing back to us, Jeffrey.

Were you able to manage the protected documents under Sensitive data shield and access them from Linux?
Awaiting your response.

Thank you for clarifying, Jeffrey.
You should be able to manage the documents protected by Sensitive Data Shield as mentioned in this article.
Please let us know, if you've tried the same steps.

As I said in my original question, "I have tried setting Data Shield to allow access from other accounts on the computer, but that only goes so far."  So, yes, Midhun, I've already tried the thing you're suggesting, and it allows me to do things from a WSL command line like "explorer.exe letter.docx", but it doesn't allow me to recreate a PDF file from WSL tools, because the PDF file is protected.  

I can turn off Data Shield totally, but what I really want is the ability to turn off protection for particular files.  It appears I can protect files, but not UNprotect them.

Thank you, Dinesh.  That's exactly the information I was looking for.  My searches of the user help were not turning it up

Several years ago I reported a problem on Windows 7 with Services For Unix where the awsidagent service would eat memory and CPU after running certain Python scripts on the Unix side.  AVG is a great product, but it doesn't always play well with Microsoft's Unix & Linux supplemental services.  I fully understand that:  folks running Unix on top of Windows are a weird edge case.  But you're great at helping with workarounds in those cases.