# Scribe application

**URL:** <https://community.netwrix.com/t/scribe-application/134154>\
**Category:** PolicyPak Discussions & Questions\
**Tags:** endpoint-policy-manager, endpoint-privilege-manager\
**Created:** [June 26, 2026, 2:09pm UTC](https://community.netwrix.com/t/scribe-application/134154 "2026-06-26T14:09:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bharris](https://avatars.discourse-cdn.com/v4/letter/b/ee7513/32.png) [@bharris](https://community.netwrix.com/u/bharris)\
**Post date:** [June 26, 2026, 2:09pm UTC](https://community.netwrix.com/t/scribe-application/134154/1 "2026-06-26T14:09:11Z")

</div>

Has anybody had any luck making a working elevation rule for Scribe?

When I install it in Program Files:  
I receive a Policypak elevation prompt  
After I create an elevation rule, I receive an error from the application: “The requested operation requires elevation”

When I install it to appdata:  
I still receive a Policypak elevation prompt  
When creating an elevation rule, I still receive “The requested operation requires elevation” error.  
I can get it to run when I change my elevation rule to an allow-and-log rule.

Scribe does work when I run it as administrator, using the stock “Run As Administrator” in Windows. That at least lends some hope that there _might_ be a way to get it to work. Should I be looking into custom tokens, or something along those lines?

---

<div class="post-metadata">

**Author:** ![john.demianiuk](https://yyz1.discourse-cdn.com/netwrix/user_avatar/community.netwrix.com/john.demianiuk/32/212_2.png) [@john.demianiuk](https://community.netwrix.com/u/john.demianiuk)\
**Post date:** [June 26, 2026, 4:07pm UTC](https://community.netwrix.com/t/scribe-application/134154/2 "2026-06-26T16:07:03Z")

</div>

Hi Brent,

Different application behave differently when elevated. Some apps will not run when a standard account is elevated to to run the app when it’s not designed to. Because you stated that scribe runs with an “Allow and Log” rule, it makes me think this is one of those apps.

Question: What is the “PolicyPak Elevation Prompt” you are referring to? I assume this is the Admin Approval prompt?

I’m going to make an assumption here and assume you are running both SecureRun and Admin Approval. SecureRun is blocking the application and thereby presenting the Admin Approval window. But it could also be that Admin Approval is configured to force all installers to present the Admin Approval window.

To know for sure if Scribe actually requires elevation (and not just forcing Admin Approval because of SecureRun blockage or an Admin Approval setting), run the installer on a computer without PolicyPak (or just stop the PolicyPak services). If you get a standard UAC prompt - it requires elevation. Opena ticket through the [Netwrix Support Portal](https://www.netwrix.com/sign_in.html) and we’ll help figure out what is required. If you don’t, then it’s just something forcing Admin Approval to prompt for permission to run. You should be good to stick with the Allow and Log rule.

Hopefully this helps explains what might be happening. Let us know. Thanks.

---

<div class="post-metadata">

**Author:** ![bharris](https://avatars.discourse-cdn.com/v4/letter/b/ee7513/32.png) [@bharris](https://community.netwrix.com/u/bharris)\
**Post date:** [June 26, 2026, 6:36pm UTC](https://community.netwrix.com/t/scribe-application/134154/3 "2026-06-26T18:36:21Z")

</div>

John,

Yes, it’s the admin approval prompt.

We aren’t running secure-run in our environment, and we aren’t forcing admin approval for all installers.

I can run install on a test-PC, if you’d like, but they’re pretty explicit about wanting admin rights. For example, on my “appdata” / “allow and log” install, the initial sign-in screen shows “limited installation”:

 ![image](https://netwrix1.discourse-cdn.com/netwrix/original/2X/2/21f285d5c1425faf06f1ac5b8cb27dea01e87148.png)

Then when I click on “limited installation” this pops up:

 ![image](https://netwrix1.discourse-cdn.com/netwrix/original/2X/9/9773bfb0d2b942e5859fe36cebfb32d1891edb15.png)

If I right-click and use Windows’s run-as-administrator, I get this:

 ![image](https://netwrix1.discourse-cdn.com/netwrix/original/2X/d/d99b4da0f2062e7fb61b05d414cc14920b5e0ce1.png)

---

<div class="post-metadata">

**Author:** ![john.demianiuk](https://yyz1.discourse-cdn.com/netwrix/user_avatar/community.netwrix.com/john.demianiuk/32/212_2.png) [@john.demianiuk](https://community.netwrix.com/u/john.demianiuk)\
**Post date:** [June 26, 2026, 7:10pm UTC](https://community.netwrix.com/t/scribe-application/134154/4 "2026-06-26T19:10:54Z")

</div>

Fair enough, Brent. Thank you for that extra info. At this point we’ll need to create a support ticket to dig into what policies are required for this particular application.

When you can please open a new ticket through the [Netwrix Support Portal](https://www.netwrix.com/sign_in.html) and we’ll help you find the solution.

Thanks,

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/netwrix/user_avatar/community.netwrix.com/system/32/3102_2.png) [@system](https://community.netwrix.com/u/system)\
**Post date:** [August 25, 2026, 7:11pm UTC](https://community.netwrix.com/t/scribe-application/134154/5 "2026-08-25T19:11:21Z")

</div>

Closed on August 25, 2026, 7:11pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
