Hi guys,
I tried to use UiPath assistant to run automation in PiP mode(a little window will be created, all the RPA tasks will be finished inside), and it works perfectly, but after I close the PiP window, I found in my main screen, my teams was log out and windows Search bar is not working, the only way I found now to fix it is reboot my PC
Not sure if the job or setting of PiP environment cause impact to the main windows environment.. ?
Did anyone here face the same or similar problem? any suggestion will be appreciated!
thanks!
hi @MOONREN_Xu
PiP runs automation in a separate Windows session, and sometimes it doesn’t detach cleanly, which can cause issues like Teams logout or Windows Search not working. It’s not caused by the workflow itself.
Suggestions:
Upgrade to the latest UiPath version
Avoid force-closing the PiP window; stop the job properly
If it keeps happening, disable PiP or use background/unattended execution
Reboot works because it resets the Windows session.
Hi @MOONREN_Xu
PiP runs in a separate session, but automations that interact with system-level UI or Windows shell can still affect the main session.
Please review the workflow activities, avoid system-level interactions, and ensure UiPath is updated.
If it continues, share logs or raise a UiPath support ticket.
If helpful, mark as solution. Happy automation with UiPath
as a start point check your event viewer logs to see if anything is getting killed or changed
reachout to customer support might be ideal for deeper investigation
cheers
@MOONREN_Xu
I suggest you to check the event viewer and also if your process contains any key shortcuts which can impact also which OS are you using and which version of UiPath? If you are using a Older version suggest to upgrade, If upgrade is not a option then log a ticket with support
Thanks,
Srini
@MOONREN_Xu This is a known behavior with PiP mode. Since PiP runs in a separate Windows session, some applications like Teams that are session-dependent can get disrupted when the PiP session closes. The Windows Search bar issue is also related to the session handling. A few things to try beyond rebooting: you can restart the Windows Search service (WSearch) via Services.msc or Task Manager to fix the search bar without a full reboot. For Teams, try signing back in — it may just need to re-authenticate after the session switch. Also make sure you’re stopping the PiP job cleanly through the Assistant rather than force-closing the PiP window, as an abrupt close is more likely to leave session artifacts behind.
Hi @MOONREN_Xu
PiP mode can interfere with system apps, causing Teams logout or Search to stop. Avoid automating system-level apps in PiP, use background/unattended runs instead, and updating Studio/Assistant helps. You can restart explorer.exe instead of rebooting to recover.