We’re also seeing this on one of our unattended processes, it seems to be the first run every morning. The server is on an automated reboot schedule, so I don’t think it is related to that, but one of the screenshots we have shows a toast notification for pending Windows Updates. I’m not sure why this would cause this exception to be thrown however.
Transaction reference: N/A, Initialisation phase.
Exception: Cannot bring the target application in the foreground. The action was blocked by the current foreground window ‘New notification’ from the process ‘shellexperiencehost.exe.’
Source: [Main]