VB6.0 application process does not Exit under Windows 7

[Sachin100]

My VB6.0 application process does not Exit under Win 7 but it exits properly on Win XP. After exiting the application process VB6 exe remains running in Task Manager. So every time I need to manually end that process. Is there any way to release all resources held by VB6.0 exe & VC++ dlls on Win 7 OS through VB6/C++ code.

 

[EzioAuditore]

One way i can think of is to create a batch file and pin it to taskbar. Save your work and click the pinned item to terminate it.

taskkill /im /f <insertprocessnamehere>

You can also use Process Explorer to see, after closing normally, which files (dll's etc) remain loaded by the program's process to identify the conflicting ones.
technet.microsoft.com/en-us/sysinternals/bb896653

 

[Sachin100]

Thanks Ezio..Earlier I used taskkill option..but as per code review comments-"do not use taskkill option" so I am exploring other options to release the resources.

I think Dlls are not unloading properly & holding the resources thatswhy Exe is running in background. If I tried to explicitly unload Dll, then application hangs & do not close.

your link displays
Error. Page cannot be displayed. Please contact your service provider for more details. (6)

 

[EzioAuditore]

Oh sorry, I edited the link in my previous post. Check now.

 

[Sachin100]

Solved!!

Thanks Ezio..first I used Process Explorer and I found some of the Dlls were not released. so to localise the problem I used Dependency Walker tool. I observed that application control stuck at one of the Dll and was not moving ahead and releasing other resources.

Finally, I sent a call to that Dll to release the resources and it worked. I dont know exactly what's difference in Win 7 and Win XP at Dll level where Win 7 was not releasing the Handles of the Dll which Win Xp does.

 

[EzioAuditore]

Thanks Ezio..first I used Process Explorer and I found some of the Dlls were not released. so to localise the problem I used Dependency Walker tool. I observed that application control stuck at one of the Dll and was not moving ahead and releasing other resources.

Finally, I sent a call to that Dll to release the resources and it worked. I dont know exactly what's difference in Win 7 and Win XP at Dll level where Win 7 was not releasing the Handles of the Dll which Win Xp does.

Thats a great news. Glad its solved.
Windows has come a long way down from XP to 7 both in features and working. If you notice any program behaving erratically, try running it in Compatibility Mode.