Powershell 3.0 Start-Process disregards -Wait Parameter when invoked Remotely - by audio4ears

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774903 Comments
Status Resolved Workarounds
Type Bug Repros 7
Opened 12/20/2012 4:03:19 PM
Access Restriction Public


When Invoking a Start-Process command remotely it appears that the -Wait parameter is disregarded. This issue is new to Powershell 3.0. Powerhsell 2.0 handled the -Wait parameter correctly.

When the Start-Process cmd-let is ran locally in Powershell 3.0 the -Wait parameter functions as expected.  The issue just occurs when invoked remotely.

Tested using: Windows Web Server 2008 x64 R2
Sign in to post a comment.
Posted by Jason [MSFT] on 11/23/2015 at 12:58 PM
Thanks for the bug report. We have verified that this has been fixed in the latest version of WMF 5.0.
Posted by Dave E 968 on 7/15/2013 at 3:40 AM
This is similar to http://connect.microsoft.com/PowerShell/feedback/details/776078/powershell-ignores-wait-request-on-start-process-when-ps-is-run-as-a-win32-job#tabs?