Software update is the process of changing installedsoftware with the intent to make it more modern. It also refers to thestored data used to update software. When storage was significantly more expensive,patching files was the dominant form of update. With the advent of larger distribution storage media and higher Internet bandwidth, it became common to replace entire files instead of patching.
An update may require prior application of other updates, or may require prior or concurrent updates to multiple components. To facilitate updates, operating systems often provide automatic or semi-automatic updating facilities.Package management systems offer update automation.
An update can be any size. An update can be relatively large when the changes add or replace data such asgraphics and sound files; for example for agame update. An update usually takes less time to run than an initial installation of the software.
Although often intended toupgrade, an update may instead degrade. An update may include unintentionalregression problems. In some cases, an update intentionally disables functionality, for instance, by removing aspects for which the consumer is no longer licensed.
Software update systems allow for updates to be managed by users and software developers. In the2017 Petya cyberpandemic, the financial software "MeDoc"'s update system is said to have been compromised to spreadmalware via its updates.[1][2] On the Tor Blog, cybersecurity expert Mike Perry states thatdeterministic, distributed builds are likely the only way to defend against malware that attacks the software development andbuild processes to infect millions of machines in a single, officially signed, instantaneous update.[3] Update managers also allow for security updates to be applied quickly and widely. Update managers ofLinux such asSynaptic allow users to update all software installed on their machine. Applications like Synaptic use cryptographic checksums to verify source/local files before they are applied to ensure fidelity against malware.[4][5]
Automatic updating has become more widespread over time. Some cite a cause of its prevalence to be due toWindows support in early 2000s.Service Pack 2 of Windows XP (available in 2004) enabled it by default.
Updates are classified many ways. Notable classifications in alphabetical order follow.
Ahotfix is a software update that is released outside the normal update cycle or intended to be applied to a live system; often to fix abug.[6]
Originally,hotfix referred topatching ahot system – a productionserver that is actively servingclients. 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 ofnot 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 modernoperating systems and desktopapplications can download and apply updates automatically.Network administrators may use software programs to automate and simplify applying updates to the machines they manage.Somehacker may compromise legitimate software update channel and injectmalicious code.[7]
Apatch isdata for modifying an existingsoftware resource such as aprogram or afile, often to fixbugs andsecurity vulnerabilities.[8][9] Patch is also the process of applying the data to the existing resource. Patching a system involves applying a patch. A patch may be created to improve functionality,usability, orperformance. A patch may be created manually, but commonly it is created via a tool that compares two versions of the resource and generates data that can be used to transform one to the other.
Typically, a patch needs to be applied to the specific version of the resource it is intended to modify, although there are exceptions. Some patching tools can detect the version of the existing resource and apply the appropriate patch, even if it supports multiple versions. As more patches are released, their cumulative size can grow significantly, sometimes exceeding the size of the resource itself. To manage this, the number of supported versions may be limited, or a complete copy of the resource might be provided instead.
Patching allows for modifying abinaryexecutable. Although this can be technically challenging (requires a thorough understanding of the workings of the executable), it may be feasible when thesource code is unavailable tobuild a full executable, and it allows for a smaller distribution which can be more economical than distributing full files.
Although often intended to fix problems, a patch can introduce new problems – a scenario calledsoftware regression. In some cases, an update intentionally disables functionality, for instance, by removing aspects for which the consumer is no longer licensed.Patch management is a part oflifecycle management, and involves a strategy and planning of what patches should be applied to which systems and at what times. Typically, a patch is applied in a permanent way (i.e. tostorage), but in some cases, a patch is applied to memory (i.e. via a tool such as adebugger) in which case the change is lost when the resource is reloaded from storage.
Software update is sometimes conflated with patch even though they are notsynonyms. An update can be implemented using patch files and the patching process. Also, some may contend that patching is not limited to modifying file content; that adding, removing and replacing whole files is patching. Typically, patch connotates a relatively small change, so a patch that is large in size or scope may be called the more generalsoftware update or another more specific name such asservice pack.Windows NT and its successors (includingWindows 2000,Windows XP,Windows Vista andWindows 7) useservice pack.[10] Historically,IBM used the termsFixPak andCorrective Service Diskette for such updates.[11]
In IBM terminology, aprogram temporary fix or product temporary fix (PTF), sometimes depending on date,[12][13] is a one or morebug fixes – distributed in a form ready toinstall.
A PTF normally follows anAuthorized Program Analysis Report (APAR),[14] and where an "APAR fix" was issued, the PTF "is a tested APAR"[15] or set of APAR fixes. However, if an APAR is resolved as "Fixed If Next" or "Permanent Restriction" then there may be no PTF fixing it, only a subsequent release.Asecurity patch is a change to correct the weakness described by a vulnerability. The corrective action prevents successful exploitation and removes or mitigates a threat's capability to exploit a specific vulnerability. Patch management is a part ofvulnerability management – the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities.
Security patches are the primary method of fixing security vulnerabilities in software. Currently Microsoft releases its security patches once a month ("patch Tuesday"), and other operating systems and software projects have security teams dedicated to releasing the most reliable software patches as soon after a vulnerability announcement as possible. Security patches are closely tied toresponsible disclosure.
These security patches are critical to ensure that business process does not get affected. In 2017, companies were struck by a ransomware calledWannaCry which encrypts files in certain versions ofMicrosoft Windows and demands a ransom via BitCoin. In response to this, Microsoft released a patch which stops the ransomware from running.
In computing, aservice pack comprises a collection of updates, fixes, or enhancements to asoftware program delivered in the form of a single installable package. Companies often release a service pack when the number of individualpatches to a given program reaches a certain (arbitrary) limit, or the software release has shown to be stabilized with a limited number of remaining issues based on users' feedback andbug reports. In large software applications such as office suites, operating systems, database software, or network management, it is not uncommon to have a service pack issued within the first year or two of a product's release. Installing a service pack is easier and less error-prone than installing many individual patches, even more so when updating multiple computers over a network, where service packs are common.
Service packs are usually numbered, and thus shortly referred to as SP1, SP2, SP3 etc.[16] They may also bring, besidesbug fixes,[17] entirely new features, as is the case ofSP2 ofWindows XP (e.g.Windows Security Center), or SP3 and SP4 of the heavily database dependentTrainz 2009: World Builder Edition.[18]Anunofficial patch, a.k.a. community patch and fan patch, is a software update created by a third party, such as auser community, without the involvement of whoever is considered the official maintainer of thesoftware (i.e. original developer). An unofficial patch generally does not change the intended use of the software, in contrast to other third-party adaptions such asmods orcracks.
An unofficial patch is typically intended to repair bugs and provide new capabilities such as support for neweroperating systems, increaseddisplay resolutions and new display formats.[19][20] While unofficial patches are most common for the PC platform, they can also be found for console games e.g. in context of the emulation community.[21]
Afan translation is an unofficial patch that adds natural language support to software.[22] Fan translations are most common forJapanese role-playing games which are often not localized for Western markets.[23][24]
Aslipstream like patch combines multiple official patches into one unofficial update package as a convenience to users when individual patches are only available online or as small incremental updates.
A common motivation for creating an unofficial patch is lack oftechnical support from the official maintainer which may result from:
Avideo game receives an update (often called a patch) to fix problems and to change features such as change game rules andalgorithms. These updates may be prompted by the discovery ofexploits in themultiplayer game experience that can be used to gain unfair advantages over other players. Extra features and gameplay tweaks can often be added. These kinds of updates are common infirst-person shooters withmultiplayer capability, and inMMORPGs, which are typically very complex with large amounts of content, almost always rely heavily on updates following the initial release, where updates sometimes add new content and abilities available to players. Because the balance and fairness for all players of an MMORPG can be severely corrupted within a short amount of time by an exploit, servers of an MMORPG are sometimes taken down with short notice to apply a critical fix.
Companies sometimes release games knowing that they have bugs.Computer Gaming World'sScorpia in 1994 denounced "companies—too numerous to mention—who release shoddy product knowing they can get by with patches and upgrades, and who make'pay-testers of their customers".[32]
Software update processes vary dramatically. Some notable processes are described here.
Updatingfirmware (i.e.motherboardBIOS) can be challenging when it involves replacing the entire image on the hardware. As such, an error or interruption during the update process, such as loss of power, may render the hardware unusable.
An update, a binary image, is often installed via a supplier-provided program that overwrite the existing image with another. This program may safeguard against serious damage. For example, the update procedure could make and keep a backup of the firmware in case it determines that the primary copy is corrupt (i.e. via achecksum).
In the cases of large updates or of significant changes, distributors often limit availability of updates to qualified developers as abeta test.
Hot patching, also known aslive patching ordynamic software updating, is the application of patches without shutting down and restarting the system or the program concerned. This addresses problems related to unavailability of service provided by the system or the program.[33] Method can be used to updateLinux kernel without stopping the system.[34][35]A patch that can be applied in this way is called ahot patch or alive patch. This is becoming a common practice in the mobile app space.[36] Companies likeRollout.io usemethod swizzling to deliver hot patches to the iOS ecosystem.[37] Another method for hot-patching iOS apps is JSPatch.[38]
Cloud providers often use hot patching to avoid downtime for customers when updating underlying infrastructure.[39]
Slipstreaming is the act of integrating updates into theinstallation files of their original app, so that the result allows a direct installation of the updated app.[40][41]
The nature of slipstreaming means that it involves an initial outlay of time and work, but can save a lot of time (and, by extension, money) in the long term. This is especially significant for administrators that are tasked with managing a large number of computers, where typical practice for installing an operating system on each computer would be to use the original media and then update each computer after the installation was complete. This would take a lot more time than starting with a more up-to-date (slipstreamed) source, and needing to download and install the few updates not included in the slipstreamed source.
However, not all updates can be applied in this fashion and one disadvantage is that if it is discovered that a certain update is responsible for later problems, that update cannot be removed without using an original, non-slipstreamed installation source.
Thoman had uploaded "DPfix 0.1 alpha," a patch that allowed Deadly Premonition players to manually adjust the game's resolution. [...] The most recent DPfix release fixed pixel offset errors that occurred at higher resolutions, fixed anti-aliasing when it was not being correctly applied, added improved depth-of-field effects, and added an option for screen space ambient occlusion.
Looking Glass Studios closed in 2000, a year after System Shock 2's release, and the copyright to the series went into the hands of an insurance company. That left EA with only the System Shock name, but no actual development rights.
Security vendor ESET, makers of the NOD32 anti-virus program, on Wednesday shipped an interim patch for the bug, almost a week before Microsoft Corp. is scheduled to release a properly tested security update.
Because of the severity of the threat, the SANS Institute, a computer security group, has released a patch for the vulnerability until Microsoft's fix is available next week.
![[2]](/mt/?noimg=&dark=on&url=https%3a%2f%2fweb.archive.org%2fweb%2f20110716024241%2fhttp%3a%2f%2fimg128.imageshack.us%2fimg128%2f1900%2ftra26ba.jpg){kind=link}
![[3]](/mt/?noimg=&dark=on&url=https%3a%2f%2fweb.archive.org%2fweb%2f20110718200414%2fhttp%3a%2f%2fimg145.imageshack.us%2fimg145%2f4573%2ftra37ws.jpg){kind=link}
![[4]](/mt/?noimg=&dark=on&url=https%3a%2f%2fweb.archive.org%2fweb%2f20110718200429%2fhttp%3a%2f%2fimg145.imageshack.us%2fimg145%2f7259%2ftra42bl.jpg){kind=link}