Editing LAN Manager (section)

==Reasons for continued use of LM hash==
Many legacy third party [[Server Message Block|SMB]] implementations have taken considerable time to add support for the stronger protocols that Microsoft has created to replace LM hashing because the [[Open-source software|open source]] communities supporting these libraries first had to [[reverse engineering|reverse engineer]] the newer protocols—[[Samba (software)|Samba]] took 5 years to add [[NTLMv2]] support, while JCIFS took 10 years.

{| class="wikitable"
|-
|+ Availability of NTLM protocols to replace LM authentication
! Product
! NTLMv1 support
! NTLMv2 support
|-
| [[Windows NT 3.1]]
| RTM (1993)
| Not supported
|-
| [[Windows NT 3.5]]
| RTM (1994)
| Not supported
|-
|-
| [[Windows NT 3.51]]
| RTM (1995)
| Not supported
|-
| [[Windows NT 4]]
| RTM (1996)
| Service Pack 4<ref>{{cite web
| url=https://support.microsoft.com/kb/194507
| title=Windows NT 4.0 Service Pack 4 Readme.txt File (40-bit)
| date=October 25, 1998
| publisher=[[Microsoft]]
| access-date=May 12, 2015
| archive-url=https://web.archive.org/web/20150519010408/https://support.microsoft.com/en-us/kb/194507
| archive-date=May 19, 2015
| url-status=dead}}</ref> (October 25, 1998)
|-
| [[Windows 95]]
| Not supported
| Directory services client (released with [[Windows 2000]] Server, February 17, 2000)
|-
| [[Windows 98]]
| RTM
| Directory services client (released with [[Windows 2000]] Server, February 17, 2000)
|-
| [[Windows 2000]]
| RTM (February 17, 2000)
| RTM (February 17, 2000)
|-
| [[Windows Me]]
| RTM (September 14, 2000)
| Directory services client (released with [[Windows 2000]] Server, February 17, 2000)
|-
| [[Samba (software)|Samba]]
| ?
| Version 3.0<ref>{{cite web
| url=https://www.samba.org/samba/history/samba-3.0.0.html
| title=The Samba Team announces the first official release of Samba 3.0
| date=September 24, 2003
| publisher=[[SAMBA]]
| access-date=May 12, 2015}}</ref> (September 24, 2003)
|-
| JCIFS
| Not supported
| Version 1.3.0 (October 25, 2008)<ref>{{cite web
| url=https://jcifs.samba.org/
| title=The Java CIFS Client Library
| access-date=May 12, 2015}}</ref>
|-
| [[IBM AIX]] (SMBFS)
| 5.3 (2004)<ref>{{cite web| url=http://www-01.ibm.com/support/knowledgecenter/ssw_aix_53/com.ibm.aix.commadmn/doc/commadmndita/smbfs_intro.htm
| title=AIX 5.3 Networks and communication management: Server Message Block file system
| page=441
| publisher=[[IBM]]
| date=March 15, 2010
| access-date=May 12, 2015}}</ref>
| Not supported as of v7.1<ref>{{cite web
| url=http://www-01.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.networkcomm/smbfs_intro.htm
| title=AIX 7.1 Networks and communication management: Server Message Block file system
| publisher=[[IBM]]
| date=December 5, 2011
| access-date=May 12, 2015}}</ref>
|}

Poor patching regimes subsequent to software releases supporting the feature becoming available have contributed to some organisations continuing to use LM Hashing in their environments, even though the protocol is easily disabled in [[Active Directory]] itself.

Lastly, prior to the release of Windows Vista, many unattended build processes still used a [[DOS]] boot disk (instead of [[Windows PE]]) to start the installation of Windows using WINNT.EXE, something that requires LM hashing to be enabled for the legacy LAN Manager networking stack to work.