Teredo Tunneling Pseudo-Interface This device cannot start. (Code 10)

I have a yellow ? in my Device Manager entry for the Teredo Tunneling Pseudo-Interface. This is a 3 week old Windows 7 64bit machine. I saw messages similar to this in this forum and have run an ipconfig /all with the following results:

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : KandE-PC

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : domain.actdsltmp

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : domain.actdsltmp

   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller

   Physical Address. . . . . . . . . : 44-87-FC-40-76-6F

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Tuesday, March 23, 2010 8:31:13 AM

   Lease Expires . . . . . . . . . . : Saturday, March 27, 2010 1:07:41 PM

   Default Gateway . . . . . . . . . : 192.168.0.1

   DHCP Server . . . . . . . . . . . : 192.168.0.1

   DNS Servers . . . . . . . . . . . : 192.168.0.1

                                       205.171.3.25

   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Windows\system32>

C:\Windows\system32>

______________________end of ipconfig data____________________

I would be most appreciative if you can help me with this (apparently) slight problem. I do not know that this situation is causing me any difficulty but I like to keep my computer running well.

Thanks in advance,

Chuck

Remember that the "teredo tunneling" is a PSEUDO interface, that means that it works without drivers.... searching for it is a waste of time!

The only good or workable solution is this one (I have put this already so many times on this forum and it always worked):

In the start menu(left corner below) search bar type in REGEDIT in capital letters( and click on it when it appears under the words programs) and open the registry editor.  Navigate through the following:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\TCPIP6\PARAMETERS. first click on  the little arrow before the word HKEY_LOCAL_MACHINE and scroll down almost to the end and click on the little arrow before SYSTEMand then same way on controle set (here it is possible to have more than one controle set, so try them one by one until you find SERVICES, TCPIP6 and PARAMETER , Then in the right pane, right click Disabled Components and select edit.  Set the DWord value to 0."

Hey everyone, I had the same code 10 problem with Teredo Tunnel  Pseudo-Interface when I connected my laptop with a public library router. Fortunately I found this solution which really worked it out! (My OS is Vista x64 SP2, but I think XP and Win7 can also follow the same solution)

Solution:

1. Open command prompt with administrator credentials (Find CMD and right-click - Run as Administrator).
2. Enter netsh environment. Type "netsh" and ENTER.
3. "int teredo" and ENTER
4. "set state disabled" and ENTER.
5. Open Device Manager and uninstall "Teredo Tunneling Pseudo-Interface".
6. Open command prompt with administrator credentials once again.
7. netsh + ENTER.
8. "int ipv6" + ENTER
9. "set teredo client" + ENTER
10. Open Device Manager and Scan for new hardware.
11. Select "Show hidden devices" from the View menu. You will now see that it is present without errors with any luck.

Sources:

http://forums.techarena.in/hardware-peripherals/892007.htm

http://www.microsoft.com/technet/net...v6/teredo.mspx

worked perfectly.

As mentioned in my post from the 2015-05-03, the issues raised concerning the “MicrosoftTeredo Tunneling Adapter” returning a code10 error, are not as strait forward and can have various causes as indicated by the multitude of solutions, to resolve the issue, proposed in this thread.

I found that irrespective of the cause of the error a sure way of drilling down on the problem is to use, Microsoft SysInternals, Process Monitor (currently ver.3.2, https://technet.microsoft.com/en-gb/sysinternals/bb896645) as mentioned in a post submitted on 2012-07-17 to reddit>sysadmin "Windows XP Registry Changes Reverting after Reboot" at: http://www.reddit.com/r/sysadmin/comments/wpdmn/windows_xp_registry_changes_reverting_after_reboot/

http://www.reddit.com/r/sysadmin/comments/wpdmn/windows_xp_registry_changes_reverting_after_reboot/

1. I set the registry value: HKLM\System\CurrentControlSet\services\TCPIP6\Parameters\Interfaces = 0
2. Checked and set "Run services.msc":

 Peer Networking Grouping = Started-Automatic

 PNRP Machine Name Publication Service = Started-Automatic

3. Checked and installed if not present:

 Device Manager>View>Show hidden devices = ticked

 Network adabtors: 

  MS Teredo Tunneling, ISATAP and 6to4 adabter are installed.

4. Enabled "Boot Logging" in Process Monitor>Options

This allowed me to discover the process that is Changing the Registry Value to 0x8e (142)

Resolving the issue then depends on figuring out why and how the process in question is behaving the way it dose and causing the reseting of the registry value. In my case it was a badly coded third party driver that was causing the issue.