Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.

18 Vote

Remove the 'Press any key to exit' on the policyupdate application for the Central Policy PBW client.

When running the policyupdate.exe from the location C:\Windows\BeyondTrust\BeyondInsight\ it will always prompt for 'Press any key to exit' once it is done running. This prevents remote scripting as it will require input to complete. It would be great to be able to suppress this message so that the policyupdate could be run silently or remotely without the prompt at the end of the update.

  • Guest
  • Jun 18 2019
  • Future consideration
  • Attach files
  • Guest commented
    19 Nov, 2020 10:35pm

    I temporarily solved this by checking for timeout in your script:

    $proc = Start-Process -filePath "C:\Windows\BeyondTrust\BeyondInsight\policyupdate.exe" -ArgumentList "/force" -PassThru

    # keep track of timeout event

    $timeouted = $null # reset any previously set timeout

    # wait up to x seconds for normal termination

    $proc | Wait-Process -Timeout 60 -ErrorAction SilentlyContinue -ErrorVariable timeouted

    if ($timeouted)


    # terminate the process

    $proc | kill

    # update internal error counter


    elseif ($proc.ExitCode -ne 0)


    # update internal error counter


  • Guest commented
    12 Aug, 2019 02:01pm

    Need a switch for scripting. For interactive use, we need the window to not close so our users can tell us what they see in the results.

  • Guest commented
    24 Jun, 2019 06:59pm

    Without the ability to PUSH policy updates to all clients from BI, we have to leverage policyupdate.exe because sometimes we can't wait for the check in time.  Without a silent switch on this, the exe stays open in the background when running this through our endpoint management system (e.g. script).  In the meantime, we give the process time to run & update at which point we use PowerShell to locate any policyupdate process and then kill it.

  • Guest commented
    18 Jun, 2019 11:45pm

    I can see why it may have been put there in the first place such as when the EXE is launched from file explorer, the cmd window would be kept open to be able to see the output of the program.
    So rather than get rid of the "Press any key to exit" altogether, this could also be done with a command-line switch like /nopresskey or somesuch.