none
Vista. Disabling tunmp service makes command "PSExec -i -s -d cmd " not worked. RRS feed

  • Question

  • I have disable tunmp service by registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tunmp\Start=4

    Then psexec (https://technet.microsoft.com/en-us/sysinternals/bb896649.aspx) does not work . It gives error:

    Error establishing communication with PsExec service on WINVISTA

    The network path was not found

    As  I can see psexesvc service cannot create pipe , so then when psexec calls CreateFileW \\WINVISTA\pipe\PSEXESVC it returns ffffffff and getlasterror = 53.

    Sunday, July 12, 2015 6:33 PM

All replies

  • This is a required Windows service don't disable it.  If you think you have a malware version, then either get the real version off a recovery disk, or go onto the web and search for tunmp.sys there are places that will point you to the safe one.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    Sunday, July 12, 2015 7:21 PM
  • This is a required Windows service don't disable it.  If you think you have a malware version, then either get the real version off a recovery disk, or go onto the web and search for tunmp.sys there are places that will point you to the safe one.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    Why there is no such service in Win7 or WinXP? What is the purpose of tunmp?

    Is this the same as tun adapter from OpenVPN package (http://swupdate.openvpn.org/community/releases/openvpn-install-2.3.6-I002-i686.exe)?

    It's just additional network adapter (I can install dozen of them , e.g. loopback adapter and so on). How can it affect psexec?

    And I am disabling services because they do nothing good (even you can't say, what it does) but eat computer resources.

    • Edited by ooligo4_3 Sunday, July 12, 2015 8:15 PM
    Sunday, July 12, 2015 8:07 PM
  • Just 'know' tunmp.sys from this IPv6 tunneling thing:

    With kind regards

    Sunday, July 12, 2015 11:52 PM
  • I have try disable IPv6 (like is  suggested support.microsoft.com/en-us/kb/929852) ,

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents=FF

    Now when "ping winvista" I see not ::1: but 127.0.0.1. But psexec still gives me same error.

    Monday, July 13, 2015 6:28 AM
  • Sorry, cannot reproduce, disabling tunmp - psexec seems to work on my box (Vista_x86) ...

    With kind regards

    Monday, July 13, 2015 10:15 AM
  • Yes. Sometimes it works but after few reboots it gives error.

    I use Vista image from here http://www.microsoft.com/en-us/download/confirmation.aspx?id=11575

    <strike>
    </strike>
    • Edited by ooligo4_3 Monday, July 13, 2015 1:23 PM
    Monday, July 13, 2015 12:22 PM
  • Related to https://social.msdn.microsoft.com/Forums/en-US/91b0f8e0-1742-489a-88d5-6cc5e7420589/win7-ie9-psexec-i-s-d-cmd-does-not-work
    Wednesday, July 15, 2015 11:37 AM