https://community.blueprism.com/t5/Product-Forum/quot-Could-not-identify-process-owning-the-current-foreground/m-p/47608#M3317 We recommend restarting the VM after accessing it with RDP. Also, are you using Login Agent?<BR />We don't recommend the use of Remote Desktop, please take a look at this KB article: <STRONG><A href="https://portal.blueprism.com/customer-support/support-center#/path/Operational-Support/Monitoring/Remote-Tools/1137406062/Which-Remote-Access-tools-do-Blue-Prism-recommend.htm" target="_blank" rel="noopener">Which Remote Access tools do Blue Prism recommend</A></STRONG><BR />For the error, please take a look a this KB article: <STRONG><A href="https://portal.blueprism.com/customer-support/support-center#/path/Automation-Design/Studio/Process-Design/1137420332/Why-do-I-get-error-Could-not-identify-process-owning-the-current-foreground-window-when-trying-to-focus-an-application.htm" target="_blank" rel="noopener">Why do I get an error "Could not identify process owning the current foreground window" when trying to focus an application</A><BR /><BR /></STRONG><BR /><BR />------------------------------<BR />Luis Lopez<BR />Customer Support Engineer English and Spanish<BR />Blue Prism Ltd<BR />------------------------------<BR /> Thu, 04 Feb 2021 19:06:00 GMT expertcr 2021-02-04T19:06:00Z https://community.blueprism.com/t5/Product-Forum/quot-Could-not-identify-process-owning-the-current-foreground/m-p/47607#M3316 <P>The bot works fine when we are connected using the RDP and logged on the windows account, but once we close the RDP connection (leaving the account logged on and the process running in the background) there is an exception that appears in the <STRONG>"Activate" action stage</STRONG>, the exception is <STRONG>""Could not identify process owning the current foreground window"".</STRONG></P> <P>However I made sure that there is only one account logged on and no other account activity ???</P><BR /><BR />------------------------------<BR />Bishoy Sawiris<BR />------------------------------<BR /> Thu, 04 Feb 2021 14:01:00 GMT https://community.blueprism.com/t5/Product-Forum/quot-Could-not-identify-process-owning-the-current-foreground/m-p/47607#M3316 BishoySawiris 2021-02-04T14:01:00Z https://community.blueprism.com/t5/Product-Forum/quot-Could-not-identify-process-owning-the-current-foreground/m-p/47608#M3317 We recommend restarting the VM after accessing it with RDP. Also, are you using Login Agent?<BR />We don't recommend the use of Remote Desktop, please take a look at this KB article: <STRONG><A href="https://portal.blueprism.com/customer-support/support-center#/path/Operational-Support/Monitoring/Remote-Tools/1137406062/Which-Remote-Access-tools-do-Blue-Prism-recommend.htm" target="_blank" rel="noopener">Which Remote Access tools do Blue Prism recommend</A></STRONG><BR />For the error, please take a look a this KB article: <STRONG><A href="https://portal.blueprism.com/customer-support/support-center#/path/Automation-Design/Studio/Process-Design/1137420332/Why-do-I-get-error-Could-not-identify-process-owning-the-current-foreground-window-when-trying-to-focus-an-application.htm" target="_blank" rel="noopener">Why do I get an error "Could not identify process owning the current foreground window" when trying to focus an application</A><BR /><BR /></STRONG><BR /><BR />------------------------------<BR />Luis Lopez<BR />Customer Support Engineer English and Spanish<BR />Blue Prism Ltd<BR />------------------------------<BR /> Thu, 04 Feb 2021 19:06:00 GMT https://community.blueprism.com/t5/Product-Forum/quot-Could-not-identify-process-owning-the-current-foreground/m-p/47608#M3317 expertcr 2021-02-04T19:06:00Z