HomeDrivers DownloadArticlesDrivers Search
Driver Search: Enter the hardware model to search for the driver
Microsoft Network Adapter Teredo Tunneling Pseudo-Interface
 
 
 
 
 
(3 stars by 285 users)
 
Teredo Tunneling Pseudo-Interface driver installation information
The following is driver installation information, which is very useful to help you find or install drivers for Teredo Tunneling Pseudo-Interface.For example: Hardware ID information item, which contains the hardware manufacturer ID and hardware ID. These two ID values are unique and will not be duplicated with other hardware. According to these two ID values, the matching driver information can be accurately found. This method is more effective than any others, and 100% correct.There are many other information items that you can use to find the driver version information and the required driver files.

The name of the driver type in the system is: Net, and the drive type GUID is: {4d36e972-e325-11ce-bfc1-08002be10318}.

For Windows OS:

Hardware ID:
: *TEREDO
: *TUNMP
CLASS
Net
MFG
Microsoft
SERVICE
tunnel
HARDWAREID
*TEREDO
ENUMERATOR_NAME
SWD
ENUMERATOR_NAME
ROOT
COMPATIBLEIDS
SWD\GenericRaw, SWD\Generic
PHYSICAL_DEVICE_OBJECT_NAME
\Device\00000001
PHYSICAL_DEVICE_OBJECT_NAME
\Device\0000007e
PHYSICAL_DEVICE_OBJECT_NAME
\Device\00000002
PHYSICAL_DEVICE_OBJECT_NAME
\Device\00000003
PHYSICAL_DEVICE_OBJECT_NAME
\Device\00000005
PHYSICAL_DEVICE_OBJECT_NAME
\Device\00000006
FRIENDLYNAME
Teredo Tunneling Pseudo-Interface
FRIENDLYNAME
Microsoft Teredo Tunneling Adapter
CLASSGUID
{4D36E972-E325-11CE-BFC1-08002BE10318}
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0013
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0016
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0012
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0011
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0014
DRIVER
{4d36e972-e325-11ce-bfc1-08002be10318}\0020
Teredo Tunneling Pseudo-Interface Driver download
Teredo Tunneling Pseudo-Interface
Net
Haven't found the right driver yet? Are you facing difficulties in the driver search process?

1. The drivers you found aren't compatible.

2. You don't know how to search for drivers.

3. Your device isn't installed with drivers and appears as an "unknown device" in the system. You don't know how to find drivers for it.

