If µTorrent is bogging down your high-speed Internet connection - whereby web browsing becomes extremely slow or either stops altogether - symptoms point towards an unpatched TCP/IP half-open limit. Most patchers directly modify the TCPIP.SYS file, which usually results in undesirable MS security issues and/or false positives from antivirus software. TCP-Z is different, as it alters the TCP/IP limit in memory, for a safe & fast solution under any Windows OS environment (including x64 Vista and the new Windows 7). Release the power of your network; download faster, and run more Internet tasks simultaneously - all without the side-effects of other patchers.

TCP-Z Features:

We’ve come a long way from the archaic Lvllord patch. TCP-Z is more than just a patcher; it’s a network monitor utility that incorporates both soft (memory) patching of the TCPIP limit, and the option to hard patch the TCPIP.SYS file.

Safe And Easy: Modifies Tcpip.sys in memory. The changes take effect immediately; there’s no need to restart the computer.

Wide Compatibility: It searches limited offset through signature, no longer focused on the MS upgrade and update. Support for all version of Windows, which are half-open limited, including: Windows XP SP2 SP3/2003/2008/Vista SP1 SP2/Windows 7, All 32bit (x86) / 64bit (x64) versions.

On-The-Fly Monitoring: TCP-Z shows number of established connections, half-open connections and download/upload speed in real-time. Software shows the number of warnings events in per-minute statistics (before and after patch), which indicates TCP half-open connection overload.

Implementation:

Download and unzip. Latest version is TCPZ_20081229 (with mirror here). There are two ways to implement TCP-Z:

1. Run either TCPZ.EXE, or TCPZ64.EXE (depending on your OS version). Here you’ll be able to soft patch TCPIP in memory, or patch the TCPIP.SYS file. Click the ‘Patch‘ tab.

1.A. — The first section is the ability to “Patch Memory”. Move the slider on the left to change the TCPIP limit to a new value.

1.B. — In the second area, “Patch File Tcpip.sys”, you can permanently change the TCPIP.SYS file (this feature is disabled under MS Vista).

2. Install the TCPZ Virtual Driver: This will automate the TCP-Z service without causing security issues (since tcpip.sys is not changed). Go into the \VirtualDevice directory, and run the applicable file. The options are available in the “Device Manager”. This virtual device will run automatically when Windows starts, and modify the TCP half-open limit value to 252, or as selected.

Vista x64 users: Be sure to read the “Readme.EN.txt” files in both directories. Another method of ‘hard patching’ TCPIP in Vista can be found at http://half-open.com.

1. Emil Says:

   Cool patch, just what I needed.

   Though I have one question - Can I actually re-enable these settings (in Vista x64) after the soft patching has been done:

   bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
   bcdedit.exe -set TESTSIGNING ON

2. voy Says:

   Still preferring lvllord’s eventID patcher. Why have a program running in the background if patching can be done on system level. I never had any problems with the eventID patch, so why bother changing?
   I give it points for the GUI, but that’s all. No need for another program.

3. asymmetric Says:

   sharky, that’s installation, not implementation.
   otoh, i really wish you could give us some real implementation details

4. ATOzTOA Says:

   Is it safe? 100%?

   I have got ZoneAlarm firewall, so isn’t it ok even if I hard patch?

5. pato Says:

   VOY: Does it work for you in Vista x64? I ended up using a rescue disk.

6. jake Says:

   This works well in vista 32 bit. I don’t see this running in the background under taskmanager - processes.

7. Anon-san Says:

   I still using xp-antispy patch, much better than lvllord’s patcher you can choise the number o connections.

8. Mick Russom Says:

   TO all who are questioning why lvllord style wont work easily in Vista, 64 bit anything or Windows 7. Its the signed driver bull that Microsoft is foisting. The problem is for someone to get a valid certificate to sign a driver you have to do:
   1) nothing wrong according to microsoft
   2) you cant touch system files
   3) you get one paid for signed driver per driver build version
   4) pass WHQL testing.

   It is expensive and obviously, since Microsoft’s private keys are unknown, no one can fake it.

   The in-memory memory patcher is the least-worst solution available today.

   You could, of course, write in to MSFT and ask that they allow you to configure the operating system you paid for. Stuff like this should be illegal, and if I was President,Gates and Ballmer would simply be detained GITMO style until crap like this stops.