Sei sulla pagina 1di 18

his tutorial fixes the following issues in device manager:

Microsoft Teredo Tunneling Adapter cannot start error: Code 10


Teredo Tunneling Pseudo Interface error: Code 10

How to solve Teredo Tunneling Error Code 10 (Device


cannot start).

Step 1. Modify TCPIPv6 Parameters through Windows Registry.


1. Open Windows Registry Editor. To do that:
1. Press Windows
+ R keys to load the Run dialog box.
2. Type regedit and press Enter.

IMPORTANT: Before you continue to modify the registry, first take a registry backup. To
do that:
a. From the main menu, go to File & select Export.
b. Specify a destination location (e.g. your Desktop), give a filename (e.g. RegistryBackup)
and press Save.

2. Inside Windows Registry, navigate (from the left pane) and highlight this key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Pa
rameters

3. At the right pane, double-click to modify the DisabledComponents key.

4. Set the DisabledComponents Value data to 0 (Zero) and select OK.

5. Close Registry Editor.


6. Restart your computer.
(Windows should reinstall Teredo Tunneling adapter automatically.)
7. Navigate to device management.
8. Check if the Teredo tunneling adapter exists and working in device manager. To do that:

From the View menu choose Show hidden devices.

If the device managers screen doesnt show any errors (and is without an exclamation
mark) next to MS Teredo Tunneling Adapter (like the screen below), then your problem is
solved and the Teredo tunneling should work without problems.

If you face a screen with a yellow exclamation mark next to Microsoft Teredo Tunneling
adapter (or the Teredo Tunneling Pseudo Interface) like the screen(s) below continue to
Step 2.

Step 2: Uninstall all Teredo Tunneling Adapters & Interfaces.


1. Right-Click and Uninstall the Teredo Tunneling Pseudo-Interface.

