Path: csiph.com!aioe.org!wIgm+2MIUUYkuZKIR0Uhug.user.gioia.aioe.org.POSTED!not-for-mail From: "R.Wieser" Newsgroups: microsoft.public.scripting.vbscript Subject: Re: wshshell.run a shortcut and waiting for it to finish. How ? Date: Mon, 16 Nov 2020 17:10:38 +0100 Organization: Aioe.org NNTP Server Lines: 24 Message-ID: References: <1dgatp0jyrk48.1utdkn8x5nbwt.dlg@40tude.net> NNTP-Posting-Host: wIgm+2MIUUYkuZKIR0Uhug.user.gioia.aioe.org X-Complaints-To: abuse@aioe.org X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-Notice: Filtered by postfilter v. 0.9.2 X-MSMail-Priority: Normal X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Xref: csiph.com microsoft.public.scripting.vbscript:12299 JJ, > IME, that problem can occur when `WshShell.Run()` ends up > delegating the new process creation to an already existing process. hmmm... I assumed that it could be a case of a process being started which than starts another one. The first one is monitored but returns directly, which is detected and causes the error to be displayed. As for being delegated to an already existing process ? 1) I only get the error when starting those scripts thru a shortcut, 2) I have started a script (a simple "hello" box) thru a shortcut trice, and can see three "wscript.exe" processes running in the task manager. > This kind of problem shouldn't occur for simple file associations > such as TXT, BAT, EXE, VBS, etc. Indeed they do. But as I'm using shortcuts as intended I expected them to work too. Regards, Rudy Wieser