<?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 Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385664#M4669</link>
    <description>&lt;P&gt;I checked the PID in both Task Manager and the PSM Connection Component logs.&lt;/P&gt;&lt;P&gt;The PID returned for the SCCM process is the same in both Task Manager and the Connection Component logs.&lt;/P&gt;&lt;P&gt;So, based on this check, the PID returned by&lt;/P&gt;&lt;P&gt;RunAs()&lt;/P&gt;&lt;P&gt;appears to be the same as the actual running SCCM process.&lt;/P&gt;&lt;P&gt;Please let me know if there is anything else I should check regarding the PID or process monitoring.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Sep 2026 10:10:15 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-09-08T10:10:15Z</dc:date>
    <item>
      <title>PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385660#M4665</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00001oDQfMIAW.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/96112i0FD1FBC4DF74BC49/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00001oDQfMIAW.png" alt="Field_Content_versions_oct20__068Vy00001oDQfMIAW.png" /&gt;&lt;/span&gt;Hi Team,&lt;/P&gt;&lt;P&gt;We have developed a custom &lt;B&gt;AutoIt script&lt;/B&gt; to launch SCCM through a CyberArk PSM connection component.&lt;/P&gt;&lt;P&gt;When the PSM session is launched, the SCCM application opens successfully, but we immediately get the following popup in the background:&lt;/P&gt;&lt;P&gt;&lt;B&gt;PSMSessionAlert.exe – “This application could not be started”&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;﻿&lt;/B&gt;The popup remains behind the SCCM application and becomes visible only when SCCM is minimized.&lt;/P&gt;&lt;P&gt;Could anyone please help us understand:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What triggers PSMSessionAlert.exe in this scenario?&lt;/LI&gt;&lt;LI&gt;Why is it failing while the SCCM application itself launches successfully?&lt;/LI&gt;&lt;LI&gt;What logs/configuration should we check to identify the root cause?&lt;/LI&gt;&lt;LI&gt;Is there a recommended solution to prevent this popup?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks in advance for your help.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Sep 2026 12:42:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385660#M4665</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-04T12:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385661#M4666</link>
      <description>&lt;P&gt;Without seeing the script it will be hard to help troubleshooting&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 07:12:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385661#M4666</guid>
      <dc:creator>NorbertBohusch</dc:creator>
      <dc:date>2026-09-08T07:12:45Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385662#M4667</link>
      <description>&lt;P&gt;Hi @Norbert Bohusch​&amp;nbsp;please find the AutoIt script below.&lt;/P&gt;&lt;P&gt;This is the complete script we are using for the SCCM PSM Connection Component. Please let me know if you need any additional logs or configuration details for troubleshooting.&lt;/P&gt;&lt;P&gt;#AutoIt3Wrapper_UseX64=Y&lt;/P&gt;&lt;P&gt;Opt("MustDeclareVars", 1)&lt;/P&gt;&lt;P&gt;AutoItSetOption("WinTitleMatchMode", 3) ; EXACT_MATCH!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;;============================================================&lt;/P&gt;&lt;P&gt;;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;PSM AutoIt Dispatcher Skeleton&lt;/P&gt;&lt;P&gt;;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;------------------------------&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;; Use this skeleton to create your own&lt;/P&gt;&lt;P&gt;; connection components integrated with the PSM.&lt;/P&gt;&lt;P&gt;; Areas you may want to modify are marked&lt;/P&gt;&lt;P&gt;; with the string "CHANGE_ME".&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;; Created : April 2013&lt;/P&gt;&lt;P&gt;; Cyber-Ark Software Ltd.&lt;/P&gt;&lt;P&gt;;============================================================&lt;/P&gt;&lt;P&gt;#include "PSMGenericClientWrapper.au3"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;; Consts &amp;amp; Globals&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;Global Const $DISPATCHER_NAME = "PSMAutoItDispatcher_SCCM"&lt;/P&gt;&lt;P&gt;Global Const $CLIENT_EXECUTABLE	= "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe"&lt;/P&gt;&lt;P&gt;Global Const $CLIENT_WORKING_DIR = "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin"&lt;/P&gt;&lt;P&gt;Global Const $ERROR_MESSAGE_TITLE = "PSM " &amp;amp; $DISPATCHER_NAME &amp;amp; " Dispatcher error message"&lt;/P&gt;&lt;P&gt;Global Const $LOG_MESSAGE_PREFIX = $DISPATCHER_NAME &amp;amp; " Dispatcher - "&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Global $TargetUsername&lt;/P&gt;&lt;P&gt;Global $TargetPassword&lt;/P&gt;&lt;P&gt;Global $TargetAddress&lt;/P&gt;&lt;P&gt;Global $TargetLogonDomain&lt;/P&gt;&lt;P&gt;Global $ConnectionClientPID = 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;; Code&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;Exit Main()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;; Main&lt;/P&gt;&lt;P&gt;;=======================================&lt;/P&gt;&lt;P&gt;Func Main()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; Init PSM Dispatcher utils wrapper&lt;/P&gt;&lt;P&gt;	ToolTip ("Initializing...")&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_Init() &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	LogWrite("successfully initialized Dispatcher Utils Wrapper")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; Get the dispatcher parameters&lt;/P&gt;&lt;P&gt;	FetchSessionProperties()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	LogWrite("mapping local drives")&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_MapTSDrives() &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	LogWrite("starting client application")&lt;/P&gt;&lt;P&gt;	ToolTip ("Starting " &amp;amp; $DISPATCHER_NAME &amp;amp; "...")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; ------------------&lt;/P&gt;&lt;P&gt;	; Handle login here! ; CHANGE_ME&lt;/P&gt;&lt;P&gt;	; ------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;LogWrite("Starting SCCM client application")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;ToolTip("Starting SCCM Console...")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;$ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,1, '"' &amp;amp; $CLIENT_EXECUTABLE)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	if ($ConnectionClientPID == 0) Then&lt;/P&gt;&lt;P&gt;		Error(StringFormat("Failed to execute process [%s]", $CLIENT_EXECUTABLE, @error))&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; Send PID to PSM so recording/monitoring can begin&lt;/P&gt;&lt;P&gt;	; Notice that until we send the PID, PSM blocks all user input.&lt;/P&gt;&lt;P&gt;	LogWrite("sending PID to PSM")&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_SendPID($ConnectionClientPID) &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; Terminate PSM Dispatcher utils wrapper&lt;/P&gt;&lt;P&gt;	LogWrite("Terminating Dispatcher Utils Wrapper")&lt;/P&gt;&lt;P&gt;	PSMGenericClient_Term()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	Return $PSM_ERROR_SUCCESS&lt;/P&gt;&lt;P&gt;EndFunc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;;==================================&lt;/P&gt;&lt;P&gt;; Functions&lt;/P&gt;&lt;P&gt;;==================================&lt;/P&gt;&lt;P&gt;; #FUNCTION# ====================================================================================================================&lt;/P&gt;&lt;P&gt;; Name...........: Error&lt;/P&gt;&lt;P&gt;; Description ...: An exception handler - displays an error message and terminates the dispatcher&lt;/P&gt;&lt;P&gt;; Parameters ....: $ErrorMessage - Error message to display&lt;/P&gt;&lt;P&gt;; 				&amp;nbsp;&amp;nbsp;$Code 		 - [Optional] Exit error code&lt;/P&gt;&lt;P&gt;; ===============================================================================================================================&lt;/P&gt;&lt;P&gt;Func Error($ErrorMessage, $Code = -1)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; If the dispatcher utils DLL was already initialized, write an error log message and terminate the wrapper&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_IsInitialized()) Then&lt;/P&gt;&lt;P&gt;		LogWrite($ErrorMessage, True)&lt;/P&gt;&lt;P&gt;		PSMGenericClient_Term()&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	Local $MessageFlags = BitOr(0, 16, 262144) ; 0=OK button, 16=Stop-sign icon, 262144=MsgBox has top-most attribute set&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	MsgBox($MessageFlags, $ERROR_MESSAGE_TITLE, $ErrorMessage)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	; If the connection component was already invoked, terminate it&lt;/P&gt;&lt;P&gt;	if ($ConnectionClientPID &amp;lt;&amp;gt; 0) Then&lt;/P&gt;&lt;P&gt;		ProcessClose($ConnectionClientPID)&lt;/P&gt;&lt;P&gt;		$ConnectionClientPID = 0&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	Exit $Code&lt;/P&gt;&lt;P&gt;EndFunc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;; #FUNCTION# ====================================================================================================================&lt;/P&gt;&lt;P&gt;; Name...........: LogWrite&lt;/P&gt;&lt;P&gt;; Description ...: Write a PSMWinSCPDispatcher log message to standard PSM log file&lt;/P&gt;&lt;P&gt;; Parameters ....: $sMessage - [IN] The message to write&lt;/P&gt;&lt;P&gt;;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;$LogLevel - [Optional] [IN] Defined if the message should be handled as an error message or as a trace messge&lt;/P&gt;&lt;P&gt;; Return values .: $PSM_ERROR_SUCCESS - Success, otherwise error - Use PSMGenericClient_PSMGetLastErrorString for details.&lt;/P&gt;&lt;P&gt;; ===============================================================================================================================&lt;/P&gt;&lt;P&gt;Func LogWrite($sMessage, $LogLevel = $LOG_LEVEL_TRACE)&lt;/P&gt;&lt;P&gt;	Return PSMGenericClient_LogWrite($LOG_MESSAGE_PREFIX &amp;amp; $sMessage, $LogLevel)&lt;/P&gt;&lt;P&gt;EndFunc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;; #FUNCTION# ====================================================================================================================&lt;/P&gt;&lt;P&gt;; Name...........: PSMGenericClient_GetSessionProperty&lt;/P&gt;&lt;P&gt;; Description ...: Fetches properties required for the session&lt;/P&gt;&lt;P&gt;; Parameters ....: None&lt;/P&gt;&lt;P&gt;; Return values .: None&lt;/P&gt;&lt;P&gt;; ===============================================================================================================================&lt;/P&gt;&lt;P&gt;Func FetchSessionProperties() ; CHANGE_ME&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_GetSessionProperty("Username", $TargetUsername) &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_GetSessionProperty("Password", $TargetPassword) &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;	if (PSMGenericClient_GetSessionProperty("Address", $TargetAddress) &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;if (PSMGenericClient_GetSessionProperty("LogonDomain", $TargetLogonDomain) &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then&lt;/P&gt;&lt;P&gt;		Error(PSMGenericClient_PSMGetLastErrorString())&lt;/P&gt;&lt;P&gt;	EndIf&lt;/P&gt;&lt;P&gt;EndFunc&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 08:58:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385662#M4667</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-08T08:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385663#M4668</link>
      <description>&lt;P&gt;It might be that the process which is started by the RunAs has a different PID then the finally running process of the SCCM client.&lt;/P&gt;&lt;P&gt;And it might not catch that properly for monitoring.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 09:11:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385663#M4668</guid>
      <dc:creator>NorbertBohusch</dc:creator>
      <dc:date>2026-09-08T09:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385664#M4669</link>
      <description>&lt;P&gt;I checked the PID in both Task Manager and the PSM Connection Component logs.&lt;/P&gt;&lt;P&gt;The PID returned for the SCCM process is the same in both Task Manager and the Connection Component logs.&lt;/P&gt;&lt;P&gt;So, based on this check, the PID returned by&lt;/P&gt;&lt;P&gt;RunAs()&lt;/P&gt;&lt;P&gt;appears to be the same as the actual running SCCM process.&lt;/P&gt;&lt;P&gt;Please let me know if there is anything else I should check regarding the PID or process monitoring.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 10:10:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385664#M4669</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-08T10:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385665#M4670</link>
      <description>&lt;P&gt;Is there a reason for this " you add to the Client-Executable in the RunAs? &lt;/P&gt;&lt;P&gt;$ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,1, '"' &amp;amp; $CLIENT_EXECUTABLE)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First of all the variable is already a string, second you only have a starting double-quote but no ending one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 10:16:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385665#M4670</guid>
      <dc:creator>NorbertBohusch</dc:creator>
      <dc:date>2026-09-08T10:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385666#M4671</link>
      <description>&lt;P&gt;I removed the additional double quote and changed the line to:&lt;/P&gt;&lt;P&gt;$ConnectionClientPID = RunAs($TargetUsername, $TargetLogonDomain, $TargetPassword, 1, $CLIENT_EXECUTABLE)&lt;/P&gt;&lt;P&gt;I tested the connection component again, but the behavior is still the same. SCCM launches successfully, and the&lt;/P&gt;&lt;P&gt;PSMSessionAlert.exe – This application could not be started&lt;/P&gt;&lt;P&gt;popup still appears.&lt;/P&gt;&lt;P&gt;So the quote does not appear to be the cause of the popup.&lt;/P&gt;&lt;P&gt;Could you please advise what else we should check?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 10:28:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385666#M4671</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-08T10:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385667#M4672</link>
      <description>&lt;P&gt;The only question which comes to my mind is if you are testing as a Connection-Component already or if you started it manually with AutoIT from CLI (https://community.cyberark.com/s/article/00004913)? I would recommend the 2nd option.&lt;/P&gt;&lt;P&gt;Else I have no idea.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 10:31:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385667#M4672</guid>
      <dc:creator>NorbertBohusch</dc:creator>
      <dc:date>2026-09-08T10:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSessionAlert.exe – “This application could not be started” popup when launching SCCM through AutoIt PSM Connection Component</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385668#M4673</link>
      <description>&lt;P&gt;We are currently testing the AutoIt script through the PSM Connection Component, and the PSMSessionAlert.exe – The application could not be started popup occurs only in that scenario.&lt;/P&gt;&lt;P&gt;The target application itself launches successfully despite the popup appearing in the background.&lt;/P&gt;&lt;P&gt;We also tested launching the AutoIt script manually from CLI, as suggested in the article. In that test, the application launched successfully without the popup.&lt;/P&gt;&lt;P&gt;However, we have not yet performed the exact CLI test from the PSM component server using the PSM Shadow User session as described in the article, because we would need to reset/recreate the Shadow User password to perform that test.&lt;/P&gt;&lt;P&gt;Based on the current testing:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;PSM Connection Component → Application launches, but PSMSessionAlert.exe popup appears.&lt;/LI&gt;&lt;LI&gt;Normal CLI execution → Application launches successfully, no popup.&lt;/LI&gt;&lt;LI&gt;PSM Shadow User CLI test → Not yet performed.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Would the PSM Shadow User CLI test be necessary to further isolate whether the issue is related to the PSM session/Shadow User context or the Connection Component configuration?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 11:37:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psmsessionalert-exe-this-application-could-not-be-started-popup/m-p/1385668#M4673</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-08T11:37:29Z</dc:date>
    </item>
  </channel>
</rss>

