The TunnelMTU registry entry does not work in Windows 7 and in Windows Server 2008 R2

Article translations Article translations
Article ID: 2266686 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You have a computer that is running Windows 7 or Windows Server 2008 R2. You follow the method that is described in the Microsoft Knowledge Base article 826159 to change the default maximum transmission unit (MTU) size for virtual private network (VPN) connections. However, the TunnelMTU registry entry that you configure does not work, and the MTU size is not changed.

Note For more information about how to change the default MTU size, click the following article number to view the article in the Microsoft Knowledge Base:
826159 How to change the default maximum transmission unit (MTU) size settings for PPP connections or for VPN connections

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.1.7600.20749118,78407-Jul-201003:40x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.1.7600.20749164,35207-Jul-201004:12x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.1.7600.20749365,05607-Jul-201003:29IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size1,863
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable

File nameX86_289190da5c55baeb1a8835eb04dedc18_31bf3856ad364e35_6.1.7600.20749_none_84d353ece3435f0f.manifest
File versionNot applicable
File size703
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable

File nameX86_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.1.7600.20749_none_f3c7ca39d197ea96.manifest
File versionNot applicable
File size2,888
Date (UTC)07-Jul-2010
Time (UTC)06:04
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_6bfb36627f32ae75dfd75fbded679454_31bf3856ad364e35_6.1.7600.20749_none_3687397119525b24.manifest
File versionNot applicable
File size707
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable

File nameAmd64_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.1.7600.20749_none_4fe665bd89f55bcc.manifest
File versionNot applicable
File size2,892
Date (UTC)07-Jul-2010
Time (UTC)06:56
PlatformNot applicable

File nameUpdate.mum
File versionNot applicable
File size1,875
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_87875626072ddaf229309d525e4a8dda_31bf3856ad364e35_6.1.7600.20749_none_d01d881e354d7e0e.manifest
File versionNot applicable
File size705
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable

File nameIa64_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.1.7600.20749_none_f3c96e2fd195f392.manifest
File versionNot applicable
File size2,890
Date (UTC)07-Jul-2010
Time (UTC)06:58
PlatformNot applicable

File nameUpdate.mum
File versionNot applicable
File size1,469
Date (UTC)07-Jul-2010
Time (UTC)14:43
PlatformNot applicable

Properties

Article ID: 2266686 - Last Review: August 12, 2010 - Revision: 1.0
APPLIES TO
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Starter
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2266686

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com