mmdbresolve.exe could not be removed. Is it in use?

asked 2019-06-12 16:20:51 +0000

I need to uninstall Wireshark 3.0.0 from a computer and I get the above error. I have run task manager and the process is not running for any user. It's important that I remove this from this computer, how can I get it removed?

edit retag flag offensive close merge delete

Comments

Can you double-check your process list? It should exit automatically when Wireshark is closed.

Lekensteyn gravatar imageLekensteyn ( 2019-06-12 20:54:08 +0000 )edit

I have, in fact I have the screen capture to prove it but I don't think I can attach pictures here.

avandehei gravatar imageavandehei ( 2019-06-12 21:01:35 +0000 )edit

Try rebooting the computer and then running the uninstall.

grahamb gravatar imagegrahamb ( 2019-06-12 22:01:46 +0000 )edit

Thanks for the suggestion but I did that several times already. Also wanted to mention here that this is on a Server 2008 R2 OS just in case that makes a difference. Since it's on a domain and Wireshark was installed before it was added to the domain, I also logged in as the local administrator, made sure I had full control of the Program Files/Wireshark directory and still got the same error. We are allowed to use Wireshark on our network for terms of less than 90 days for troubleshooting only. After that it must be removed. I'm getting heat to get this removed but just can't do it. If delete the directory it will still be in the registry so it won't get the server off the 'bad boy" list. Thanks again for the help!

avandehei gravatar imageavandehei ( 2019-06-12 22:09:11 +0000 )edit

The normal reason for this error message is that the process from the file is still running, so it's odd that you can't see a running process and it remains this way even after a reboot. Is it possible that someone has set Wireshark to autostart?

I guess you could manually delete all the files in the Program Files\Wireshark directory that you can, likely just the troublesome one will be left, then reboot and nothing should be starting up that process and you can do a final cleanup.

I did wonder if it were a permission problem but the steps you've taken and the error message make that unlikely.

grahamb gravatar imagegrahamb ( 2019-06-12 22:31:49 +0000 )edit