2. Uninstall also all Microsoft Teredo Tunneling Adapters (e.g. Microsoft Teredo Tunneling
Adapter #2 or #3 or #4, etc.)

3. Re-install Microsoft Teredo Tunneling Adapter by following the steps from this tutorial: How
to install Microsoft Teredo Tunneling Adapter
4. If after re-installing teredo tunneling, you still have problems then proceed to Step 3.

Step 3. Enable Teredo Client using NETSH command


1. Go to Start > All Programs > Accessories.
2. Right click at Command Prompt and select Run as Administrator

3. At command prompt window type the following commands in this order and press Enter after
typing each one of them.

netsh
int teredo

set state disabled

int ipv6

set teredo client

4. Close command prompt.


5. Open Device manager.

6. Select View > Show Hidden Devices. The Teredo Tunneling Pseudo Interface reappears and
should be working without problems now.
Thats it!
If you want to stay constantly protected from malware threats, existing and future ones, we
recommend that you install Malwarebytes Anti-Malware PRO by clicking below (we do earn a
commision from sales generated from this link, but at no additional cost to you. We have
experience with this software and we recommend it because it is helpful and useful):

Full household PC Protection - Protect up to 3 PCs with NEW Malwarebytes


Anti-Malware Premium!
If this article was useful for you, please consider supporting us by making a donation. Even $1
can a make a huge difference for us in our effort to continue fighting spam while keeping this
site free:
Remove SuperFish Adware Software (Adware Removal Guide) {FIX} Teredo Tunneling is
installed but missing in Device Manager or gives error code 10 after restart.
17 Comments

1.

Lisa Newlin
May 30, 2015 @ 17:40:16

THANK YOU!
Reply

2.

Aditi
Jun 15, 2015 @ 08:10:10

Thanks a ton!!!
Reply

3.

Bob
Jun 20, 2015 @ 18:56:43

Thank you for this!!! I owe you !!!

Reply

4.

Link
Jun 23, 2015 @ 13:38:05

Worked flawlessly. I appreciate the very detailed and clear instructions. I wasnt even
sure what that adapter did or why it suddenly started not working, but Im glad my PC is
once again free of any yellow exclamation signs.
Any idea what caused it to malfunction?
Reply

Link

Jun 24, 2015 @ 07:44:46

Okay I was mislead. It appeared to work for that day, but today, when I turned
the PC back on, the adapter once again is giving the Code 10 (cannot start). So,
me donating above through PayPal was a waste. What gives? Why is this adapter
suddenly not working?
Brand new PC: Asus Maximus Impact VII, Intel i7 4790k, nVidia GTX680, 16GB
of Kingston Beast DDR3 RAM, Windows 7 x64 Home Premium on a 1TB
Samsung 850Evo SSD.
Reply

lakonst
Jun 24, 2015 @ 11:17:18

@Link: I m really sorry for your problem. Do you have any firewall
program installed? If, so please uninstall it. (like AVG or Zone Alarm?
specially in ZA your have to Enable IPv6 checkbox in Firewall).
1. Make sure that all your drivers are updated.
2. Make sure that the IPv6 is enabled in network properties.
3. Set the value to 0 in registry and then restart your computer. (do not
uninstall/re-install teredo) If the problem persists then
4. Give these commands (in order, as Admin) and then restart your
computer:
netsh
int teredo

set state disabled


int ipv6
set teredo client
Reply

Bradley Brewer
Jun 25, 2015 @ 11:46:03

I had replied with more information, but it seems yall deleted it.
The only security programs I have installed are the same ones Ive
been using for years: Windows Firewall, Avast Free Antivirus, and
Malwarebytes Anti-Exploit Free. I have checked through and
through them looking for anything dealing with IPv6 options and
there is nothing restricting listed.
1. My drivers are all up to date, as always, on both computers on
my network.
2. IPv6 is enabled on both computers.
3. I have done that step multiple times. It always works for ONE
reboot. After the computer is again restarted, the registry value
automatically changes back to 8e, and, subsequently, the Teredo
adapter gives a code 10.
4. I have also done this to no success.
I also cannot connect to a Homegroup with either computer. I can
start one on both, but neither shows that there is a Homegroup on
the network even though I can see both computers and peak into
their folders from the other computer. They are both on the same
Home network. They are both on the same Workgroup.
I have a Netgear Nighthawk R7000 802.11ac router and Ive also
checked through that for anything reguarding IPv6 nothing is
restricted. Ive restored everything to defaults. I tried setting
various options on and off Ive spent at least 6 hours trying to
figure out whats gone wrong and why that registry value keeps
auto-changing itself back to 8e from 0.
I cannot think of anything Ive done recently, since when I noticed
the device wasnt starting, that Ive changed from my normal
habits. I cant think of any new programs Ive tried out.

Everything I find through Google is from around 2011 to 2013,


and the instructions to fix it are the same as listed here, or to
simply disable the adapter, as apparently, its not needed.
Thanks for the response.
Reply

lakonst
Jun 25, 2015 @ 14:01:24

OK then. Lets find which process modifies the registry.


1. Open an elevated command prompt and run the
following command:
auditpol /set /subcategory:Registry /success:enable
2. Then Open Registry Editor and navigate to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
services\TCPIP6\Parameters
3. Select the DisabledComponents key.
4. From menu choose: Edit > Permissions
5. Choose Advanced.
7. Choose the Auditing tab
8. Click Add
9. Type Administrators on the box and click OK.
10. Click the Set Value checkbox at Successful column
and press OK.
11. Apply settings and press OK to Exit.
12. Now change the DisabledComponents value to 0 and
select OK.
13. Close Registry Editor and restart your computer.
After Restart:
1. Open Event Viewer > Security
2. Select Registry line(s) (Task Category) to find out
which process (Process Information) modifies the
DisabledComponents registry value.
Good luck!

5.

Link
Jul 04, 2015 @ 15:13:06

Lakonst,

Before seeing you last reply instructions, I tried all three steps once more and found that
after restarting the computer, the registry value was no longer auto changing itself, but
that also the Teredo adapter was not installed. I reinstalled the adapter AGAIN, and
restarted. The registry value mystically has stopped changing itself, and the adapter is
installed and working. After a week of restarts, it has not malfunctioned again. So,
thanks! No idea what fixed it, but alls well.
Cheers!
Reply

6.

Pa
Jul 16, 2015 @ 04:56:36

I just want to add my solution here in case anyone else has this problem. I fixed it
extremely easily by simply looking at the registry of a working win 7 laptop. Just delete
the registry key in the photos in step 1 named DisabledComponents. In my registry, the
EnableICSIPv6 registry key was absent altogether, so I created it by right clicking in the
white space and clicking DWORD. Then you rename it to EnableICSIPv6, enter 1 as the
value and click the Hexadecimal radio button. The exclamation on the Teredo Tunneling
device is gone and there appear to be no issues.
Reply

7.

Ayush
Jul 29, 2015 @ 14:23:24

after following your 2nd method that is cmd one. my teredo file is not showing in my
device manger after enabling hidden file. now what shall i do?
Reply

lakonst

Jul 30, 2015 @ 11:47:04

@Ayush: Re-install Teredo Adapter > How to Install Teredo Tunneling Adapter
Reply

8.

Anton
Aug 04, 2015 @ 19:24:44

This worked for me


1. Open the command prompt
2. Type in netsh winsock reset (without the quotes)
3. After resetting winsock, Restart your computer.
Worked on Windows 7 x64
Not taking any credit, found on this site:
http://seoroot.com/blog/networking/how-to-reset-winsock.html
Reply

9.

Travis
Aug 07, 2015 @ 13:54:40

Thank you!!
Reply

10.

Dave
Aug 10, 2015 @ 02:32:09

Per your detailed instructions, modified registry, rebooted, uninstalled adapter, rebooted,
checked hidden devices and windows reinstalled the adapter and it is working properly.
Thank you so much!
Reply

11.

anil
Aug 18, 2015 @ 17:13:30

Thanks a ton , simple instructions and problem solved


Reply

12.

Robert
Aug 24, 2015 @ 16:23:39

Many thanks, so far it seems to have worked.

Potrebbero piacerti anche