Editing Hotfix (section)

{{Short description|Software update released outside the normal update cycle}}
{{More citations needed|date=May 2010}}
A '''hotfix''' is a [[software]] update that is released outside the normal update cycle or intended to be applied to a live system; often to fix a [[software bug|bug]].<ref>{{cite book|last=Bragg|first=Roberta|title=MCSE Self-Paced Training Kit (Exam 70–298): Designing Security for a Microsoft Windows Server 2003 Network|year=2003|publisher=[[Microsoft Press]]|location=[[Redmond, WA]]|isbn=0735619697|page=5–12|chapter=5: Designing a Security Update Infrastructure|url-access=registration|url=https://archive.org/details/mcseselfpacedtra00brag_0}}</ref>

Originally, ''hotfix'' referred to [[Patch (computing)|patching]] a ''hot'' system {{endash}} a production [[server (computing)|server]] that is actively serving [[Client (computing)|clients]]. For development, such a change usually must be designed quickly and outside normal development processes; at relatively high cost and disrupting other development effort. For the user, a hotfix is relatively risky since it is applied to a server without time for testing it. The risk of applying the hotfix must be weighed against the risk of ''not'' applying it. The problem to be fixed might be so critical that inaction is riskier than the potential loss of service.

Over time, the meaning has shifted to an update that is created with urgency or released outside the normal update cycle for the software.

Applying (installing) a hotfix generally involves the same process as any software update. Most modern [[operating systems]] and desktop [[application software|applications]] can download and apply updates automatically. [[Network administrators]] may use software programs to automate and simplify applying updates to the machines they manage.