ProcessDialog & FilesInUseDialog

Hi,Can you clarify the two dialogs ProcessDialog & FilesInUseDialog ? ProcessDialog tells me for example my application exe needs to be closed - we can understand that. The second dialog telling application exe is in use by system.exe - even if i do nothing (not clicking any button) the update finishes successfully. Is this necessary ? What do i tell my users ?

Great software !

The process dialog warns about open processes in the "your app" directory. The File in use dialog warns about files in use.

The only way the user will get the "file in use" because of a running process is if the user opens a process in your app's folder after the update has begun (and already passed the running processes dialog).

Sorry to disagree, but I'm getting FilesInUse while waiting (patiently) update to do it's work. I.e. not opening any process anywhere.

What's queer is that - the process incriminated is called "(system.exe)" with the parenthesis. - And nobody on the internet seems to know about "system.exe" inside Windows, other than being a virus...

Any help appreciated !

If you're on Vista+ then wyUpdate actually lets you close the processes that are currently using the "in-use" file.

On Windows XP, you'll have to use another 3rd party piece of software: http://superuser.com/questions/13291/how-do-i-delete-a-locked-file

In short, wyUpdate is doing its job correctly. It's trying to update a file, but it's in-use, thus it can't update it. How do you solve this? Stop using the file before the update.

In my first message, I mentioned that the main application exe (which I'm updating) got ProcessesDialog.Then the FilesInUseDialog says that this same file application.exe is used by "(system.exe)". It seems that system.exe is a kind of scheduler that invokes application.exe, which is consistent with ProcessesDialog, like what you said, but kind of "redundant".

Question is: can I remove the second dialog ?

Question is: can I remove the second dialog ?

No, absolutely not. That dialog only comes up because wyUpdate is trying to update the file but can't (because, the file is in use -- hence the name).