 |
| - A - |
| - B - |
| - C - |
| - D - |
| - E - |
| - F - |
| - G - |
| - H - |
| - I - |
| - J - |
| - K - |
| - L - |
| - M - |
| - N - |
| - O - |
| - P - |
| - Q - |
| - R - |
| - S - |
| - T - |
| - U - |
| - V - |
| - W - |
| - X - |
| - Y - |
| - Z - |
Hotfix Releases
Hotfix Releases
When vulnerabilities are discovered in a program or operating system, hotfix releases are made available to maintain protection. They are mostly downloaded and instantly installed if an end-user has the automatic update feature of their program enabled. Some host-based platforms will automatically check for hotfix releases when a user is connected to the web. The patches may be rated from low to high-risk to indicate the seriousness of a particular threat. Hotfix releases are put in place so a user will know exactly what vulnerabilities need to be addressed.
Staying up to date with the latest patches as they are released is convenient for a user and provides added protection. Hotfix releases are even more effective when coupled with frequently updated web browsers, firewall, anti-virus and spyware applications.
In some cases, a hotfix release may not be the answer. An example would be a failed hard drive that actually requires new installation from a boot disk. One way to minimize this problem is to create an updated boot disk with all of the most recent patches slipstreamed into it. This incorporates the latest hotfixes into the system during the new installation.