How to create a process and kill the parent in windows

Question

1.00/5 (1 vote)

See more:

Hi all

I have an mfc - application: foo.exe.

Now i want this foo.exe to create a process of itself and kill itself.

(I simply want to create a new process of itself and kill the old one.)

I tried this like that:

CreateProcess("path of foo.exe", NULL, NULL, NULL, FALSE, NORMAL_PRIORITY_CLASS, NULL, "directory of the foo.exe", &startup, &info);

PostQuitMessage(0);

But: This does not work, it comes up a message box.... if i click ok there, it works. (in german, the text of the messagebox is "server ausgelastet" which means that the server is busy. (this is an ole message)

Does anyone has a solution to this problem?

Thx alot!

Posted 28-Apr-15 5:03am

Member 10781325

Add a Solution

Comments

nv3 28-Apr-15 11:27am

Could you provide the following information in order to help:
1. What is the return code of the CreateProcess call?
2. Put a breakpoint on the PostQuitMessage call and see, if the new process is created correctly before trying to terminate the old process.
3. Which process is the owner of the message box? (You can check with Spy++, which is a tool that is part of Visual Studio)

Could it be that this message box is generated as part of your MFC application. Some application check on startup whether they are already running in another instance. Perhaps that is where the message box comes from.

[no name] 28-Apr-15 19:59pm

This may be what you need: http://www.codeproject.com/Articles/15184/How-To-Create-a-Self-Restartable-Application

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-04-28T11:33:00

The trouble is: PostQuiteMessage does not work in all situations. It posts WM_QUITE, so you should assume that all conditions work the way that it would lead to application termination eventually: the message loop is being still executed, messages are being processed, and so on. Please see: https://msdn.microsoft.com/en-us/library/windows/desktop/ms644945%28v=vs.85%29.aspx[^].

This is probably not the case. As you did not provide any information on the state of your process, I have no idea what is it. It could be anything, really.

The hard way of terminating the process (yes, you can terminate your current process) is this:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms683179%28v=vs.85%29.aspx[^],
https://msdn.microsoft.com/en-us/library/windows/desktop/ms686714%28v=vs.85%29.aspx[^].

Better avoid doing it by all means.

Many would say that the idea to kill the current process in this way is abusive. And I will agree with this opinion. I will only add that the whole idea to terminate the current process (even nicely) and start another instance of the same application is itself a pretty strong indication of technology abuse. If you need more help, you will need to explain some motivation of what you are doing, and your ultimate goals. Chances are, you will be suggested more reasonable alternative.

—SA