Windows Vista tcpip.sys Connection Limit Patch for Event ID 4226

HomeΒ»Operating SystemsΒ»WindowsΒ»Windows Vista tcpip.sys Connection Limit Patch for Event ID 4226

Apparently in Windows Vista, Microsoft still enforce and hard-limit (hard coded in tcpip.sys) the maximum simultaneous half-open (incomplete) outbound TCP connection attempts per second that the system can make, as in Windows XP SP2, in order to protect the system from being used by malicious programs, such as viruses and worms, to spread to uninfected computers, or to launch distributed denial of service attack (DDoS). When the limit is hit, in Event Viewer, there will be such an entry:

EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts

Unlike Windows XP SP2 which has 10 maximum incomplete concurrent connection attempts limit per second, Windows Vista default limit is based on which edition of Vista users are using. For example, Home Basic has maximum limit of 2, and Vista Ultimate is 25 per second. Normal Windows Vista users should not face any problem or slow network connection with the half-open connections limit. However, heavy P2P (peer-to-peer) applications users such as uTorrent, BitTorrent, BitComet, Azureus, ABC, eMule (eDonkey network), etc, or P2PTV such as TVants, PPLive, PPStream, Sopcast, etc may face some error or slow download and upload speed due to this limit.

Due to enhanced security, to fix or crack the TCP concurrent connection limit in Vista is not as easy as in Windows XP. To remove maximum concurrent half-open connection limits in Windows Vista, apply the patched tcpip.sys with the following steps:

  1. Download patched tcpip.sys: Vista TCP/IP and UAC Auto Patcher (patched tcpip.sys is contained inside the archive).
  2. Open command prompt, and run the following 2 commands:
    takeown /f c:\windows\system32\drivers\tcpip.sys
    cacls c:\windows\system32\drivers\tcpip.sys /G "username":F

    Replace username with the actual user name that used to log on to Windows Vista currently.

    The second command can also replace with the improved icacls:

    icacls c:\Windows\System32\drivers\tcpip.sys /grant "username":f
  3. Disable the TCP/IP Auto-Tuning feature by running the following command in command prompt:
    netsh int tcp set global autotuninglevel=disable
  4. For 64-bit Windows Vista (x64), the integrity checks need to be disabled as it need all drivers to be signed. So run the following command in DOS prompt:
    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

    Note: Above command no longer supported, and users require to press F8 on system startup to bypass driver signing integrity check.

  5. Replace the tcpip.sys in C:\windows\system32\drivers folder with the patched tcpip.sys downloaded from step 1 (remember the use the correct x64 or x86 versionοΌ‰. Normally, this procedure can be done by simply login to Windows Vista with administrator account. However, if the process failed, reboot the computer and then press F8 to boot up in Safe Mode, and then copy and paste overwrite the tcpip.sys.
  6. Next, the maximum number of TCP half complete connection limits need to be set in registry. Open registry editor (regedit), and navigate to the following registry key:

    HKEY_LOCALL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  7. Right click on the right pane, select “New”, then select “DWORD value”. Enter the new value name as TcpNumConnections.
  8. Double click on TcpNumConnections registry value, and modify the value data to the desired maximum TCP/IP connection limit that you want to allow, in decimal value. For example, enter 500 as the value data for TcpNumConnections. You can use any limit that you prefer.

    Alternatively, download this registry registration file (no longer available) that when executed, will set the TCP simultaneous connection limit to 16777214 (you can always modify the value in the file or in the registry after applied).

  9. Restart computer.

Update 5 (Latest): Since Windows Vista and Windows Server 2008 SP2, there is no more restriction (now unlimited) concurrent half open TCP/IP connection limit.

Update 4: Windows Vista Event ID 4226 Auto Patcher

Windows Vista Event ID 4226 Auto Patcher has been renamed as Vista tcpip.sys and UAC Auto Patcher, which now has more than 6 versions of auto patcher download links for different versions of tcpip.sys with the release of various hotfixes and SP1. Visit the page for details.

Update 3: Half-Open Limit Fix (Automated tcpip.sys Patch using Test Self-Signed Certificate)

Update 2: Driver Version: CrackTcpip.sys for Vista SP1 v.668 – a non-patching method to bypass TCP connection limit.

Update 1: Also available is TCP/IP auto patcher for 64-bit (x64) Windows Vista SP1.

Gui Version: VistaTcpPath TCP Auto Patcher which works for Vista RTM (non-SP1) version of tcpip.sys.

Old Version:

Version 1.0
Version 1.2
Version 1.3
Version 1.4
Version 1.5

(resources no longer available)

With thanks to YaronMaor for batch script.

The TCP connection limit which trigger Event ID 4226 has now increased to 500 (or any other value you set), and will likely fix the error for re-occurring again.

By | 2016-12-23T19:20:45+00:00 December 23rd, 2016|Categories: Windows|Tags: |342 Comments

About the Author:

LK is a technology writer for Tech Journey with background of system and network administrator. He has be documenting his experiences in digital and technology world for over 15 years.Connect with LK through Tech Journey on Facebook, Twitter or Google+.
  • Justin

    I keep getting a message in Vista saying that I need to get permission to replace that file. I have tried everything I could think of. I am listed as an administrator and I have tried Safe Mode. How can I unlock the ability to change permissions in Vista so I can do this? I think it is the reason I have been having trouble with my Azuarus. Thanks.

  • admin

    Justin, have you try open command prompt in elevated mode?

  • Hi,

    Many thanks to this great guide.

    you can create a small batch file to have an auto-patch installation. just create a text file using notepad, called InstallPatch.bat

    and paste the following text:

    REM ————————————–

    REM this patch will remove Vista's tcpip concurrent connection limit.

    REM this limit produces the 4226 event in the System event viewer.

    takeown /f c:WindowsSystem32drivers cpip.sys

    echo *** Enter Y (yes) to the following question… ***

    echo.

    cacls c:WindowsSystem32drivers cpip.sys /g "%username%":f

    netsh int tcp set global autotuninglevel=disable

    copy tcpip.sys C:windowssystem32drivers /y

    reg import Vista_TCPIP_limit_16777214.reg

    echo.

    echo *** Please RESTART your computer!! ***

    pause

    REM ————————————–

    Note! the downloaded files (sys+reg) should be in the same folder as the batch file- uncompressed!.

    Cheers,

    YaronM

  • Pingback: Optimize Vista for BitTorrent, eMule, P2PTV | TorrentFreak()

  • Ernst

    Any chance someone could mirror the files? It's not easy wading through the ads & popups of depositfiles.com

    Great article, I've been waiting for this since Vista x64 came out

  • Hi,

    You can also download a copy of the patched driver including the Install batch file from my site: http://www.yaronmaor.net/repair.htm

    Cheers,

    YaronM

  • TheSleeper

    YaronMaor, thanks for your install.bat file !!

    this is very useful !!

    I will forward this to my freinds and colleagues who are using vista

  • I've updated the InstallPatch batch file to easily support the two 32/64 versions.

    I recommend you to download this package from:
    http://www.yaronmaor.net/repair.htm
    it appears as #2 "EventID4226Fix for Vista"

    Cheers,

    YaronM

  • Chris

    How do I revert back to default because my internet keeps crashing and I want to revert back to default but I don't know how.Please help

  • admin

    If you keep the original tcpip.sys simply replace it back.

  • Chris

    Haha, which means I have to get the tcpip.sys file from another laptop because I didn;t keep the original one.But thanks for the help, and do I have to delete the registry enty and enable back auto tuning?

  • admin

    Hi sorry about that. Coz you shouldn't face this problem I believe.

  • admin

    Hi Chris, you can try reinstalling your internet explorer. Feedback from Justin Weberg.

  • Chris

    I have installed back the original tcpip.sys file and I shall inform back on whether it works or not. just in case, I have enabled again auto tuning and deleted the registry entry. Thanks for the feedback though. Much appreciated.

  • Jug

    "may face some error or slow download and upload speed due to this limit"

    This is largely a well spread myth. While the error may occur once every hour or so due to an unusual flood of new connections, it'll just queue the connections, so nothing is dropped, and no bandwidth is lost. There is no hard limit to connections an unpatched system enforce; you'll get exactly as many as you should have before. It's just that new connections might be made slightly slower when they happen in rare bursts.

    So, what I'm saying is that the net effect of an unpatched system may be that you're e.g. up and running in full speed in something like 30 seconds instead of 15 on a patched one. But the end result is identical.

    This can easily be checked on an "unpatched" system too. I have no trouble getting up to, and maintaining, up/downloads at over 500 Kbps over here, and how this limit kicks in is also unrelated to your connection speed, and only the rate of new connections being made.

    Many modern P2P clients also feature a built-in setting nowadays for maximum connections.

  • freedomfighter

    Does this work with XP x64 SP2? I haven't found a working patch for this problem yet, but I don't want to get major problems experimenting and have to reformat (like I've heard others having to do)

  • GiGi

    @Jug "This is largely a well spread myth."

    Obviously you are talking about something you read somewhere on the internet because this limit DOES slow down p2p applications and although some applications have settings for it the program will always perform better without the limit and with normal settings. I agree that eventually all connections will come true but with shareaza for instance while downloading 3 torrents and a few edonkey files the whole download process is coming to a hold without such a patch.

  • levy

    10xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  • Emanuele

    Great trick!!!! I've used it also on XP. But I always haved a doubt. How many half-connections are recommended to open? I've just open 100 half-connections. Thanks.

  • Wex

    It works for a short while, then I can't open any websites of download anything, or just at a very low speed, just like described in the "Disable TCP Auto-Tuning" Article. What's wrong? I have tunned it off.

  • Web

    Hi,

    Thanks for the patch, but it needs one little change:

    my vista is installed on my F: Partition, at first it didn't work for me until i noticed this mistake.

    you should replace "c:windows" with "%Systemroot%" in the batch files ;P.

  • Hi,

    I've updated the vista patch to include:

    a) Uninstaller (undo changes to originals)

    b) update destination path to %systemroot%

    Download it from http://www.yaronmaor.net under the Repair section.

    Cheers,

    YaronM

  • admin

    Thanks web, will update it soon.

  • Bryan

    Mine tells me the system file is not found when I was trying to do a Bit-32 patch.

  • admin

    Hi Bryan, do you have more error details? Like screenshot?

  • Hi,

    Sorry, I've had a path mistake..

    get the updated version from:
    http://www.yaronmaor.net under the Repair section.

    Cheers,

    YaronM

  • Jules Winnfield

    Autotuning command should be "netsh int tcp set global autotuninglevel=normal" in UndoPatch.bat, not "netsh int tcp set global autotuninglevel=enable".

  • admin

    Thanks to YaronMaor, Bryan and Jules, has corrected the errors.

  • Bryan

    Alright thank you. Will try again πŸ™‚

  • Wex

    I am facing an wired problem:

    After I applied the patch, it will first work fine after reboot, then in a while any out connection can't establish, for example, browser won't open new sites, p2p connected peers and clients drops to 1 or 0. But some sort of connection remains usable, for example ICQ, MSN, what's wrong with this? Can anybody help? Thank you.

    PS: I want to know what changes have been made to the TCPIP.SYS what's the new HARD-CODED connection limits?

  • Roby

    Hi.. I'm trying to install this patch but it can't copy the tcpip.sys to system32 even if I execute it as the administrator.. I tried also the f8 way but it has the same problem even in safe mode.. What can I do?

  • Ero

    Hi I ran the patch as administrator and got this half success, half error:

    Confirm to apply? (Press Ctrl-C and answer Y to terminate)

    Press any key to continue . . .

    SUCCESS: The file (or folder): "C:WindowsSystem32drivers cpip.sys" now owned

    by user "X2Ero".

    Are you sure (Y/N)?Ok.

    1 file(s) copied.

    Original tcpip.sys driver has been renamed to "tcpip.original" in its original folder.

    The system cannot find the file specified.

    ERROR: Error opening the file. There may be a disk or file system error.

    *** Patch installation is complete. Please RESTART computer!!

    Press any key to continue . . .

    Is the patch applied or did it error like it said in the first part?

  • Roby

    I had the same error Ero has..

  • Jules Winnfield

    It says above that one of the steps involved in applying the TCP patch is to disable the autotuning service.

    Is it necessary to do this and will the patch still work with it enabled?

  • Wex

    It might because of the WinPcap, that caused my situation.

  • Wex

    And the patched file won't work with ICS, very unstable.

  • Lenmaer

    The manual one works great, but I cannot say that for the auto patcher.

  • rafael

    i couldnt copy the file in the windows folder… It says i dont have permission, even in safe mode.

    How do i copy the file??

  • AnonymousOne

    Error message on Longhorn (vista server 64) build 6001

    Auto Patcher batch script by http://www.yaronmaor.net

    for 64-bit version of Windows Vista

    Confirm to apply? (Press Ctrl-C and answer Y to terminate)

    Press any key to continue . . .

    ERROR: The system cannot find the path specified.

    Are you sure (Y/N)?Ok.

    'bcdedit.exe' is not recognized as an internal or external command,

    operable program or batch file.

    The system cannot find the path specified.

    Original tcpip.sys driver has been renamed to "tcpip.original" in its original f

    older.

    The system cannot find the path specified.

    0 file(s) copied.

    The operation completed successfully.

    *** Patch installation is complete. Please RESTART your computer!! ***

    Press any key to continue . . .

  • Hello All,

    Sorry for the delay.

    I've released an updated v1.4 of the Patcher.

    it resolves the permission issue some of you mentioned in trying to copy the tcpip.sys file.

    I haven't yet tested it on a 64bit version but it should act the same. I'm also not sure it is supported on a Longhorn Server Beta due to changes in folder locations and command-line syntax. if anyone of you have any feedback, feel free to contact me: info at yaronmaor.net

    Download v1.4 from: http://www.yaronmaor.net

    Cheers,

    YaronM

  • zaknaf

    Hi,

    The new version (1.4) works perfectly on my 64bit Vista (I was getting the permission denied error before)

    Thanks a lot YaronMaor

  • Sivashanker

    Hi everone. I seem to have a problem with the autopatcher. P2PNETSH.DLL cannot be found. How do I fix this error. Thanks.

  • Rick

    I tried v1.5 on Vista, and the batch got as far as the reg import command where it failed to go any further, insisting that either there was a problem with the disk or the filename was bad (it was correct).

    Is there a permissions issue with "reg import" for an admin-level user with UAC? Perhaps the batch needs to be elevated with "Run as administrator"

    Note: I merged the .REG file manually without incident.

  • Rick

    I set mine to a more reasonable 5000, but uTorrent still triggers several 4226's — even though uTorrent is only set for 80 half-open connections. Something's not quite right about this, since 5000 is WAY over what I'd use with this single program or even a fleet of them. I never saw this happen with the equivalent patch in XP.

  • Hi All,

    I've uploaded a new v1.6 which now includes a fix to disable the UAC prompt for those of you still using the UAC protecion.

    it also includes a tool to completly disable the UAC protection.

    download from: <a href="http://www.yaronmaor.net” target=”_blank”>www.yaronmaor.net

    Cheers,

    YaronM

  • El Denno

    Doesn't seem to be working for me I get the following error;

    Windows Vista Concurrent TCP/IP Connection Attempt Limit Auto Patcher

    Event ID 4226 Fix

    Version 1.6

    (c) My Digital Life (www.mydigitallife.info)
    Auto Patcher batch script by http://www.yaronmaor.net

    for 32-bit version of Windows Vista

    Confirm to apply? (Press Ctrl-C and answer Y to terminate)

    Press any key to continue . . .

    ERROR: Not all data was successfully written to the registry.

    Some keys are open by the system or other processes.

    SUCCESS: The file (or folder): "C:WindowsSystem32drivers cpip.sys" now owned

    by user "JACKSJack".

    processed file: C:WindowsSystem32drivers cpip.sys

    Successfully processed 1 files; Failed processing 0 files

    Set global command failed on IPv4 The requested operation requires elevation.

    Access is denied.

    0 file(s) copied.

    Original tcpip.sys driver has been renamed to "tcpip.original" in its original f

    older.

    1 file(s) copied.

    ERROR: Not all data was successfully written to the registry.

    Some keys are open by the system or other processes.

    *** Patch installation is complete. Please RESTART computer!!

    Press any key to continue . . .

    Please help me. My email is el_denno@hotmail.com

    Thanks

  • admin

    Did you run as administrator?

  • nocrash

    @El Denno

    use the script within an "elevated command prompt", simply press the Win key; type cmd; press Ctrl+Shift+Enter; and then hit Alt+C to confirm

    (http://blogs.msdn.com/tims/archive/2006/11/02/windows-vista-secret-10-open-an-elevated-command-prompt-in-six-keystrokes.aspx)

    cheers

  • El Denno

    Thanks for the help. I ran it with an elevated cmd and this is what I got;

    Windows Vista Concurrent TCP/IP Connection Attempt Limit Auto Patcher

    Event ID 4226 Fix

    Version 1.6

    (c) My Digital Life (www.mydigitallife.info)
    Auto Patcher batch script by http://www.yaronmaor.net

    for 32-bit version of Windows Vista

    Confirm to apply? (Press Ctrl-C and answer Y to terminate)

    Press any key to continue . . .

    ERROR: Error opening the file. There may be a disk or file system error.

    SUCCESS: The file (or folder): "C:WindowsSystem32drivers cpip.sys" now owned

    by user "JACKSJack".

    processed file: C:WindowsSystem32drivers cpip.sys

    Successfully processed 1 files; Failed processing 0 files

    Ok.

    1 file(s) copied.

    Original tcpip.sys driver has been renamed to "tcpip.original" in its original f

    older.

    The system cannot find the file specified.

    ERROR: Error opening the file. There may be a disk or file system error.

    *** Patch installation is complete. Please RESTART computer!!

    Press any key to continue . . .

    I don't understand why I'm getting this error.

  • admin

    Have you try version 1.5 instead? If still fail, simply use manual method specify above.

  • May

    Hi all,

    May i know what is the default value of 'concurrent connection attempts limit per second' for Window Vista Business version.

    As i knew, there are 2 for Window Vista Home edition and 25 for Ultimate version.

    Thanks πŸ™‚

  • Markus (OM)

    Hi!

    Is this patch really working? I've been messing and testing it for a week now; and I'm still experiencing connection limit, but just without error in Event Viewer!

    πŸ™

    (Vista Ultimate 32bit user)

  • Rick

    How do you know you're experiencing the connection limit if you're not getting errors in Event Viewer?

    uTorrent still gives me 4226's in EV even though I can't be anywhere near hitting the limit (and besides, uTorrent is configured to use less than 100). Never happened in XP with its corresponding patch. So this patch still needs work.

  • Markus (OM)

    Hi Rick!

    Without patch:

    After an 4226 error uTorrent would continue to download it's current torrents!

    Patched:

    If I open more than few pages (in Maxthon of Firefox) and surf a "little" while uTorrent (or etc.) is downloading; I get same network errors (with no error in Event Viewer), but uTorrent still continues to download it's current torrents!

  • X_Splinter

    Its doesnt work… danm

    Somebody help me… i have Vista Home Basic and can have more than 20 conections in torrents… like 15sedders and 5 downloaders

    I pacth with version 1.5 didint work… i tryed version 1.6 didint work… can someone help me?????

  • john

    yeah thanks a lot! Now my windows xp's internet connection stopped. windows cannot start the windows firewall/internet connection sharing. Yeah! aint that great? i can't go online now thx alot!

    …………/´¯/)

    …………/….// …….^^^^^^^^^^^^^^^^^^^

    ………../….// ……/……__………..__…….

    …../´¯/…./´¯…..(-….(.0.)…….(.0.)…..-)

    .././…/…./…./.|_…¡………../_…………….

    (.(….(….(…./.)..)…………____………./

    ……………../../ …………………………

    ………………./……..__________/

    ………………( ……………………..

    ………………. ……………………..ο»Ώ

  • X_Splinter

    This is for windows vista and NOT for xp.

    Use System Mechanic or Windows Restore Points to put it back to normal

  • eurosete

    Dear john if you are an idiot, it is normal that do not work! The tile is:Windows Vista tcpip.sys Connection Limit Patch for Event ID 4226.

    Windows Vista, you understand?

  • dark knight

    MS ha updated the tcpip.sys file with one of windows update latest patches.

    We need another modified tcpip.sys for build 6.0.6000.20582 .

    Where we can find it?

  • dark knight

    MS has updated the tcpip.sys file with one of windows update latest patches.

    We need another modified tcpip.sys for build 6.0.6000.20582 .

    Where we can find it?

  • Gordon

    it's actually version 6.0.6000.20583 of tcpip.sys

    well it is on my pc anyway

    explains why the patch does not work

    stupid microsoft why limit it anyway didn't do it on pre sp2 xp and not much harm was done

  • Rick

    It's interesting that you guys show differing version numbers (did one of you install a pre-release hotfix?). I wonder which update did it? I'm still on 6.0.6000.16386, and the only update I haven't installed is the infamous troublemaker Q935807 (see link), which few people seem to be able to actually get installed.

    http://www.microsoft.com/technet/security/Bulletin/MS07-038.mspx

    While the files that it installs (as shown in "File Information") include all sorts of TCP/IP-related files, it doesn't show TCPIP.SYS itself as being one of them.

    So if not this update, which one? Or maybe it's an omission?

    I sure miss lvllord's version of this patch for XP, which 1) Worked completely (with this Vista patch I still get error messages, though a small number) and 2) It was well updated.

  • adams

    MS has updated the tcpip.sys file with one of windows update latest patches.

    We need another modified tcpip.sys for build 6.0.6000.20582 .

    Where we can find it?

  • adams

    MS has updated the tcpip.sys file with one of windows update latest patches.

    We need another modified tcpip.sys for build 6.0.6000.20583 .

    Where we can find it?

  • bruce

    Where can we find an updated patch for the new build of tcpip.sys? The old patch doesn't work anymore.

  • brian

    I did everything through step 5 and then my internet didn't work anymore

  • help !

    tcpip.sys 6.0.6000.20583

    any crack for it ?

    please help

  • Lole

    Quéquette πŸ˜€

  • EricLee

    If apply KB932596 patch on Vista64 system then tcpip stack will not be run.

    would you reslove it ?

    thanks

  • Dickson Balls

    this is a half baked backyard hack that does more harm than good.it has been only half thought through by someone who knows stuff all with what they are actually doing. They may have lucked out once or twice with this patch on a Vista PC but there are safer alternatives around than this lame attempt at a fix. do yourself a favour and google for the real fix.

  • Pingback: KB929547 - Aussetzer in Anwendungen nach Installation eines WFP-Treibers - drvista.de()

  • Pingback: KB929547 - Aussetzer in Anwendungen nach Installation eines WFP-Treibers - drvista.de()

  • Pingback: Windows Vista tcp.sys Patch()

  • hh

    I uninstalled KB932596 on my Vista-x64 system, but I still can't get it to work, always fails on dial-in just as with that patch.

    Any ideas??

  • Howdy!

    The new tcpip.sys is version 6.0.6000.20597!

    We need another modified tcpip.sys for build 6.0.6000.20597 .

    Where we can find it?

    Greets

  • a new version 1.7 was released to support Windows Vista SP1 Beta.

    Find it here: http://www.yaronmaor.net/downloads/VistaTcpipUacPatch1.7beta.rar

    Cheers,

    YaronM

  • aww shit….

    yeah so… now MSDTC starts up with 0 in allow remote administration…. i removed the TCPIP patch…. what did i forget???

    i think it has something to do with this:

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

  • Rick

    To clarify, there is no "new" version of TCPIP.SYS if you're running non-beta Vista 32-bit. It's only an issue on 64-bit as well as the SP1 beta. For everyone else, unless you've installed some unofficial hotfix, you should still be using v6.0.6000.16386.

    Here's an alternative tool for anyone actually in need:
    http://www.mydigitallife.info/2007/09/01/vistatcppatch-windows-vista-tcp-half-open-limit-auto-patcher-gui-version/

  • Manoj

    mine says its v6.0.6000.20645 not v6.0.6000.16386

    but i only installed official patches.

  • Rick

    By "official" I meant what's offered by Windows Update. There is at least one patch, this one:
    http://support.microsoft.com/kb/940646

    Which will update tcpip.sys to the version you mentioned, but it's a very specific fix intended for only the few who need it. MS has not broadly offered a newer tcpip.sys to Vista 32-bit (non-SP1).

  • Thresholder

    Hi,

    I have been trying to patch tcp on windows vista home premium 32 using both the autopatcher and the elevated cmd prompt.

    When I use the elevated cmd prompt I get the message:" VistaTcpPatch is not recognised as an internal nor external comand a program or batch file".

    If I use the autopatcher when I reboot I get a blue screen with a memory crash dump and need to remove the patch in order to get the system back up.

    Has this worked for somebody?

    Am I doing anything wrong?

    Thanks.

  • Rick

    >When I use the elevated cmd prompt

    >I get the message:” VistaTcpPatch

    >is not recognised as an internal

    >nor external comand a program or batch file”.

    Be sure to extract the complete contents of the archive into whatever temp directory you're using, and be sure to move into that directory once you've dropped to the command line. You couldn't have been in the directory when trying to execute the commands.

  • GiGi.

    The patch posted earlier that is supposed to work with vista sp1 beta does not function properly. I still get warning that the imposed connection limit has been reached. Can someone look at a solution to this?

    Cheers

  • Rick

    I suspect there's not much inclination to bother with SP1 beta at this point, since it's a moving target. Several more builds will come out.

    What we really need is an intelligent patcher, not just a canned one, which can look through the DLL and dynamically make the changes as appropriate. One existed for XP for years.

  • Hi All,

    The patch for the Vista SP1 Beta is unstable and might not function correctly on all the Beta builds. as soon as the final SP1 will be out I will try to publish ASAP an updated version of the patch.

    Meanwhile, versions v1.5/1.6 works fine. for those of you that installed the hotfix KB940646 and got a different version of the tcpip.sys driver- the patch will not work. Please note that this patch is not essential for most of you and is not delivered through Windows Update.

    YaronM.

  • Thresholder

    Rick

    November 1st, 2007 09:49

    95

    >When I use the elevated cmd prompt

    >I get the message:” VistaTcpPatch

    >is not recognised as an internal

    >nor external comand a program or batch file”.

    Be sure to extract the complete contents of the archive into whatever temp directory you’re using, and be sure to move into that directory once you’ve dropped to the command line. You couldn’t have been in the directory when trying to execute the commands.

    Hi Rick and thanks for the help.

    I do not understand what archive I need to extract since the only thing I get from the download is VistaTcpPatch.exe.

    What else should I get?

    Anyway I copied the VistaTcpPatch.exe file in the System32 directory and executed the cmd prompt.

    I got the following message:Tcpip.sys file version unsupported.

    Did I do everything right this time?

    If so is there anything else I can try?

    Thank you.

  • Rick

    Thresholder, the .exe file is the autopatcher (VistaTcpPatch), which you said blue screened your system. You also said it wouldn't run (unrecognized command), which is contradictory. Regardless, since you're commenting on this page you should be referring only to what's available here, and that's an archive of several files.

    But it appears from your second post that you're running the version of TCPIP.SYS from either SP1 or KB940646, so you're going to have forget about patching at all.

  • Thresholder

    Hello Rick,

    I am sorry if I posted on the wrong page.

    I am commenting now on what is available on this page.

    I checked my tcpip.sys and it is build 6.0.6000.20582 although I do not have KB940646 installed within my Windows Updates.

    Don't know how but in my download folder I got a copy of tcpip.sys build v6.0.6000.16386 that I maybe downloaded from someplace or maybe is a backup of my old tcpip.sys but I am unsure.

    Do you think it would be advisable to replace tcpip.sys 6.0.6000.20582 with v6.0.6000.16386 in order for the patch to work?

    I also saw in the comments a link to version 1.7 of the patch.

    Does that works out for versions 6.0.6000.20582 of tcpip.sys in case you discourage the substitution with the older version of the file?

    Did you test it?

    One last question:in your previous post you tell me to "be sure to move into that directory once you’ve dropped to the command line".

    I do not understand what this mean so would you mind explaining it please?

    I have extracted the archive file on the desktop (VISTA).

    Thank you

  • Nuno Lopes

    Hi

    when i install the tcpip patch my computer stops detecting any network available, norton 360 says that are an internal problem. When i put the original tcpip.sys i star to have internet again.

  • Nuno Lopes

    Hi

    when i install the tcpip patch my computer stops detecting any network available, norton 360 says that are an internal problem. When i put the original tcpip.sys i star to have internet again. I´m using Windows vista 64bits ultimate

  • where is the reference that the limit is different in home basic vs ultimate?? Since it seems that the tcpip.sys file is the same in all flavors of vista?

    How/Why would the limit be different? What was the point of stating such a thing if not true? A limit is a limit is a limit – if its 2 or 10 or 25 what does it matter if what your looking to do is remove the limit?

    To be honest the whole thing is pointless — there really is not valid reason to work within the limits.. But I am looking for reference to the 2 in home an 25 in ultimate statement. Can someone please provide reference to this statement??

  • uac

    All editions have 10 half-open connections TCP/IP limit. The exceding connections attempts are not lost, but they're put in a queue.

  • Rick

    Funny you mention that, since there's a debate ongoing about it here, but it does appear that it is 10 for any edition:

    h**p://www.neowin.net/forum/index.php?showtopic=599056

  • ghost

    the auto patcher dose not work with the 64bit version of vista

  • ldog

    ok so my internet stopped working b/c of this patch how do i unpatch tcpip.sys??? does n e one know were it is on my computer and how to get the old one back?

  • ldog

    ok i got it to work, i also wanted to know i get an error on startup almost everytime MSDTC concosle do u guys know how to fix that dumb message?

  • admin

    Idog, do you have screenshot? What is the error message?

  • ldog

    A critical error occurred in an MS DTC component therefore the process is terminating. The category field identifies the component that encountered the error. Please contact Microsoft Product Support. Error Specifics: hr = 0x80070002, d:vistartmcomcomplusdtcdtcmsdtcsrccservice.cpp:461, CmdLine: C:WindowsSystem32msdtc.exe, Pid: 3748

    i dont need msdtc i dont think i think its for a server how do i disable it????

  • ROK

    If i replace my tcpip.sys with sys file from this site or from those patches my computer crash after start up and I got blue screen of death. I use vista business edition and I think reason why those sys files don't work is this windows vista KB93897 update.

    Chck this site: link removed there is also Vista TCP/IP and UAC AutoPatch 6.0

    This limit thing is so frustrating.

  • admin

    Hi ROK, the site stole the patched tcpip.sys from here. So link to it not allowed. Anyway, it's basically the same thing, and won't work on newer version of tcpip.sys installed by SP1.

  • PrEzi

    Has anyone managed to grab a patched tcpip.sys made for Vista SP1 RC0 ? tcpip.sys build is :

    6.0.6001.17042.

    I have tryed the Windows Vista Event ID 4226 Auto Patcher build 1.7beta for SP1 but it's actually an older build of tcpip.sys and my Vista hangs πŸ™

  • Anyone got a new TCPIP patch for Windows Vista Sp1 Beta??…I installed the beta from Windows Update, and it fixed many things on my system, and I want to use it. But had to uninstall it due to the damn TCPIP limit which the government forced Microsoft to implement. Anyone have a new patch so I can reinstall the service pack?

  • ROK

    Hi admin.

    Site stoled it from here??? Sorry I didn't know that.

    Will there be updated version to this patch or tcpip.sys soon?

  • admin

    Unlikely.

  • **Admin: "Unlikely"**

    So does this mean that no further TCPIP hacks will be available? Has MS finally locked it down? Are we all sol? I guess SP3 of XP does the same thing?

    Finally gonna have to switch back over to Linux I guess. To bad the Government has MS by the balls. Oh well. πŸ™

  • vano_spb

    For people who have installed KB940646 and have version of tcpip.sys 20645 i have made patch, tested on my PC

    link removed

    if u have previose version 20XXX install kb940646 and use this path.

  • Data

    I have the same problem as Nuno Lopes in Vista x64, when i install the patch my computer stops detecting any network available. I tried patch 1.5, as my original tcpip32.sys was version 16386. Does anyone have an alternative version for x64? [patch 1.5 works fine on another computer running Vista x32…]

    Thanks in advance.

  • Data

    Here ist the solution for Vista x64:

    I had to uninstall the following Windows updates, as they automatically re-enabled driver signing in Vista x64:

    -KB943078

    -KB932596

    -KB938979

    -KB941649

    I uninstalled them in Windows safe mode, just to make sure.

    After that I could apply patch 1.5 or 1.6.

    I had to manually start the command

    "bcdedit.exe /set loadoptions DDISABLE_INTEGRITY_CHECKS"

    after running the InstallPatch64.bat, as it showed that bcdedit wasn't found for unknown reasons. After this procedure I restarted and everything worked!

    PS: Be careful, any future Windows Update or Service Pack may (sadly) re-enable this driver signing process. So if your network card stops working and shows up with a red x in the tray one day it will probably be due to an update that was just installed.

    Hope this helps anyone, cost me half a day to find that out.

  • RobG

    vano_spb,

    Could you make the patch TCP file to 64 bit systems ???

  • Rick

    Just a heads up, MS today released the first mainstream update to TCPIP.SYS since 32-bit RTM. It's part of Security Bulletin MS08-001 and is v6.0.6000.20689.

    By "first" I'm not counting betas and not counting a couple optional updates made available only via obscure KB articles. This one is being pushed out to everyone via Windows Update, though technically speaking it is optional if you don't use automatic updates.

    So now the search is on for the patched version (just like was created for the RTM version), though why an intelligent updater like the original one for XP isn't available is still a mystery.

  • Rick

    Clarification: After actually installing MS08-001, I got v6.0.6000.16567 of TCPIP.SYS, not what I mentioned earlier. Both versions are mentioned in the technote for 32-bit, so apparently some 32-bit flavors get one and some the other. First I've heard of such a thing, but I can't think of any other explanation.

  • admin

    After installing KB941644, I too get tcpip.sys version 6.0.6000.16567. 6.0.6000.20689 probably is for other files?

  • Rick

    There appear to be two sets of files with this update listed here in the Security Update Deployment, Windows Vista (all editions), File Information section. Since we both got 6.0.6000.16567 (I tested on the Enterprise edition) it's pretty safe to assume most will get that, but the other version is mentioned for tcpip.sys as well, so eventually someone's going to turn up with it.

    http://www.microsoft.com/technet/security/bulletin/ms08-001.mspx

  • Rick

    OK, so here's my line of thinking on patching 6.0.6000.16567. Tell me if I'm crazy, please.

    Comparing the RTM version with your patch in UltraEdit, the only differences I see are these:

    RTM: 140H-141H: 67 0F

    Patch: 140H-141H: 91 26

    RTM: 3F47dH-3F482H: 0F 87 8b 00 00 00

    Patch: 3F47dH-3F482H: 90 90 90 90 90 90

    When looking in 6.0.6000.16567 for something comparable, I found:

    -The first pattern is still 140H-141H, but the new values there are: AB 86. The byte following, at 142H, is now 0C instead of 0D.

    -3f479H-3f47fH is the new location for the second pattern, and all the numbers around it also match the original so it's definitely the right location.

    So the second change seems easy. The first one is more ambiguous, since I'm not sure if the third byte should also be changed.

  • Rick

    Modified 6.0.6000.16567 (32-bit), in case anyone wants to try it out. How I did it is explained below. Let me know how it works.

    Well, by doing extensive searching, I found out the purpose of the mystery pair of bytes starting at 140H: the checksum. No wonder it was different with each revision of the file.

    So, I took 6.0.6000.16567 (32-bit) and did the following. With this recipe, any version that comes along can be easily modded:

    1) With UltraEdit (or your favorite binary file editor), search for this pattern:

    0F 87 8b 00 00 00

    2) In the found location, replace those six bytes with:

    90 90 90 90 90 90

    3) Save the file and close the editor.

    4) Download PEChksum here (you can ignore the other four programs in the archive).
    http://www.bitsum.com/files/pesuite.zip
    5) Copy PEChksum.exe to the same directory as your modified tcpip.sys, open an elevated command prompt in that directory, and run:

    PEChksum tcpip.sys

    6) You're done.

    Your output will look like this (values will vary by version; this is the output for 6.0.6000.16567):

    + Processing file: tcpip.sys

    + Original checksum: 0x000C86AB

    + New checksum : 0x000C9DD5

    + Checksum required correction.

    Modules analyzed: 1

    Modules whose checksum was corrected: 1

    PEChksum automatically makes the modification necessary to the file: the checksum, which in this case was located at 140H-141H. This is necessary because you modified the file earlier.

    In summary, these are the changes for this particular file:

    tcpip.sys 6.0.6000.16567

    00000140 : AB D5

    00000141 : 86 9D

    0003F479 : 0F 90

    0003F47A : 87 90

    0003F47B : 8B 90

    0003F47C : 00 90

    0003F47D : 00 90

    0003F47E : 00 90

  • Hi All,

    in the link below you can find the new v1.9 of the tcpip patch supporting KB941644 (for 32bit only). Find it under the "Repair" section:
    http://www.yaronmaor.net

    Thanks for Rick for his helpful information in cracking the tcpip driver.

    Cheers,

    YaronM

  • RobG

    YaronM,

    Is it difficult to make the patch to 64 bit version ???

  • Rick

    Rob, I'd guess that you could follow the same recipe, but without seeing the original version I wouldn't know.

  • Hi RobG,

    Please send a copy of the unpatched version of 64-bit v6.0.6000.16386 tcpip.sys to the following address:

    info at yaronmaor dot net

    thanks,

    YaronM

  • RobG

    YaronM,

    Mine is the version 20689….

  • Rick

    Rob, KB941644 installs 16567 in some cases and 20689 in other cases (read a few posts back), but regardless we need the original UNpatched 16386 to be able to see what needs to be done.

    BTW, since I take it you were using the patched version (of 16386) on 64-bit until recently, how did it work for you?

  • Rick

    Rob, please email your 64-bit 20689 to yaronmaor dot net. Thanks.

  • Rick

    Er, that's: info at yaronmaor dot net

  • Rick

    For anyone wondering how to mod 64-bit, it's the same procedure as in post #131, with the following exception:

    1) With UltraEdit (or your favorite binary file editor), search for this pattern:

    0f 87 24 01 00 00

  • Hi All,

    There's a new revision (v1.9b) for the patch that includes support for 64bit and also to the two file versions that comes with the 32bit (16567 & 20689).

    Please follow the README.TXT file that comes with the patch.

    find it at: http://www.yaronmaor.net
    under the "repair" section.

    Cheers,

    YaronM

  • THE_CD

    Hi there

    I got 16567 version of file (tcpip.sys) after instaling KB941644 in Vista Utlimate x64.

    Anyone there with same case.

    YaronMaor are you planing patch this version of file for 64bit system ?

    Salutation

    CD

  • Hi CD,

    I was waiting for someone to come-up with this situation… πŸ™‚

    Please send me a copy of the tcpip.sys file with the version 16567 archived in RAR or ZIP.

    send it to: info at yaronmaor dot net.

    I will patch it and add it to the patch-package.

    Thanks,

    YaronM

  • Rick

    My theory about the KB941644 lottery is this. I'm anxious to hear from anyone who can prove or disprove it:

    -If you already have 6.0.6000.16xxx before installing it, you'll get 6.0.6000.16567.

    -If you already have 6.0.6000.2xxxx before installing it, you'll get 6.0.6000.20689.

    If true, I'd recommend people already be on a 6.0.6000.2xxxx hotfix before installing it, since I expect that the larger, seemingly "newer" 20689 version is the more comprehensive fix, a "QFE" (integrates all other fixes which apply to that module) rather than a "GDR" (contains only the specific fix and not all others). Why Microsoft would do it this way I can't understand, since they're both roughly the same size.

    This would be a convenient way to get onto 6.0.6000.2xxxx if you haven't installed KB941644 yet:
    http://support.microsoft.com/kb/940646

  • Silverbreaker

    @YaronMaor and @Rick

    your Patch (1.9) doesn't work on my 20689 x64 vista!! the tcpip.sys crachs after the reboot!

    please fix the problem!

  • Rick

    Silverbreaker: Was the RTM 64-bit patch working for you before? I ask because if it wasn't, the new one won't either, since it was done in the same way.

    Let's consider the new 64-bit patch a "work in progress" at this point until we can get more feedback.

    I'd also like to hear any feedback on the 64-bit 16567, which is forthcoming if it's not already there.

  • RyanHo

    Rick, you are right. It actually works. But I have another problem.

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

    The option "DDISABLE_INTEGRITY_CHECKS" doesn't work, I don't know why. I have to press F8 in boot menu and select "don't check driver integrity".

  • Hi All,

    I've just updated the recent patch to include the 64bit of v16567 driver.
    http://www.yaronmaor.net > "Repair" section.

    As Rick wrote before, please send us details on 64bit systems installed with patch. which version did you install? did it work for you? did the earlier versions work before?

    Thanks,

    YaronM

  • Rick

    RyanHo, You're talking about 20689, right?

    I don't know why that line in the batch wouldn't work for you. Did you run it from an elevated prompt?

    Everyone: When posting, please cite version and platform.

  • Rick

    Follow-up: the DDISABLE_INTEGRITY_CHECKS issue turns out to be well known and is unrelated to the patch.

    Basically, when any of these updates are installed, you cannot run the DDISABLE_INTEGRITY_CHECKS command:

    KB943899

    KB943078

    KB932596

    KB938979

    KB941649

    And there may be others. The F8 workaround, as previously mentioned, is the only solution right now for this idiocy (I certainly don't recommend uninstalling the KBs just for this). Watch this thread for further developments on this "evil updates" issue:
    http://forums.microsoft.com/technet/showpost.aspx?postid=2012166&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2

  • Silverbreaker

    @YaronMaor I have send you my tcpip.sys (x64, 20689) to your mail-adress (info at yaronmaor dot net).

    @all this patch (v. 1.9) was my first patch, i don't patch the .sys eather! first i installed the kb940646 and than the kbKB941644, at last the patch (1.9)…

    it doesn't work…

  • Rick

    Ripped from the aforementioned forum since it's important to know:

    If you tap F8 during startup (to get the bootup menu where you select normal mode, safe mode etc.), at the bottom is an option "DISABLE DEVICE DRIVER SIGNATURE ENFORCEMENT".

    Select this and Vista will bootup without device driver signature enforcement. This works. No really, it works. This is different to "bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS" or any other such options.

    The "bcdedit" seems to be for device signing during runtime. The recent slew of updates however seem to be applying a BOOTUP signature enforcement, which obviously being bootup happens before runtime.

    Unfortunately there is no way to get this to automatically run every time – you have to go to your bootup menu every time you start your PC up. Somewhat of an annoyance, but I have got used to it as a way to remove the half-open connection limiter.

    I hope this helps other people. It helped me as I thought I had destroyed my internet when I patched my tcpip.sys without backing it up and suddenly found anything related to networking was "broke" – any network related service not starting up etc., only to find this was because tcpip.sys was not loading due to it not passing this new bootup device driver signature check/enforcement.

  • Silverbreaker

    so, this mean that the patch will not run wihtout the "device driver signature enforcement"-bootoption?!

    oh damm, it's very stupid to boot windows every time like that…

  • RyanHo

    This is my situation. I already installed KB941644. I remove it, then download KB940646 and install it.

    I install KB941644 standalone patch download form MS website, but it doesn't work. TCPIP.sys doesn't be replaced. Finally I install KB941644 through Windows Update, that's all done.

  • Rick

    @Silver: Yup. It should be emphasized again that this is now the case for any patched system files, not just these. It's a deliberate choice they made by virtue of those (at least) 5 other updates I mentioned. I expect someone will come up with a way to make the F8 selection (or equivalent) "stick" though. People are pretty clever.

  • RobG

    Waiting to a automatic solution to DISABLE DEVICE DRIVER SIGNATURE ENFORCEMENT !!!

  • Rick

    Sleep/hibernation?

  • Ben Ford

    SO how do we fix the new version? ive seen so many different things, i'm lost.

  • Rick

    @Ben: It is a long and winding thread, but AFAIK the patches work. If you're 64-bit, you'll have to do the F8 workaround (see #151) because of MS's signed driver requirement that they've been rolling out starting last August with the first of a series of updates.

    This is not to say that it'll work perfectly in every case, but if the batch file executes properly there's a very good chance you won't see a problem.

  • RyanHo

    Another problem, when I use this patch on Vista x64 home premium 6.0.6000 (for tcpip.sys v20689), then launch emule or utorrent for 1 or 2 days, the port they use seems to be blocked. This never happened before patch.

  • Braddman

    I have a 6.0.6001.17052 TCPIP.SYS, does the crack work for this version? I will email the file to you.

  • Rick

    Braddman, please update to the RC Refresh build (likely the last public release until RTM), which uses 17128. There is a fix for that one, though it's not up yet.

    http://www.microsoft.com/downloads/details.aspx?FamilyID=529d992a-d69e-4c73-9213-7a7f3852c0ca&DisplayLang=en

  • Rick

    I should add, though, that SP1 (even 32-bit) does make you do the F8 dance, as described below in post #152 for pre-SP1 64-bit.

    Here's more:

    There's a new twist as of SP1 on 32-bit Vista systems:

    http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx

    "Driver binaries that load at boot time ("boot start drivers") must contain an embedded signature, *for both x86 and x64 versions of Windows Vista and Windows Server 2008*."

    Boot-start drivers.

    "In the special case of boot-start drivers–drivers that are loaded by the Windows Vista operating system loader–publishers must use an SPC to embedded-sign the driver binary image file. This requirement ensures optimal system boot performance."

    In tests using the publicly available 32-bit RC Refresh build, I found the experience identical to what's discussed above in the case of 64-bit: When booting, you're told that such-and-such a driver doesn't have a valid digital signature, and the only way around it is to use F8 for that boot only. In this particular case, I was testing [a modded] tcpip.sys.

    32-bit SP1 drivers are digitally signed, unlike the original release. This is not surprising or even unwelcome, but the enforcement is.

  • Braddman

    Rick, I just downloaded this RC like 2 days ago from Microsoft, and in the corner it says BUILD 6001. There isn't a newer one is there??

  • Braddman

    Rick, I just checked, my version is 936330 and the link you gave me is the exact same version, but I still have the TCPIP.SYS noted below!

  • Rick

    The KB number (936660) doesn't change from beta to beta. If you do properties on the Computer icon on the Start menu, you'll be able to see what version you have. It should say 6001.17128 (v.744) there. If it doesn't you somehow downloaded the original RC1 and not this year's refresh.

    I wouldn't get too excited about it though, because just to make me eat my words, MS released Refresh 2 of RC1 this afternoon to those in the beta. No word yet whether this one will be put out to the general public as well. It's 6001.18000.

  • admin

    There is no longer a need to patch tcpip.sys in Vista SP1, and I believe it's not possible to patch SP1 tcpip.sys without breaking it due to signature issue. There is now a external driver version to fix 4226 problem and unlock the TCP connection limit. Refer here:

    http://www.mydigitallife.info/2008/01/07/cracktcpipsys-driver-for-vista-sp1-v668-to-patch-tcpipsys-60600117052/

    It should works on all SP1 RC v.668, v.744 and latest 6001.18000. The author will write an auto patcher/installer once the SP1 is RTM.

  • Rick

    It says in the post that it's version specific though, in that case targeted at the original RC release. Is that not the case? Where's the author?

    Using a foreign driver running on top of TCPIP makes me uncomfortable and could have very subtle repercussions I'm not looking forward to discovering. At least this patch method is tried and true.

    As mentioned a couple posts ago, SP1 drivers are now signed even on 32-bit, so there is the F8 signature issue to deal with (at least for now), but as someone who doesn't boot that often, it's only a small issue for me.

  • admin

    Sorry about the version because initially we thought the tcpip.sys is changed every version, and hence the 'limit' memory location. It turns out the driver can still function with subsequent release. I will update the post soon. The patched SP1 tcpip.sys has some reports that it crashes, have you get it to work?

  • admin

    Rick, btw, to answer your question, the author is from China.

  • Rick

    OK, that's good to know about the memory address not changing. Incidentally, by "where is the author" I wasn't referring to the country but meant it in the sense of does he have a site, blog, etc, where he talks about this in more detail and can be contacted?

    In my case, patched 32-bit 17128 is working, so I would expect 18000 to as well (I didn't try the original RC). We also had some reports of success with the pre-SP1 January update to tcpip.sys.

    Even back to the original version, there were reports of problems, but there are a lot of variables on systems so lots of things to go wrong. The batch file has to execute in its entirety. You have to be aware of F8 (and if you're not, that looks like a crash). Etc. And some issues pertained to 64-bit, which I can't test directly (and the other solution doesn't work with 64-bit).

    Note: The patch "recipe" I posted sometime back can no longer be followed exactly with SP1 builds due to a problem with the now outdated PEChksum. You need to use a tool called PE Explorer instead but only to determine what the new checksum is so that you can change it manually (don't let PE Explorer do it). PEChksum may or may not be updated to handle the new compiler or whatever it is that MS changed in the way they make their files.

  • admin

    He doesn't has blog as of I know of. We currently IM. The driver theory is simple – monitor that particular memory address and change it to another value.

    That's great that the patch still work. That's mean we will have 2 editions that users can fall back to if one doesn't work. I will update this post soon too to reflect newer version.

    Btw, please use contact to email me if you wish to share your patched 17128. I don't see it been included by yaronmaor yet.

  • Rick

    Yaronmaor has it and was going to test it, but I suspect he got busy. With RTM coming as soon as early February, and probably no later than about a month from now, we'll all have one build to concentrate on soon anyway.

    Do you know of a tool that allows you to browse memory locations (as mentioned in the context of the driver)? I know one of Norton's could do that LONG ago, but I'm hard-pressed to think of one currently, and I'd like to check it out.

  • Hi All,

    sorry for the delay πŸ™‚

    I've just published v1.9c of the patch, directed for Vista SP1 RC v744 with tcpip driver build 17128.

    download at: http://www.yaronmaor.net
    listed under "Repair" section.

    at the moment only 32bit version is available.

    Cheers,

    YaronM

  • Braddman

    Hey guys-

    Here is the SP1 Eefresh 2 Script to install to download the Refresh 2 from Windows Update

    http://files.filefront.com/SP1+rcr2RKcmd/;9508147;/fileinfo.html

    Or make this into a reg file.

    @echo off

    reg delete HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateVistaSp1 /f > NUL 2>&1

    reg delete HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionWindowsUpdateVistaSP1 /f > NUL 2>&1

    reg add HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateVistaSp1 /v Beta1 /t REG_SZ /d dcf99ef8-d784-414e-b411-81a910d2761d /f

    IF NOT %errorlevel% == 0 ( goto ERROR)

    :SUCCESS

    @echo.

    echo ===========================================================

    echo Windows Vista SP1 registry key has been set successfully.

    echo Please check for updates in Windows Update.

    echo ===========================================================

    @echo.

    goto END

    :ERROR

    @echo.

    echo ===========================================================

    echo FAILED to set Windows Vista SP1 registry keys.

    echo Please run this script by right clicking and selecting

    echo "Run as Administrator".

    echo ===========================================================

    @echo.

    goto END

    :END

    pause

  • Pingback: Windows Vista Internet Probleme - Forum Fachinformatiker.de()

  • Braddman

    Also, this new release DOES NOT say evaluation version on the bottom right. And when you go to properties it says SERVICE PACK 1 now.

  • Tmanxxiv

    I've installed this patch before on my 32 bit system but i recently upgraded to 64…I can't seem to get it to work now. After I install the patch (64-bit 16567) and reboot, it freezes at logon.

    Yes, i disabled UAC and ran as administrator.

    Vista Ultimate 64 is what I am running.

    Any suggestions?

  • Rick

    Tmanxxiv, did you literally mean "at logon," as in when you enter your password? Because that's well after tcpip.sys would have loaded. Or do you mean before Windows loads in regard to getting a message from the boot menu about loading unsigned drivers (in which case you need to use F8, as described earlier).

    And just so we're on the same page, you did also edit the icacls line in the installation batch file to include your username, right?

  • Tmanxxiv

    Yeah, it actually happens at login when i type in my password. I thought that was funny…but hey stuff happens.

    I did edit icalcs as well…maybe my system is just acting up

  • Tmanxxiv

    After thinking about your post Rick, i decided to check it out anyway…turns out i spelled my user name wrong…

    Thanks for the pickup there buddy

    -Travis

  • ElQuia

    Hi. I tried "EventID4226Fix for Windows Vista v1.9b supports KB941644 v16567+v20689(32/64bit)" as published on http://www.yaronmaor.net/repair.htm.
    My vista x64 has tcpip.sys ver 6.0.6000.20689. I run the bat as specified, it said everything ok. But when I rebooted, my network connection didn´t work, DUMeter service for example didn´t start, anything related to networking did not work.

    Please somebody: IDEAS?. I´ve just started using Limwire and found the limitations everybody does.

    HELLLPPPPPP !!!

  • Rick

    ElQuia, check out some of the preceding posts. There are certain things you must do, such as what I mentioned in #180 about your username and the line in the batch file. And as mentioned in #179, you'll want to ensure you do a "run as admin" when you run it.

    If that still doesn't work, edit the batch file again, remove "@echo off" and put a "pause" after each line so that you can be sure each line is executing as expected.

  • ElQuia

    Hey Rick. I´m DUMB, usually I ALWAYS READ preceding post. uhuh. Well, Ill try:

    QUESTION: I already have uac disabled in my user "Pablo". This user is an Administrator, see the bat below , I echoed the uac line, IS THIS CORRECT?. Please tell me if the sintax for username is correct?.

    I´d try, but each time I have to recover (acronis) a C: backup its 40 to 50 minutes idle.

    THANKS FOR YOUR QUICK REPLY πŸ˜€

    Pablo

  • ElQuia

    Sorry here is the bat:

    @echo off

    TITLE Windows Vista Event ID 4226 Auto Patcher v1.9

    echo.

    echo Windows Vista Concurrent TCP/IP Connection Attempt Limit Auto Patcher

    echo Event ID 4226 Fix

    echo Version 1.9b

    echo.

    echo Auto Patcher batch script by http://www.yaronmaor.net
    echo.

    echo for 64-bit version of Windows Vista (v20689)

    echo.

    echo.

    echo Confirm to apply? (Press Ctrl-C and answer Y to terminate)

    pause

    echo.

    echo.

    echo ** by Pablo** reg import Disable_UAC_Prompt.reg

    takeown /f %Systemroot%System32drivers cpip.sys

    icacls %Systemroot%System32drivers cpip.sys /grant "Pablo":f

    netsh int tcp set global autotuninglevel=disable

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

    copy %Systemroot%system32drivers cpip.sys %Systemroot%system32drivers cpip.original

    echo.

    echo Original tcpip.sys driver has been renamed to "tcpip.original" in its original folder.

    echo.

    copy tcpip64-20689.sys %Systemroot%system32drivers cpip.sys /y

    reg import Vista_TCPIP_limit_50K.reg

    echo.

    echo *** Patch installation is complete. Please RESTART your computer!! ***

    echo.

    pause

  • Rick

    OK, since UAC is disabled, it doesn't matter what you did with the UAC line. The username syntax on the icacls line is correct. So assuming that all lines executed without incident (which is why I recommended removing @echo off and inserting a pause after each important line), I'm not sure what to make of it. Every system is different, and it doesn't seem to get along on your system for whatever reason. Do you have other Internet related kernel-level utilities, like ZoneAlarm, which may need to be notified of the change before "allowing" you out onto the Internet?

    BTW, rather than restoring the entire image each time you experiment with this (does it really take most of an hour?!), it's easier to have a bootable emergency CD on hand which is capable of accessing NTFS volumes. That way you can simply access the drivers directory and rename your previous tcpip.sys file back again. It's handy to have in general.

    http://www.bootdisk.com

    Or Google "hiren bootcd" for a treasure trove bootable disk image that you will want to put under your pillow at night.

    Active Bootdisk is also nice, though not technically free. Ahem.

  • ElQuia

    Rick, havn´t tried yet after first try, was waiting for your comments on the username in the bat. Will try later and keep you posted.

    BUT: am using eset ess (firewall, av + antispam). Usually should´nt have a problem. Don´t know if ess will recognize the modded tcpip.sys as "foraneous" and cut down comm.

    Keep you posted.

  • MtK

    @Yaron,

    I've used your patch for 17128 – no good.

    after the restart the Windows won't start up…

    I had to repair it with the installation CD…

  • Rick

    x32 or x64? And you didn't provide nearly enough detail. See the previous several posts for tips.

  • MtK

    Sorry for that: Vista x32 SP1 RC 17128.

    Installed Yaron's Patch + restarted = win won't start-up.

  • Rick

    I've tested that combo personally and it does work. "Won't start up" is very vague. Do you mean you get the textual message about unsigned drivers? If so, remember that anytime you introduce an unsigned boot driver into SP1 (64bit *or* 32bit) you must now use F8.

    Or are you talking more like what ElQuia found on 64bit? If so, I'd mention the same things to you as I did to him, since those are all the possible things you can check.

    BTW, I wouldn't get too concerned about this older RC build, since SP1 went RTM today and it'll leak soon one way or another. Since Server 2008 also came out, and it and RC1 are sync'd to the same codebase, it's interesting that Server 2008 has the same build string (6001.18000.080118-1840) as the last SP1 RC "Refresh 2." One would assume then that the last SP1 RC *is* RTM (something MS last week denied) but I'm holding out for official word. Sometimes things aren't as they seem.

  • MtK

    I'm getting a message outside windows saying:

    "Windows Failed to Start. a recent hardware or software change might be the cause. To fix the problem:

    1. Insert your Windows installation CD & restart.

    2. Choose Language.

    3. Click "Repair…"

    File: windowsSystem32drivers cpip.sys

    Status: 0xc0000428

    Info: Windows cannot verify the digital signature for this file.

    Pressing ENTER, gives me the same menu as if F8 was pressed, non of the options make Windows Start-Up (I get the same error page all the time)

  • Rick

    Yes, that's the new normal for SP1 (see post #164), but you will be able to get around it by using the F8 option "DISABLE DEVICE DRIVER SIGNATURE ENFORCEMENT" (or words to that effect). Try it again. If that doesn't work for you I have no explanation.

  • MtK

    Thanks, it seemed to work.

    Will I have to do this on every Start-Up?

    Will/Can this be fixed?

  • Rick

    For the time being, yes, though it becomes almost a non-issue if you mostly use the sleep/hibernate feature rather than rebooting.

    I'm sure someone will eventually figure a way around it, at least on 32-bit, where I'm surprised it's enforced in the first place. There may even be an official way to do it on 32-bit.

  • MtK

    Thanks again, I'll wait at least for the final release of SP1, then will see..

  • Rick

    It's confirmed now by MS: SP1 RC Refresh 2 (build 18000) is indeed RTM.

  • admin

    Rick, where do you read the news?

  • Rick

    Admin, CYM

  • Rick

    ElQuia, it’ll happen eventually, no question. Here’s the problem: In SP1 x64, as opposed to any other release, the byte pattern that needs replacing has changed. And I’m afraid that I have no idea whatsoever how to go about finding the new pattern. It’s going to take either the person who found the original pattern in the old RTM release to come forward, or someone just as knowledgeable. I’m guessing that it was found with a debugger but don’t know.

  • ElQuia

    Rick: Hello. I´ve just (yesterday) installed Service Pack 1 (RTM 6.0.6001.18000) on Vista 64 bits (x64). There´s a note in the CrackTcpip.sys patch that says that it won´t work on x64. Any Chance of a patched tcpip.sys for x64 build 18000??. Please?

    Best.

  • ElQuia

    Uh Oh!. Well I guess us non programmers will have to wait till someone with more knowledge than us comes up with a solution … I very like the idea of a system driver like cracktcpip.sys … IF it worked on x64. Well thanks anyway!!!!

  • R32

    Does anyone need a patch for tcpip.sys 6000.16627 (x86)?

  • Nuno

    Hi

    Can anyone tell me how can i see what version i have of tcpip.sys?

  • Pingback: Windows Vista - Page 140 - Computer Games Forum()

  • maxin

    Hi

    need a patch for tcpip.sys 6000.16627 (x86), thanks.

  • Rick

    @maxin/R32, please email a copy of the file to:

    info at yaronmaor dot net

    I'm a little surprised that MS had to release another TCPIP update, since they just released one last month. BTW, SP1 is not affected byt the update, but since it's not "officially" out yet (though incredibly easy to get anyway), I guess many people will still need this one.

    @Nuno: Put this into the search box:

    %systemroot%system32drivers

    Now located tcpip.sys and examine its Properties by right-clicking it.

  • Rick

    Same email request (see previous post) to anyone with:

    6.0.6000.20752

    Unfortunately, just like with last month's TCP update, MS08-004 is one of those which can result in either of two different TCP versions.

  • R32

    That's the diff for tcpip.sys 6000.16627 (x86) from yesterday's update …

    Have fun!

    00000140: 7F A9

    00000141: 7A 91

    0003F4B9: 0F 90

    0003F4BA: 87 90

    0003F4BB: 8B 90

    0003F4BC: 00 90

    0003F4BD: 00 90

    0003F4BE: 00 90

  • swashbuckle

    I need a fix for v20752.

    Any idea when its coming out Rick?

  • swashbuckle

    to rick->

    btw, do I have to disable auto-tuning after patching?

  • Rick

    @swashbuckle, send it here if you haven't already (same for anyone with 16627):

    info at yaronmaor dot net

    It should be out soon after.

    Autotuning is automatically disabled by this line in the batch file:

    netsh int tcp set global autotuninglevel=disable

  • Hi All,

    just published v1.9c for KB946456

    with driver build v16627(32bit Only).

    find it at: http://www.yaronmaor.net under the Repair section.

    Cheers,

    YaronM

  • swashbuckle

    can i leave auto-tuning on after removing the tcp/ip limit?

    will it have negative effects on the tcp/ip stack performance

  • Rick

    Test. Either there's a problem with the comment system, or there's a pretty low limit on comment length.

  • Rick

    @swashbuckle, great question. I don't know for sure, and I think it might vary from person to person. I'd invite anyone to try enabling it again to see how it goes.

    First, take a look at comments #34, #38, #39. That's one case where it did make a difference, though it was complicated by using the packet-capture tool WinPCap (most don't run anything like that).

    (cont'd)

  • Rick

    (cont'd)

    I think the whole "disable autotuning" thing got started not because of anything to do with this patch exactly, but rather this (and notably the "previously" article linked inside):

    h**p://w*w.mydigitallife.info/2007/05/24/increase-multithread-download-speed-by-disable-vista-auto-tuning-on-tcpip

    (cont'd)

  • Rick

    (cont'd)

    Though I doubt that most people saw any of those problems in Vista with autotuning on, which after all, is the default. Particularly in SP1, with its 500+ fixes, I have serious doubts about the popular advice to disable autotuning, especially since the entire point of the feature is to maximize network performance. Disabling it may be urban legend at this point outside particular issues. It should be noted that as of last September at least, MS did have a general issue relating to it still in their KB:

    h**p://support.microsoft.com/kb/940266/en-us

  • swashbuckle

    thanks rick,

    btw have u received v20752 tcpip.sys which I sent?

  • Rick

    @swashbuckle: No

  • Andy

    According to Ricks How-To I've successfully patched the tcpip.sys v6.0.6000.20752. It works great – no event id 4226!

    Thanks so far!

  • Andy

    For those who can't wait: I've uploaded a modiefied version of the patch . It works fine for Vista tcpip.sys v6.0.6000.20752.

    Have fun πŸ™‚

  • Andy

    For those who can't wait: I've uploaded a modified version of the patch here. It works fine for Vista tcpip.sys v6.0.6000.20752.

    Have fun πŸ™‚

  • swashbuckle

    Rick –

    I have tried to send you the v20752 tcp/ip to your email again.

    My email wldn't let me send a .sys file out.. lol

    Can you check if you have received it?

    Regards

  • Rick

    @Swashbuckle, please ZIP it and send it in that form.

  • swashbuckle

    yeah i zipped it and sent it to info @ yaronmaor dot net

  • Sorry for the long wait..

    I've uploaded v1.9d which supports KB946456 with driver v20752(32bit Only)

    find it at: http://www.yaronmaor.net

    for everyone seeking for 64bit/2008 versions- we don't have any success so far. if anyone knows better – please contact me through my site.

    Cheers,

    YaronM

  • Rick

    More specifically: 64-bit *SP1*. And the reason that can't be patched right now is that the byte pattern has changed from earlier 64-bit releases. We're seeking someone who knows how to go about finding the new pattern, which will probably take someone with a 64-bit SP1 system and a debugger.

  • swashbuckle

    thanks dude!

  • Huzi

    Please provide patche for 64bit 16627 …

  • Rick

    64-bit versions of 16627 and 20752 need to be sent here before they can be made available (ZIP please):

    info at yaronmaor dot net

  • xboris

    Does this patch works also with vista v6.0.6001 (sp1) ???

  • Rick

    xboris, yes, as long as you mean 32-bit. See "EventID4226Fix for Windows Vista v2.0 for SP1-RTM (build 18000) (32bit only!)" here:
    http://www.yaronmaor.net/repair.htm

    Don't forget to read the Readme for an important advisory.

  • Nick

    Hi..

    just wanna say thanks for the patch…works perfectly. But since applying it, I have noticed a new Event Log entry which I can't get rid of:

    Source: tcpip

    Event ID; 4227

    TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.

    I have seen a few websites which suggest disabling/reenabling my LAN connection but that doesn't stop the entries being created. Plus my network connection seems to be working fine.

    Is this anything worth worrying about of is it just a minor side effect from patching tcpip?

    Thanks again πŸ™‚

  • Rick

    Nick, which Vista and patch are you running?

    I just filtered my Event Viewer on 4227, and I see that it's happened only 6 times in this 10 month-old x86 installation, the last one being 5 months ago. One of them even occurred before implementing the patch.

    Do you never show it happening before? And how frequently are we talking about?

    As you found, MS's help page on it doesn't seem too concerned, and it is only a warning, one of many different kinds of warnings. Now, if we're talking hundreds or thousands of them like 4226, then there's reason for concern.

  • Nick

    Thanks for the reply Rick.

    I'm running Vista Ultimate x32 and have used patch v1.9.

    It's not an entry I have noticed before patching and the frequency is sometimes as much as one every 30 (or so) minutes but sometimes less frequent. At the time it's logged, i'm not using any p2p software, just browsing the web and checking mail.

    Everything's running sweetly though so i'm not too concerned, just curious as to why it has started.

    Thanks πŸ™‚

  • Rick

    I think it's going to remain a mystery due to the infinite number of variables. I'm also on Ultimate x32, so it's apparently something you have installed/do that I don't, or vice-versa.

    Who knows, maybe SP1 will be the trick for you.

    Do you still have tcp autotuning off (this occurs in the installation batch file)? I do, but was considering turning it back on, since I don't know of any reason currently that it should be off. If you have it on, that would be one fundamental difference.

  • swashbuckle

    hi nick, it might be your router's limit on the 1/2 open tcp/ip connections..

    i know some routers that have a 180 limit

  • Nick

    @Rick:

    Yep…autotuning is still disabled.

    @swashbuckle:

    Thanks for the suggestion but I've had a good look in the router interface and I can't see any 'half-open tcpip connection' settings so not sure if my router (Netgear DG834G) is to blame.

    Like I said previously..i'm not too fussed about the entry as I haven't noticed any ill effects, was more curious than anything.

    Anyway, thanks for all the suggestions and help.

    Nick

  • Rick

    It's interesting that a half-open setting is in some routers (I don't even see it in DD-WRT, and it has just over 5,000 different settings). I guess that's in consideration of non-Windows machines? For modern Windows machines, their half-open setting would be the limiter, not the router. Still, you said it happens when there's no P2P going at all, so that couldn't be it. I'm curious to see if anyone else is getting any notable number of 4227's. I even enabled autotuning –which is perfectly fine to do AFAIK–and still don't see it.

    I've given up trying to understand Windows "error" logging. For example, nothing to do with this patch, but in Vista I've always gotten about 10 ID 51's when simply inserting a blank DVD (half as many with CD+R). Not a written one, a blank one.

  • Lee

    Hello, after applying v2.0 I can not connect to the internet at all, Vista fails at recognising a connection,

    after running the Undo .bat and a reboot, I can connect to the internet once again,

    can someone please help me with this issue?

    I am using Vista Enterprise 32bit

    thanks in advance

  • Rick

    @Lee,

    You *are* running RTM SP1, right? If not, you have the wrong version.

    And since you're getting back into Windows, you know about the necessity to use F8 at boot to disable driver signing checking, so it's not that.

    Also, you verified that each line of the installation batch file executes successfully from your elevated command prompt.

    That leaves, as I think happened for one previous poster, something else, a wildcard. And my best guess as to what that is, since I definitely know the file works, is interference being run by security software, particularly a firewall but possibly any other kind. Check to see that it's not blocking communications because it sees a new system file, namely tcpip.sys.

  • frazbox

    how do you check tcpip without using this patch? i've been searching google but cannot find a method to do that search

  • Rick

    frazbox, could you restate the question?

  • Mophead

    I'm getting the error message "The current logged on user does not have ownership privileges…" but I'm the only user on this computer. Wouldn't this give me the admin privfileges?

  • Rick

    Mophead, you'll want to run the installation batch file from an elevated command prompt or by right-clicking it and choosing "Run as administrator."

    Note that the "icacls" line in the installation batch file just uses whatever the currently logged in user is, and even if that user is listed as an "Administrator" in User Accounts, it won't be one truly when UAC is enabled, thus the need for elevation.

  • Semp

    Hey, I did the auto patch downloader and it said it installed but it said there was an error and that 1 file was installed correctly and 0 failed. Which didn't make much sense, and at the end it said everything was successful but it still had the error messages inside it. Then when I restarted my computer I didn't have to press f8 or anything it just started up, and my downloads are still as slow as ever. I tried downloading the KB946456 but it never works it says "The update does not apply to your system" I don't think its worked. Someone help please.

    Thanks in advance.

  • Rick

    Semp, that phrasing telling you that 1 file was installed and 0 failed means just that: success for that particular command. It's not an error message.

    You only need to press F8 if you're on SP1 or using 64-bit.

    KB946456 is a security update for TCP/IP and not related to performance, but since it's a replacement of your tcpip.sys, you'd want to install it *before* patching. The only way it shouldn't apply to your system is if you're on SP1, which you can't be. It's also possible that that update was installed previously via Automatic Updates. You didn't mention what version of tcpip.sys you're on, so there's no way of knowing.

    As you probably know, there are numerous things that contribute to torrent speed, and half-opens are but one of them. Speeds are almost entirely unpredictable. Half-opens are not a silver bullet and it's likely the problem lies elsewhere (if it's even a problem and not just a slow torrent).

    Still, you want to be sure that the patch actually did install. Look in your windowssystem32drivers directory to see if the tcpip.sys there is the one from the ZIP file you downloaded. If it is, and assuming that the rest of the batch file executed (importantly, the modification of the Registry), then you know the speed has nothing to do with half-open connections (well, assuming your torrent client is configured for a sufficient number of half-opens).

  • ZeroHart

    Hello I just applied patch 1.9d in my v20752 tcpip.sys from my Vista Ultimate x64 and I am getting this error with no connection

    "the dependency service or group failed to start"

    and

    "failed to read firewll configuration"

    can you help me please

  • Rick

    ZeroHart, as might have happened to a couple people before you, I suspect that whatever security program(s) you use has taken upon itself to halt communications due to a foreign driver being injected into the system. See if you can tell it otherwise.

  • ZeroHart

    Actually I found out what happened! I did not do the f8 thing in the reboot!! now works perfectly just have to remember to do the f8 thing everytime i reboot

    Thanks!

  • Rick

    ZeroHart, that's confusing, since if you didn't use F8, you shouldn't have been able to get into Windows at all, right? Because an updated 64-bit Vista (and Vista 32-bit SP1, too) requires that you use F8 to disable signed driver checking with each boot.

  • ZeroHart

    Yes I know and to be honest I have no Idea what happened! If I dont use f8 I get to windows but no internet! if I use it it works!

    I use a Vlite version of the Vista! and I disable a lot of unused services, maybe that is why

  • Peter

    hello..

    I noticed every time i turn on my computer, the event id 4227 appear in the event log.

    I dont really know did this happen before or after the patch(1.9c),and my internet connection seems fine. im using vista Ultimate(no sp1) and I'm using wireless g usb adapter. my router is 2wire2701 hg-g.

    I also had read the previous reply and I'm just wondering,what event 4227 does to my internet connection?

  • Rick

    Peter, so you see it when booting, as opposed to anytime else?

    (For those wanting to catch-up, start reading from post #236.)

    You can filter your Event Viewer on 4227 to get a good look at how long it's been happening. For me, it's been almost 6 months now since I last saw it (and I also saw it happen before patching), so it's difficult to tie this to the patch alone. It could relate to the router, for example. Like many other (most?) messages in Event Viewer, I doubt it amounts to anything.

  • Peter

    thanks for the reply rick. Yes, i only see it when booting, it doesn't happen anytime else….

    o well, since the event doesn't do much to my internet connection, I'll just leave it there.

    Thanks once again!

  • happyroach

    thank you! the patch worked beautifully. now i can finally bear with vista ;D

  • airless

    any information on the possibility of patched tcpip.sys being made available here for Vista x64 SP1 (with tcpip.sys version 6.0.60001.18000)?

  • Rick

    airless, not that I've seen. The problem is that the byte pattern found in all previous 64-bit versions is no more in 64-bit SP1, and that's a fundamental problem. Until that's known, nothing can be done. If anyone knows of a place on the Internets where that new pattern is revealed, or a place which even shows how to go about finding it yourself (debugger?), please chime in.

  • David

    Hey all,

    Can anyone help me with this snag I'm running into? The autopatch doesn't seem to work with my 6.0.6000.16627 tcpip version. I tried to run a search for the KB946456 and came up with a windows update, which I downloaded and it said that it wasn't needed in my system, so it doesn't work. utorrent is so slow on vista, i think this patch may help if i can get it to work. Thanks.

    – David

  • Rick

    David, see #251.

  • frustrated

    Hi

    I am hoping someone will know an answer. I managed to patch my tcpip.sys file a few weeks back, and was running smoothly. I decided to install Vista SP1 and everything seemed to be OK. A couple of days ago I had a BSOD crash, my first. I noticed today thay my tcpip.sys had been changed. However, there is no version information.

    I tried using the older tcpip.sys file which worked previously, but that completely killed my machine.

    I still have no version number for tcpip.sys and for most of the other files in c:windowssystem32drivers

  • Rick

    frustrated, when you upgraded your SP1, your tcpip.sys would have been replaced. How it doesn't show a version number for you is baffling, but I saw something on XP once just like that, and I chalked it up to an Explorer issue. It's beyond the scope of this thread in any case and unrelated to the patch.

    As you found, you cannot use the older version in SP1. If you're on 32-bit SP1, download v2.0 from here:
    http://www.mydigitallife.info/2008/02/17/download-vista-tcpipsys-and-uac-auto-patcher-to-increase-tcp-connection-limit/

    There is no patch for 64-bit yet.

  • DavidMiller

    Hi, I updated my vista x64 to sp1 and now my bit torrent isn't work properly. It looks like there isn't a solution for the problem yet so meanwhile I will have to use my xp2 computer for downloads. I'll be eagerly waiting for the new patch!

  • ElQuia

    Hello everyone. I´ve been following this thread since some months. I´m CUIRIOUS: I use Limewire on vista x64 sp1. I DONT have a patched tcpip.sys (it´s not available), but for me limewire works very fast, if i do multimple donwnloads at the same time, it uses all my available spped (cable 1mb = 128 Kbps).

    Not than I´m complaining, but WHY dont I have the trouble everyone else seems to have????

    Best to Rick & all you guys.

  • Rick

    ElQuia, that's hard to say. Are 4226 errors that common in your System Log? If not, then what you're doing cumulatively on that system is staying mostly within the bounds of the default number of concurrent TCP connect attempts, and you're not going to notice much of anything. It would probably get noticeably worse the more bandwidth you had and the more you tried to do simultaneously on the system.

    The Limewire FAQ mentions a scenario in which the default limit can lead to being disconnected from their network. They mention these three things that may help (you may already be doing these, helping you out of the box):

    -Disable Ultrapeer Capabilities in Tools > Options > Speed

    -Minimize the number of simultaneous downloads (can also be found in Options > Downloads)

    -Minimize the number of other internet programs used alongside LimeWire

  • ElQuia

    Uh Rick, sorry for the very basic question: how do I see the system log?

  • ElQuia

    OK Rick Found it: yes, your right, got some 4226 events….

    By reading post i suppose there isn´t a patched tcpip.sys available for vista x64 SP1?

  • Rick

    No, it isn't, even though I've had a request out for the new byte string for 64-bit SP1 for quite a while (last time I mentioned it was #262). Apparently, the only people who know how to find it are off planet.

    But since you only have a few events and you're not noticing the problem, I think you're good as you are.

    Plus, you avoid the annoyance of dealing with the unsigned driver nag every time you boot Windows, which is a problem for 32-bit and 64-bit SP1. If you don't boot Windows that often (say, if you use standby instead) it wouldn't be that annoying.

    For those interested in an adventure, there is a way to get around it, and it's what I use for 32-bit SP1, but it's complex:

    The Jan 31 and Feb 26 posts here give the specifics:

    http://forums.microsoft.com/technet/showpost.aspx?postid=2012166&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=3

  • Adam

    umm i cant copsy the patch, and now ive lost the whole of by desktop i just get a blue screen, what do i do?

  • Rick

    For those interested in the latest on patching 64-bit SP1, check out the messages in this thread starting with till69's post on April 5th. It's looking very promising (I'm bjf2000 there).

    http://forums.mydigitallife.info/showthread.php?t=1249

  • lava

    Vista SP2 just came out. Does the update undo the tcpip fix? If it does, is another patch already in the works for SP2? I don't want to update if it's going to mess up my speeds on bt.

  • Rick

    lava, tell us all about 2010 please. It sounds way cool!

    OK, I assume you meant SP1, and that you're only getting to it now since you use one of the languages that MS didn't release until yesterday.

    Yes, SP1 does require a new fix, and it complicates things even on 32-bit due to driver signing checks.

    For 32-bit, see message #266, and be sure to read the Readme in that v2.0 of the file.

    For 64-bit, see the thread pointed to in #272.

  • Andrew

    Hi guys,

    I replaced the original tcpip.sys file with the "patched" tcpip.sys one. I restarted but now appears a BSOD at startup and I can't open my computer anymore!!! Help me please…

  • Observador

    Andrew, hit F8 on the boot screen and choose disable driver digital signatures check to load windows.

  • Andrew

    Doesn't work. πŸ™

  • Observador

    Andrew you have sp1 installed? What i said is for vista with sp1 of you don´t have it, you probably do something wrong, try restart in safe mode and put the original file again

  • Rick

    What version of tcpip.sys is this and on which version of Vista? And what specifically is the BSOD (particularly any module it mentions)?

    You can reinstate tcpip.original for now so that you can get back into Windows.

  • Andrew

    I can't open Windows,even in safe mode..I think I should repair Vista with the Recovery CD…

  • Andrew

    P.s. I have Vista Ultimate 32bit SP1

  • Rodney, PC newbie

    I'm having problems with the patch..

    I'm on a different computer right now as I can't get the patch to work, and any post I've read does not explain it.

    Though, my problem is simmilar to that of Sub Zero.

    I also have the “the dependency service or group failed to start” problem.

    When I read through what the (auto version) patch did, I see that the cmd

    netsh int tcp set global autotuninglevel=disable

    is not supported by IPv4 (which I recall being Internet Protocol v4)

    Anything you need to know to help me?

  • Rick

    Rodney, I don't know what the dependency service message has to do with this patch. The other person who mentioned it, attributed it to not using F8 at boot (to get around driver checking), but that didn't make much sense.

    Disabling autotuning is certainly compatible with IPv4 (which is what everyone uses), but it's entirely optional and is really only needed in certain specific situations that have all probably been solved by SP1 anyway.

    Speaking of which, what specific version of the patch are you using? SP1, 64-bit, etc.

  • Hi All,

    I just published version 2.1 of the patch.

    it includes the most anticipated version of x64bit SP1 including the ReadyDriverPlus tool that bypass the need to manually press F8 at boot time.

    Any feedback is welcome: yaron.pc AT gmail.com

    Cheers,

    YaronM

  • robgio

    YaronMaor,

    Thanks for your work !!

  • robgio

    YaronMaor,

    Can I use the patched TCPIP.SYS in my "non SP1" Windows Vista ??

  • admin
  • admin

    robgio, are you on 64-bit? You have to download version 1.6 or 1.9/b/c/d auto patch script for tcpip.sys prior to SP1.

  • robgio

    I´m on a 64 bit system… I don´t want to install the SP1 in my machine but I want to install the cracked TCPIP.SYS. Is it possible ??

  • Rick

    You just have to determine which specific version of tcpip.sys you're on and then use the appropriate update, but I'd reconsider your decision not to use SP1 first. I can't imagine why you wouldn't want to update.

  • robgio

    I don´t want to install the SP1 because my Vista is pirate and the SP1 will kill the activation that I use…

    my TCPIP.SYS´s version is 6.0.6000.20752

  • Rick

    Ah, OK (though I thought there were new cracks out by now). You want v1.9d, which you can get at here or other places. Be sure to read the Readme first.

    ReadyDriverPlus is then the easiest way to bypass the F8 boot requirement:
    http://www.tipandtrick.net/2008/permanently-turn-off-and-disable-64-bit-x64-windows-vista-forced-driver-signature-signing-with-readydriver-plus/

  • Rodney

    I assume its servicepack 1, since there's none shown.. Or is that servicepack 0?

    Its 32-bit.

    Doesn't automatic updates update to a newer service pack?

    IPv4, I know that I use it but it somehow isn't compatible. Autopatcher isn't able to either..

  • Windows XP x64 SP2 T

    what is the solution for Windows XP x64 SP2 ?

    i only find a workaround for SP1 but it does not work… i've installed Vista x64 patch but i still have errors in the windows event viewer…

    TY

  • XP x64

    what is the solution for Windows XP PRO CORP x64 SP2 ?

    – I've tried the XP patch but it only works with XP x64 SP1.

    – I've tried the latest Vista x64 patch but i sill have errors in windows event viewer…

    TY

  • Rick

    Here we go again:
    http://support.microsoft.com/?kbid=952709

    Tcpip.sys 6.0.6001.18063 891,448 26-Apr-2008

    Tcpip.sys 6.0.6001.22167 891,448 26-Apr-2008

    As is MS's habit (see earlier posts), you'll get one version or the other; it's hard to predict which or know why.

    If past "reliability and performance update" fixes are any guide though, DO NOT install it until some time has passed, unless you're severely affected by one of the issues. Until these updates are pushed out via Windows Update, it's more or less a public preview/beta. Seriously. These type of fixes have caused big problems in the past, they were tweaked, and then released on Windows Update in their revised form.

  • Jason

    try to find a workaround to change the tcpip.sys back to 6.0.6001.18000 and use cracktcpip.sys. Worked for me.

  • DA ERROR NO LO PONGAN ES ESTUPIDO AY QUE COMPONER WIN OSEA NO ES UN BUEN PARCHE MEJOR USEN XP Y SI SIRVE CUALQUIERA QUE ANDAN EN LA RED

  • Hi All,

    I've just published v2.2 of the patch that includes KB952709 with driver versions 18063+22167. The patch is for 32/64bit of Vista w/ SP1.

    the 64bit was not yet tested on a live machine. any comments are most welcome here..

    download at: http://www.yaronmaor.net
    Please read the README!.txt file for installations notes.

    Cheers,

    YaronM

  • matt

    Thanks, YaronMaor and all who make this possible.

    Just installed the new 2.2 patch for 64bit and it works great.

  • Dixours

    v2.2 of the patch with driver version 18063 does'nt work (Vista SP1 32 bits, with driver 18063).Vista auto-repairs at reboot… any idea ?

  • Rick

    @Dixours: You're not talking about the F8 requirement, right (see the Readme)?

    Are you saying that when Vista boots, it's restoring the previous non-patched version? If so, I wonder if it's being pulled from the hidden WinSxS areas under the Windows directory (they're obscurely named but there). I hadn't heard of that happening on x86, but we may need to start updating those copies during installation. Previously, they were updated only on x64.

  • Flow

    tcpip.sys patch for all Windows version including Vista sp1 x64/86!!
    http://half-open.com

  • Rick

    Flow, you should specify in the Questions section whether it's a dynamic patcher, like the EventID4226 patcher for XP. That is, does it search for the byte pattern and calculate the proper CRC, thereby allowing it to work for any future tcpip.sys without need for an update to the program. If it's not, you've created a lot more work for yourself.

  • Flow

    Of course it`s using dynamic search πŸ™‚

    I do not think, that it is interestingly for ordinary users.

  • Sunny

    Hi… I am having windows vista home premium 32 bit… Whenever i run Vista TCP/IP and Uac Patcher v1.9 … I got error saying that … Set global command failed on Ipv4 the requested operation requires elevation … Help me please thanks..

  • Rick

    Sunny, the batch file should be run elevated. Right-click it and choose "Run as administrator."

  • Sunny

    Thanks @ rick… For replying . But i did what you said but that also now working i am still getting very slow net i am a dial up user … Listen what i did .. I installed vista and by using take control application i take controls of all the files in system32/drivers/ … Than i booted in safe mode and ran that patch as administrator and got this error … Help me please currently i am dual booting vista and xp…

  • Sunny

    Thanks @ rick… For replying . But i did what you said but that also now working i am still getting very slow net i am a dial up user … Listen what i did .. I installed vista and by using take control application i take controls of all the files in system32/drivers/ … Than i booted in safe mode and ran that patch as administrator and got this error … Help me please currently i am dual booting vista and xp…..!

  • Sunny

    @ rick… But i did what you said but that also now working i am still getting very slow net i am a dial up user … Listen what i did .. I installed vista and by using take control application i take controls of all the files in system32/drivers/ … Than i booted in safe mode and ran that patch as administrator and got this error … Help me please currently i am dual booting vista and xp…

  • Sunny

    Not working dude … Any other tip plz

  • Rick

    Are you still talking about the error you mentioned in #312 or 4226 errors in Event Viewer? The elevation really should have worked, and if it didn't, a lot of other commands in the batch file aren't going to work either.

    That command "netsh int tcp set global autotuninglevel=disable" can be edited out of the batch file since it no longer is necessary. Then run the batch file again, ensuring that each command is completed.

    BTW, *do* you get 4226 errors in Event Viewer when downloading (pre patch)? I didn't think that would happen on dial-up. If you don't (and maybe even if you do), this patch isn't necessarily going to help you any.

  • Sunny

    Earlier i installed the patch successfully but i dnt know how i did it….. But Recently when i formatted my HDD and Installed Vista then again i tried to install that patch and failed….

  • Domdom

    I tried the half-open tool from http://half-open.com, full GUI easy and it seems the updated tcpsys is signed so no issue on reboot … nice … (Vista SP1) and it works at 100 half connections. Anyone else has tested?

  • Rick

    Good to hear. It was announced here in #308, but since the site says essentially nothing about the details of what it does, I was reluctant to try it (and still am, though I really have no need for it). I didn't even know it took the test-signing route rather than using ReadyDriver+ to mod the boot manager.

  • Domdom

    @Rick: tested it in a VM and it does what it is supposed to, no need to mess up with the bootmanager, you can also reverse to the original tcpip.sys … worth testing, and 4226 seems to be gone so … but more feedback would be welcome indeed! I havent noticed any weird behaviour so far …

  • Peterson

    I never patch TCP/IP on win2k,winxp pro,vista ultimate.

    Bitcomet work fine.

  • Rick

    @Domdom, so I take it that what it does is: dynamically patch your existing tcpip.sys, enable testsigning, run the string of commands necessary for testsigning (e.g. makecert, certmgr, signtool), and then patch your user32.dll.mui.

    Does it show any of that happening, or is it totally a black box in its operation?

    There are a lot of ways for the above to go wrong, particularly when running it again (either because a new tcpip.sys has been installed or it's just run again for whatever reason), so it's a little surprising that it all works. It's far more complicated than what the one for XP had to do.

  • Domdom

    Hey Rick, I have no idea, its black box but it seems to work, reboot is required, it creates a backup first, then modify a few bytes πŸ™‚ and thats it. Why dont you use free VMWare server and try it?

  • DePalmo

    My problem wa this: after applying this "home made" patch, all my external connections have failed, LAN and Wireless. After waiting about 30 mins for something to happen, nothing did. So i copied back original file and rebooted the system. Before login wireless hass connected, after login I can access my home network (LAN). So this patch doesn't work for me.

    Yes, I checked for the right version of the file, I installed that readydriver (or whatever it is) for quicker boot, but it didn't work. Looks like I will have to live with this stupid enforcment until official microsoft update (that will happen: never).

  • Rick

    Since the file itself (tcpip.sys) is good, it sounds to me like a firewall (or comparable) program was blocking or otherwise interfering with communications, as it didn't recognize the new system file.

  • DePalmo

    It looked to me like the system has recognized the new file and didn't want to accept it. No firewall could be blocking it, because I didn't change any settings for it. I just replaced the tcpip.sys (after some trouble-at first the file was locked, and I have some trouble removing it).

  • Rick

    I was thinking more along the lines of a security program of some kind which operates on file signatures, particularly for files in important directories like that one. Once it saw that the file was no longer the one it knew, it locked access to that file, though it certainly should have notified you about it.

    I don't know if the program you use does that, however.

    Tons of people have used the patched file without incident. It can't behave differently for you than others without some other variable involved.

    Checking the System log for that time period might be informative.

    Did you install using the batch file? Because that should have plowed right through any locked file issues.

  • Apareti

    Thank you much for the patcher.

  • Domdom

    Installed the half-open patcher (see previous post) and it works smoothely, no fuss to install, easy GUI, set the nummber of half-connection, reboot, and you are done. Rollback to original tcpip.sys is possible.

  • chris

    i have vista sp1 x32 and when i used tyhis patch i had 2 system restore it . it would not let me boot. i got blue screen of death do not use

  • chris

    BLUE SCREEN OF DEATH!!!! immediately at startup. finally figured out it was to do with the tcpip.sys being corrupt. beware of using this. leave your connection alone unless you feel like reinstalling windows.

  • Rick

    Chris, and what version were you using exactly? You mentioned you were on SP1, so depending on the version of your TCPIP.SYS, you should have been using v2.1a or v2.2 (see post #304 for details).

    It pays to read the comments, as you can't use old versions. They're proven good files, obviously.

    And be sure the read the Readme for special info having to do with the boot manager, else it will appear that you have BSOD'd even with the correct version.

  • Pingback: Link alle partite del campionato di serie A | Elettroaffari()

  • Pingback: W-Files » Blog Archive » Vista tcp/ip patch()

  • Shambles

    Got the blue screen of death, ran windows repair once now and it hasn't fixed anything. If anyone fixes this keep us updated, going to bed, too late to wait 20 minutes for the vista install cd to load again.

  • nikkipotz

    awwww., i also got the BLUE SCREEN OF DEATH!!! i just replaced the file and then restarted,m then boom., i can't even open windows., awww., what the hell., now i know why vista sucs., any solutions?

  • caddy

    So what should I set to net.max_halfopen in the uTorrent settings after I have installed the patch? Now it is set to 4. Should I even change it?? i am using vista home basic.

  • Rick

    I usually set uTorrent to 75 or 100, which should be more than it would use. This is well under the limit you set in Windows when doing the patch.

  • Pingback: Probleme mit Max. Verbindungen.()

  • Pingback: Limited or no connectivity on Vista when downloading torrents ! - Page 2 - Overclock.net - Overclocking.net()

  • Pingback: Limited or no connectivity on Vista when downloading torrents ! - Page 3 - Overclock.net - Overclocking.net()

  • Visitor

    Hi fellows, I used the patch and I couldn

    t boot the system afterwards. The reason is that during boot a msg about digital signature precented the start. Is this error common?

  • Simon

    Do you know why this patch doesn't work anymore?

    BECAUSE THIS PATCH IS A YEAR OLD – IT WON'T WORK ANYMORE MICROSOFT HAVE FIXED THIS SO WE CAN'T CHANGE IT.

  • Rick

    Simon, um, that's completely wrong. I know this is the Internet and all, but really, try to get your facts straight.

    Visitor, yes, since SP1 MS has boot-time driver signature checking. It's not only common but expected on all SP1 systems, even x32. If you don't want to have to bypass it manually every time you boot (using the F8 key), then read up the thread for a couple different alternatives.

  • Gloom&Doom

    It Works but whenever I use the patch Vista displays Test Mode watermark in all 4 corners of screen. When I restore original tcpip the Test Mode warnings disappear.

  • Rick

    Gloom&Doom, that's expected if you attempt to use a self-signed version of tcpip.sys in order to avoid having to hit F8 every time you boot. Somehow, you must have gone down that road.

    You can either use a normal, unsigned version of patched TCPIP.SYS (the kind in the files at YaronMaor's link above) along with a boot menu key stuffer called ReadyDriver Plus V1.1 (Google it), or you can continue with the signed version of the file you have, but you'll need to also do this, which can be tricky:
    http://www.mydigitallife.info/2006/11/23/remove-and-disable-windows-vista-evaluation-watermark-from-desktop

    Note that Step #10 at that link is incomplete. See line 738? That "Test Mode" needs to be converted like all the others you’ve done. If you don’t, you’ll still have four watermarks on the screen.

  • Oliver

    I've done everything by this instructions and my Vista collapsed. I'm on XP now, so if anyone has a same problem, let me know. I've tried to modify that tcpip.sys file given on site, but I can't even copy it. What's the deal?

  • jackson

    i tried to follow this now my vistas screwed and when open if it manages to open the mouse doesnt move and it freezes.

    My comp works on safe mode but i want to undo all i have done

    can anyone please help

  • Vista SP1 notes:

    dropped the modded tcpip.sys file and changed registry setting. after a reboot, I get a blue screen.

    blue screen didn't last long enough to capture error code. Also nothing logged in Event Log (lame Microsoft)

    My guess is this hack isn't ready for Vista SP1. It might work for pre-SP1.

    Good luck.

  • dime

    Guys DO NOT ATTEMPT THIS IN VISTA.. IT BSODs your Vista and gives a F4 stop error. I had to run the windows system restore function to get back in.

  • carlos

    Guys Vista SP1 patches this hack. This only applies to pre-SP1 Vista. So you can either decide to uninstall SP1, get a copy of XP, or don't use this hack until an updated SP1-compatible work-around surfaces. I'm leaning toward the XP route… tired of Vista's antics.

  • Pingback: Problem with torrent and ftp speed continuum - Overclock.net - Overclocking.net()

  • eSham_Atnaz

    is there a patch for vista tcpip.sys version

    6.0.6001.22121?

  • when the system is infected by malicious virus. VistaTcpPatch is actually the GUI version of the original tcip.sys autopatcher batch script. Patching tcpip.sys is a way to optimize and speed up BitTorrent

  • Eko

    Well it has taken me 3days of reading and working up the courage to try this out. Like alot of ppl here i upgraded from xp to vista and was seriously sadened when i tried to use utorrent with vishita excuse me vista. I searched about 6-7 other sites like this and finally tried this solution out and I am literally bout to ejaculate on my girl right now b/c everything went smoothly i had no errors anywhere and i'm simultaneously downloading 5torrents at 200-400kb/s a piece and browsing youtube and other sites flawlessly! I am so grateful to everyone's help and input b/c w/o my torrents I was about to go and hurt someone!

  • chazzyb31

    I followed the instructions here, but when I re-booted my laptop I was given the option to repair or reinstall Vista. Clearly this doesn't work for everyone, even if you follow the instructions carefully, so beware! Thankfully I'd had the presence of mind to create a system restore point before doing any of this, so my system reverted to where it was before I started tinkering with it. I won't be attempting this again in a hurry.

  • Robert

    I just try this shit and crashed my PC forcing me to insert the vista disc and restore the PC. My PC is a self assebled one vith a retail version of win vista ultimate edition. I tell this: if you are not able to recover and advanced manage your pc DO NOT TRY this or be advised to do a FULL BACKUP of your system. My was a really bad experience. Tried it also on an HP laptop: SAME RESULT. The OS doesn't start and give blue screen. I'm an assembler and not a novice. Be careful using this "patch". Man advised, half saved! Bye

  • Pingback: Utorrent vs Browsing - TORRENTs.RO()

  • Jan

    Hey. I wish i could use this. I did everything as listed above, but i cant replace the tcpip.sys file in my system. I really dont know how. I tried to do it as administrator, i tried to do it in safe mode, but always without success. Do anybody has any idea, please?

  • anonymous

    Bullshit! There is no limit of 2 half-open connections in vista home premium. More over this limit is not per sec. People please don't waste your time downloading crap. This limit is removed in Vista SP2 anyways. Check Microsoft Website.

  • tigr_sp

    DO NOT UPLOAD THIS PATCH FOR VISTA

    THIS WILL CRASH YOUR SYSTEM SO YOU HAVE TO RECOVER IT

  • Pingback: CrackTcpip.sys Driver for Windows Vista SP1 v.668 to Patch tcpip.sys 6.0.6001.17052 - Tech Journey()

  • Pingback: Unable to Disable Integrity Checks Cause Driver Files Not Found in 64-bit Windows Vista (x64) - Tech Journey()

Pin It on Pinterest

Share This

Share This

Share this post with your friends!