Powershell explorer process exits immediately after using Start-Process












0















I'm using the following command to spawn an explorer window:



PS C:> $er3 = (Start-Process explorer -passthru)


I'd like to access its mainWindowHandle for another task but it is returning nothing



PS C:> $er3.MainWindowHandle
(nothing)


I'm noting that the process has exited, even though the filebrowser explorer window stays open on my desktop.... is there a way to keep this process running so I can access its mainWindowHandle?



PS C:> $er3.HasExited
True









share|improve this question




















  • 2





    I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

    – Lieven Keersmaekers
    Dec 17 '18 at 7:12
















0















I'm using the following command to spawn an explorer window:



PS C:> $er3 = (Start-Process explorer -passthru)


I'd like to access its mainWindowHandle for another task but it is returning nothing



PS C:> $er3.MainWindowHandle
(nothing)


I'm noting that the process has exited, even though the filebrowser explorer window stays open on my desktop.... is there a way to keep this process running so I can access its mainWindowHandle?



PS C:> $er3.HasExited
True









share|improve this question




















  • 2





    I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

    – Lieven Keersmaekers
    Dec 17 '18 at 7:12














0












0








0








I'm using the following command to spawn an explorer window:



PS C:> $er3 = (Start-Process explorer -passthru)


I'd like to access its mainWindowHandle for another task but it is returning nothing



PS C:> $er3.MainWindowHandle
(nothing)


I'm noting that the process has exited, even though the filebrowser explorer window stays open on my desktop.... is there a way to keep this process running so I can access its mainWindowHandle?



PS C:> $er3.HasExited
True









share|improve this question
















I'm using the following command to spawn an explorer window:



PS C:> $er3 = (Start-Process explorer -passthru)


I'd like to access its mainWindowHandle for another task but it is returning nothing



PS C:> $er3.MainWindowHandle
(nothing)


I'm noting that the process has exited, even though the filebrowser explorer window stays open on my desktop.... is there a way to keep this process running so I can access its mainWindowHandle?



PS C:> $er3.HasExited
True






windows-7 powershell process






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 17 '18 at 5:32







Ryu S.

















asked Dec 17 '18 at 5:08









Ryu S.Ryu S.

84




84








  • 2





    I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

    – Lieven Keersmaekers
    Dec 17 '18 at 7:12














  • 2





    I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

    – Lieven Keersmaekers
    Dec 17 '18 at 7:12








2




2





I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

– Lieven Keersmaekers
Dec 17 '18 at 7:12





I don't have a readily solution but following is in short what is happening: Your Explorer process checks if there's already an Explorer process running. If it's not, it will start as a new shell. If there is, it will delegate to the existing Explorer process wich will start an Explorer window after wich your process terminates.

– Lieven Keersmaekers
Dec 17 '18 at 7:12










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1385142%2fpowershell-explorer-process-exits-immediately-after-using-start-process%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1385142%2fpowershell-explorer-process-exits-immediately-after-using-start-process%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Сан-Квентин

8-я гвардейская общевойсковая армия

Алькесар