This website offers a new method for finding drivers, a precise and fast way. Click here to use the new feature.
Installation Parameter
[Version]
Signature
"$Windows NT$"
Class
Net
ClassGUID
{4d36e972-e325-11ce-bfc1-08002be10318}
Provider
%Msft%
DriverVer
06/21/2006,6.1.7600.16385
[Manufacturer]
%Msft%
Microsoft,NTamd64
[Microsoft.NTamd64]
%ISATAP.DisplayName%
ISATAP.ndi, *ISATAP
%6to4mp.DisplayName%
6to4mp.ndi, *6to4mp
%TUNDIRECT.DisplayName%
TUNDIRECT.ndi, *TUNDIRECT
%TEREDO.DisplayName%
TEREDO.ndi, *TEREDO
%CPTUNNEL.DisplayName%
CPTUNNEL.ndi, *CPTUNNEL
%IPHTTPS.DisplayName%
IPHTTPS.ndi, *IPHTTPS
[TUNNEL.Service]
DisplayName
%TUNNEL.Service.DisplayName%
ServiceType
1 ;SERVICE_KERNEL_DRIVER
StartType
3 ;SERVICE_DEMAND_START
ErrorControl
1 ;NORMAL
ServiceBinary
%12%\tunnel.sys
LoadOrderGroup
NDIS
[ISATAP.ndi]
AddReg
ISATAP.ndi.params, ISATAP.ndi.reg
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
[ISATAP.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, "%ISATAP.HelpText%"
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel"
 
HKR, , Type , 0, "13"
[ISATAP.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
 
HKR, Ndi\Params\Type, ParamDesc, 0, %Type%
 
HKR, Ndi\Params\Type, Default, 0, ""
 
HKR, Ndi\Params\Type, Type, 0, "int"
[ISATAP.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, ISATAP.AddEventLog
[ISATAP.AddEventLog]
AddReg
ISATAP.AddEventLog.Reg
[ISATAP.AddEventLog.Reg]
 
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
 
HKR, , TypesSupported, 0x00010001, 7
[6to4mp.ndi]
AddReg
6to4mp.ndi.params, 6to4mp.ndi.reg
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
[6to4mp.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, "%6to4mp.HelpText%"
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel"
 
HKR, , Type , 0, "11"
[6to4mp.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
 
HKR, Ndi\Params\Type, ParamDesc, 0, %Type%
 
HKR, Ndi\Params\Type, Default, 0, ""
 
HKR, Ndi\Params\Type, Type, 0, "int"
[6to4mp.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, 6to4mp.AddEventLog
[6to4mp.AddEventLog]
AddReg
6to4mp.AddEventLog.Reg
[6to4mp.AddEventLog.Reg]
 
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
 
HKR, , TypesSupported, 0x00010001, 7
[TUNDIRECT.ndi]
AddReg
TUNDIRECT.ndi.params, TUNDIRECT.ndi.reg
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
[TUNDIRECT.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, "%TUNDIRECT.HelpText%"
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel"
 
HKR, , Type , 0, "2"
 
HKR, , AddressLength , 0, "4"
[TUNDIRECT.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
 
HKR, Ndi\Params\Type, ParamDesc, 0, %Type%
 
HKR, Ndi\Params\Type, Default, 0, ""
 
HKR, Ndi\Params\Type, Type, 0, "int"
[TUNDIRECT.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, TUNDIRECT.AddEventLog
[TUNDIRECT.AddEventLog]
AddReg
TUNDIRECT.AddEventLog.Reg
[TUNDIRECT.AddEventLog.Reg]
 
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
 
HKR, , TypesSupported, 0x00010001, 7
[TEREDO.ndi]
AddReg
TEREDO.ndi.reg, TEREDO.ndi.params
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
[TEREDO.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, %TEREDO.HelpText%
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel"
 
HKR, , Type, 0, "14"
 
HKR, , DeviceName, 0, "\Device\TeredoTun"
 
HKR, , SymbolicName, 0, "\GLOBAL??\TeredoTun"
[TEREDO.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
[TEREDO.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, TUNNEL.AddEventLog
[CPTUNNEL.ndi]
AddReg
CPTUNNEL.ndi.params, CPTUNNEL.ndi.reg
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
[CPTUNNEL.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, "%CPTUNNEL.HelpText%"
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel,ndis5_tunnel"
 
HKR, , Type, 0, "1"
 
HKR, , SubType, 0, "1"
[CPTUNNEL.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
[CPTUNNEL.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, CPTUNNEL.AddEventLog
[CPTUNNEL.AddEventLog]
AddReg
CPTUNNEL.AddEventLog.Reg
[CPTUNNEL.AddEventLog.Reg]
 
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
 
HKR, , TypesSupported, 0x00010001, 7
[IPHTTPS.ndi]
AddReg
IPHTTPS.ndi.reg, IPHTTPS.ndi.params
*IfType
131 ; IF_TYPE_TUNNEL
*MediaType
15 ; NdisMediumTunnel
*PhysicalMediaType
0 ; NdisPhysicalMediumUnspecified
Characteristics
0x9 ; NCF_VIRTUAL, NCF_HIDDEN
[IPHTTPS.ndi.reg]
 
HKR, Ndi, Service, 0, "tunnel"
 
HKR, Ndi, HelpText, 0, %IPHTTPS.HelpText%
 
HKR, Ndi\Interfaces, LowerRange, 0, "tunnel"
 
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5_ip6_tunnel"
 
HKR, , Type, 0, "15"
 
HKR, , DeviceName, 0, "\Device\IpHttpsDevice"
 
HKR, , SymbolicName, 0, "\GLOBAL??\IpHttpsDevice"
[IPHTTPS.ndi.params]
 
HKR, Ndi\Params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
 
HKR, Ndi\Params\NetworkAddress, Default, 0, ""
 
HKR, Ndi\Params\NetworkAddress, Type, 0, "text"
[IPHTTPS.ndi.Services]
AddService
tunnel, 2, TUNNEL.Service, TUNNEL.AddEventLog
[Strings]
Msft
"Microsoft"
NetworkAddress
"Network Address"
Type
"Type"
TUNNEL.Service.DisplayName
"Microsoft Tunnel Miniport Adapter Driver"
ISATAP.DisplayName
"Microsoft ISATAP Adapter"
ISATAP.HelpText
"Microsoft ISATAP Adapter Driver"
6to4mp.DisplayName
"Microsoft 6to4 Adapter"
6to4mp.HelpText
"Microsoft 6to4 Adapter Driver"
TUNDIRECT.DisplayName
"Microsoft Direct Point-to-point Adapater"
TUNDIRECT.HelpText
"Microsoft Direct Point-to-point Adapter Driver"
TEREDO.DisplayName
"Microsoft Teredo Tunneling Adapter"
TEREDO.HelpText
"Microsoft Teredo Tunneling Adapter"
CPTUNNEL.DisplayName
"Microsoft Connectivity Platform Adapter"
CPTUNNEL.HelpText
"Microsoft Connectivity Platform Adapter Driver"
IPHTTPS.DisplayName
"Microsoft IP-HTTPS Platform Adapter"
IPHTTPS.HelpText
"Microsoft IP-HTTPS Platform Adapter Driver"
Use the search function to find the driver you need

Many hardware names are usually named after the chip model, and each chip model has its own dedicated driver, so as long as you know the chip model used by the hardware, you can find the right driver. For example, if your graphics card is named: "AMD Radeon RX 580", while actually the core chip model used is: "Radeon RX 580", then enter "Radeon RX 580" or "RX 580" to find the driver.

If you have a laptop or an all-in-one PC, you can also use the product name to search, and then go to the download page which has all the drivers for this machine (including: graphics card, network card, sound card, etc.). For example, if your laptop product name is: "Dell A6-9220e Inspiron Flagship", then type "Dell A6-9220e" to find all the drivers for this laptop.

Search steps:

1. Enter a keyword in the input box and click the "Search" button

2. In the query results, find the driver file you need, and click the download button

Driver Finder:

• Can't find the required driver files?
• Don't know how to find driver files?
• Unable to download driver files due to unstable network?
You can try using this driver file finder. The method of use is very simple. The program will automatically list all the driver files available for your current system. You can install drivers for devices that do not have drivers installed, and you can also upgrade drivers to the latest driver version for devices that have already installed drivers. Click here to download the driver finder.

Leave a Reply

If you have any questions, please leave a message. We will seriously reply to every question.

Name * ( Required fields are marked * )

Email ( Your email address will not be published )

    ToolBar:
    ←Upload Images

    Uploading pictures, please wait...    

    To better address the issue, please provide a detailed description of the problem.
    If possible, it would be helpful to include some images for additional clarification.
    For example, include screenshots of the error messages that appeared or any relevant dialog boxes.

Comment

HTML Code, Read Only, Click here Edit Post.

 
Latest Posts
 
User Reply & Help
About | Contact | Privacy Policy | Statement
Copyright © 2024 runonpc.com All rights reserved.
Any other third-party products, brands or trademarks listed above are the sole property of their respective owner.
runonpc.com does not have any cooperation or affiliation relationship with all the companies mentioned in the site content.