<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Possible that the VM you're… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/73716#M26321</link>
    <description>Possible that the VM you're using has this ""total black screen"" feature that when you minimize or disconnect to VM the screen of VM turns into black and BP can't work because it doesn't see any. That's why when you run it and you tried minimizing or disconnecting from VM, there's an error ""Could not identify process owning the current foreground window""
If that's not case, if you're not minimizing or disconnecting from VM, then maybe there are other factors triggering this error.</description>
    <pubDate>Tue, 26 Feb 2019 15:36:00 GMT</pubDate>
    <dc:creator>CeddrickFerido</dc:creator>
    <dc:date>2019-02-26T15:36:00Z</dc:date>
    <item>
      <title>Could not identify process owning the current foreground window</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/73715#M26320</link>
      <description>Hi - We are getting the below issue when we are running the process on the VM through the Control Room. Can you suggest the steps to resolve this issue.

&amp;nbsp;

ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Activate PDF' on page 'launch' - Could not identify process owning the current foreground window</description>
      <pubDate>Sat, 23 Feb 2019 07:51:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/73715#M26320</guid>
      <dc:creator>SudhindraGanesh</dc:creator>
      <dc:date>2019-02-23T07:51:00Z</dc:date>
    </item>
    <item>
      <title>Possible that the VM you're…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/73716#M26321</link>
      <description>Possible that the VM you're using has this ""total black screen"" feature that when you minimize or disconnect to VM the screen of VM turns into black and BP can't work because it doesn't see any. That's why when you run it and you tried minimizing or disconnecting from VM, there's an error ""Could not identify process owning the current foreground window""
If that's not case, if you're not minimizing or disconnecting from VM, then maybe there are other factors triggering this error.</description>
      <pubDate>Tue, 26 Feb 2019 15:36:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/73716#M26321</guid>
      <dc:creator>CeddrickFerido</dc:creator>
      <dc:date>2019-02-26T15:36:00Z</dc:date>
    </item>
  </channel>
</rss>

