Litespeed Instance Configuration drops extended stored procedure even if executed with an account (4274367)

The user account that performs LiteSpeed installation must have Windows admin rights and must have database permissions to perform the following operations:
- Install stored procedures and extended stored procedures
- Create databases, tables, and indexes
- Insert, update, and delete to/from the MSDB, LiteSpeedLocal, and LiteSpeedCentral databases.

This is stated in LiteSpeed for SQL Server Database Objects and Privileges guide.
However, sometimes instance configuration is mistakenly executed with an account that has insufficient or partial permission resulting in the deletion of some extended stored procedure but which cannot be created in return due to lack of windows admin privileges. This is because before extended stored procedures can be created, litespeed dlls must be added to the Binn directory.

In addition to the extended stored procedures not being created, the information is not logged. The user is not even notified and he ends up assuming that the operation was successful when in reality he is missing out on most of the much needed extended procedures.