Please elevate session, or spawn elevated session as necessary.

I cannot express how frustrating it is to be working in a normal powershell session and then need to install something via cinst only to get a security exception. Please elevate the session when necessary with RunAs or Invoke-Command -Verb when necessary.

The issue names no repository files or tests; start by tracing the cinst command path and reviewing how a normal PowerShell session handles the requested elevation. Compare the existing behavior with the mentioned RunAs or Invoke-Command -Verb approaches, with done defined as elevating or spawning an elevated session when necessary.

Written by the indexing model from the issue text.