Lock Pages in Memory (SeLockMemoryPrivilege)

I don't know whether this is the intended behavior, but the 7-Zip filemanager permanently assigns the SeLockMemoryPrivilege user right (i.e., "Lock Pages in Memory" under User Rights in Local Security Policy) to the user every time the application is closed, regardless of whether the "Use Large Memory Pages" option in the settings menu is checked.  This behavior occurs with 7-zip 9.22 beta under XP/2003 64-bit when the user is logged on as an administrator.

I don't think it's appropriate to modify local policies without user consent.  This is particularly a problem when 7-zip is occasionally run with administrative  privileges from an account that normally runs in a limited-user context.  Is this the expected behavior, or is it only supposed to happen when the "Use Large Memory Pages" option in the settings is selected? I hope this is just a bug.  In either case, I know it's not something done out of malice; make no mistake.

I'll check whether this happens in 9.20 as well…

That aside: thanks for the great software!  It's one of few applications I consider a "must have".

The problem with large pages, that it needs one reboot after getting SeLockMemoryPrivilege.
So 7-zip asks SeLockMemoryPrivilege every time at 7-Zip File Manager app start.
So after next reboot, if the user enables large pages, it will be able to get it without reboot. Also it allows console application to use large pages.

What exact problems do you see with such behavior?

Thanks for taking the time to respond.

If I'm interpreting you correctly, 7-zip automatically enables the privilege, but doesn't actually make use of the feature unless the "enable large pages" option is selected.

My only concern is that any process executing from the account in question can presumably exercise the privilege once it's been granted to the user, even as a regular (i.e., non-admin) user.

Because I understand your reasoning and it's clearly intentional, I won't take up more of your time on the issue.