Forum Discussion
kjadhavkunal wrote:
The problem was with my machine. Though I re-installed internet explorer11. There was 'iexplore.exe' service running even if we close the browser.
Did you manage to fix it in the end?
Interested to hear how if you'd already tried re-installing IE, and that didn't fix it first time ....
** EDIT **
I'm not sure the code from sanjay0288 would work here as it relies on counts of browsers to determine loop lengths. And I'm not sure if the invisible one in this case would be caught that way.
However, if you modified to look for all instances of the "iexplore*" process (with the wildcard there to catch any "*32" versions) and kill those, it might have done it. Even with the dodgy invisible version hiding in the background.
ie. Use processes to drive the loop. Not browser instances.
As I said before, its not about closing instances of a browser. I am able to see the browser is closed. But when I go to Task Manager, there is process for the same in running state.
Also, it was working fine on my machine yesterday. When I returned back from 30 minutes break again found the same issue. Currently working from another machine. Is it something machine specific?
Please help with the solutions.
Thank you in advance!
- sanjay02889 years agoFrequent Contributor
Kill the instances at the process level. The code to achieve the same has already been shared in the previous posts.
For the second part of the problem not sure why the process always be in running state. Because of the addons you could be facing this issue. You can try going through the below mentioned link to figure out the root cause of the problem.
- Colin_McCrae9 years agoCommunity Hero
The last few posts ARE the solution!
Kill it at process level. Simply make sure you find and terminate all the possible variations of the process. It's pretty simple to do. A search with a wildcard (or two searches if using a * to search for a * doesn't work), and then a loop (or loops - but easy enough to get both search results into the same array if you do two searches) to kill off the found processes.
That should get round the problem., But no idea why your PC is leaving bits of process behind.