Rather than "powermt remove", try "powermt check", or "powermt check force" if that doesn't work.

I have tried powermt check, remove and check force with the same results.

Even rebooting the production server does not help, the dead paths are still there.

search your system disk for powermt.custom ..rename it to something else and try running powermt check ..if that still does not remove it, reboot.

Thanks dynamox, but that did not work either. I found the powermt.custom file in C:\WINDOWS\system32\drivers\etc, renamed it and reran "powermt check dev=all". Same results. The path will not diappear.

I have rebooted and the path still comes back.

hmm ..that's weird ..my last resort would be to re-install powerpath.

I have exactly the same problem. Am using version 4.6 though.
I don't even seem to have a powermt.custom file. Why would this be?

powermt.custom file gets created whenever you run powermt save ..for example if you made setting changes within powerpath and want to save them..you would run powermt save. I have seen instances where i made changes on the storage side and i just could not force powerpath to reconfigure itself, so i was uninstall powerpath, re-install it ..and dead paths would not go away. So now if i cannot get powerpath to recognize changes elegantly (powermt config, powermt check ..etc) , i uninstall powerpath, remove powermt.custom and then reboot the system. Make sure to save the license key, i have had mixed luck where sometimes uninstall will remove the license key as well.

Uninstalled and upgraded to v5.1 and it seems to be fixed.
Thanks for the information