The following are uninstallation issues in the respective Operating Systems that have been resolved:

• In Windows 10 - Named Pipe log was not getting deleted after uninstalling Admin Version of the Runner
• In Windows server 2012 - Package 70 folder was not getting deleted after uninstalling Admin Version of the Runner
• In Windows 8 - Product and Unhandled Exception folders in the Log folder was not getting deleted after uninstalling Admin version of the Runner
• In Windows Server 2016 -. Unhandled Exception log folder was not getting deleted after uninstalling Admin version  of the Runner.
• In Windows Server 2008 - Dll management folder, package 70 and Log folder were not getting deleted after uninstalling Admin version of the Runner.

There was one installation issue in the following OS that has been resolved:

• In Windows Server 2008 – After installing Admin version of the Runner, when user double-clicked on the Runner Icon in the desktop it displayed an error stating " Robility runner stopped working.”

Other Bugs Fixed

• After running the bot, the execution details were not getting updated in the Runner log in SmartManager’s Environment Monitoring menu upon clicking on View Log button and selecting SmartRunner in Log Details page.
• When a robot is initiated to execute a workflow by logging into the machine using the AutoLogon feature, the workflow did not get executed and the robot moved to allocated status.
• The Log was taking longer than the usual time to get printed in the user’s local Runner log path after execution of the workflow.