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

Anonymous
2010-03-26T19:13:02+00:00

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

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-03-27T14:40:05+00:00

Hi,

First lets follow these below steps and  check if the issue gets resolved.

Right click the Teredo Tunneling Pseudo-Interface > Update Driver Software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer ->  network Adapter > Microsoft > Microsoft teredo tunneling adapter

To troubleshoot your issue you may try the below methods one by one.

The error message you posted indicates that you have an incompatible driver or the device driver is missing.

To make sure that you download the correct and the most up-to-date version of the driver driver, visit the Motherboard manufacturer’s website wherein all the drivers will be listed. Select the appropriate driver for the device that is compatible with Windows 7.

You may uninstall the existing driver from device manager before installing the new one.

1.    Open Device Manager by clicking the Start button, clicking Control Panel , clicking System and Maintenance, and then clicking Device Manager.

 If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

2.    Locate the sound card, right click on it and select properties .

3.    Go to driver tab and click on Uninstall button to uninstall the driver associated with the device.

Once the uninstall completes, restart your computer and check if the issue got resolved.

Thanks and Regards:

I. Suuresh Kumar- Microsoft Support.

Visit our Microsoft Answers Feedback Forum and let us know what you think.

Was this answer helpful?

100+ people found this answer helpful.
0 comments

190 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-09-15T21:48:17+00:00

    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

    Looks like this solution solved my problem.. Thank you a bunch!!!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2011-09-09T08:10:48+00:00

    Great! Finally this is the right answer :

    • In the Registry, open:
    • HKEY_LOCAL_MACHINE
    • SYSTEM
    • CURRENTCONTROLSET
    • SERVICES
    • TCPIP6
    • PARAMETERS
    • On the right pane, the value named
    • "Disabled Components"
    • must be set to DWord: 0, or must be deleted (0 is its default value).

    This hidden registry setting was set mysterioulsy at one time (I don't know which tool or Windows update has defined it, but this was effectively blocking Teredo from starting, causing the code 10, even if its driver was properly installed, and its parameters correctly defined in "netsh" !

    Unfortunately, NONE of the "Problem solvers" proposed by Microsoft detect this hidden registry setting, which is also not exposed in the "netsh" interface and neither by any UI components of the "Devices Manager", or of the "Network center" in the Windows Explorer, or the Devices and Printers folder in the Control Panel.

    I really hate those STUPID hidden registry settings that are documented nowhere !

    The only correct way to disable Teredo should be either:

    • in "netsh", entering "interface teredo", then "set state disabled" (this does not affect the registry setting above but another one)
    • in the Devices manager: uninstalling Teredo, or disabling the driver from there.

    Note: once you have uninstalled the Teredo driver, it will NOT reinstall magically by scanning for new hardware, because this is NOT a Plug'n Play device. To reinstall it you have to manually install it as a legacy driver, that you'll find by "Add driver > Manual installation > Netwok Interface > Select driver > Microsoft > Microsoft Teredo Tunneling Pseudo-interface.

    Note that uninstalling and reinstalling the Microsoft Teredo driver DOES NOT affect the TCPIP6 parameters in the registry (described above), which remains there. Another reason why this HIDDEN Registry setting is completely stupid and should only have been used by Microsoft for testing/debugging purposes, but NEVER in a production driver.

    If Microsoft really wants to keep this registry setting, the TCPIP6 driver should LOG somewhere the presence of this parameter, and the the TEREDO driver should also LOG the presence of this parameter before bailing out with such stupid "code 10" which never explains the cause.

    Seriously, those stupid registry settings are a major cause of failures in Windows, some malwares are using it to block some essential Wndows components from starting. Please Microsoft, remove those stupid hdden registry parameters.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2010-04-06T11:33:01+00:00

    Hi Chuckjo:

    I have the same problems and receive the same messages.  I have completed all the steps suggested by MS to no avail.  Also have AVG but turned off all firewalls and anti-virsus programs...to no avail.  Also tried to run in safe mode with networking...to no avail.  You have one good point.  How does one get the manufacturer's driver for the software?  In my case MS is the manufacturer.  They make no suggestion as to how we may locate and install the driver.  As a note there are over 80,000 posts on this issue and no solutions posted by MS other that the same old routine we have run through.  Mine is a new HP with W7.

    Good luck and lets hope MS response with a better solution.  By now they should have worked this out.  it's been months since the first post.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments