Apache HTTP Server Version 2.2

Apache > HTTP Server > Documentation > Version 2.2 > Modules

#### Please note

This document refers to a legacy release (2.2) of Apache httpd. The active release (2.4) is documented here. If you have not already upgraded, please follow this link for more information.

You may follow this link to go to the current version of this document.

# Apache MPM winnt

Available Languages: de | en | ja

Description: | This Multi-Processing Module is optimized for Windows NT.
Status: | MPM
Module Identifier: | mpm_winnt_module
Source File: | mpm_winnt.c

### Summary

This Multi-Processing Module (MPM) is the default for the Windows NT operating systems. It uses a single control process which launches a single child process which in turn creates threads to handle requests

### Directives

### See also

- Using Apache HTTP Server on Microsoft Windows

- Comments

## Win32DisableAcceptEx Directive

Description: | Use accept() rather than AcceptEx() to accept network connections
Syntax: | `Win32DisableAcceptEx`
Default: | `AcceptEx() is enabled by default. Use this directive to disable use of AcceptEx()`
Context: | server config
Status: | MPM
Module: | mpm_winnt
Compatibility: | Available in Version 2.0.49 and later

`AcceptEx()` is a Microsoft WinSock v2 API that provides some performance improvements over the use of the BSD style `accept()` API in certain circumstances. Some popular Windows products, typically virus scanning or virtual private network packages, have bugs that interfere with the proper operation of `AcceptEx()`. If you encounter an error condition like:

`[error] (730038)An operation was attempted on something that is not a socket.: winnt_accept: AcceptEx failed. Attempting to recover.`

you should use this directive to disable the use of `AcceptEx()`.

Available Languages: de | en | ja

## Comments

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.