The windows patch process and how it works
View PDF | Print View
by: Admin
Total views: 75
Word Count: 318
A windows patch, a simple little thing. It comes down from the internet, installs itself and protects your computer from harm. How does the process work, from the point a windows patch is deemed necessary to the time it gets installed? When a hole in code is suspected, an identification process takes place to determine the extent of the vulnerability. A hole is any opportunity presented by software that can allow unintended access to your computer from outside parties. The risk of the suspected hole has to be assessed, and if it is found to be real and the result of a fixable piece of code, software security engineers then begin work on a windows patch that will repair the problem and eliminate the associated risk.
The windows patch has to be developed and tested thoroughly to ensure little to no impact on the client system that the windows patch is being installed onto. Compatibility must be tested extensively, and the process must be able to execute reliably or else there could be millions of failing computer systems as a result. Once the windows patch is ready to be deployed, the windows patch is then presented to the automatic update client present on all supported operating systems. For corporate windows patch, this monthly patch will be made available to systems administrators for perusal. The windows patch will not be authorized to send out to corporate systems that use an SUS or WUS server until it has been activated for deployment by an administrator.
Once the windows patch is in place, the machine will generally require a reboot. At that point, boot and functionality can be tested. If a problem manifests after the windows patch is installed, the patch can be removed and the system rolled back to test and see if it is the windows patch that caused the failure.
About the Author
Find more info regarding windows patches, stop in at windowspatchmanagement.com.
Rating: Not yet rated