Quote:
Originally Posted by john rogers
With all the versions of Windows I have ever used from 2.0 through 10 the issue of updates and security patches always has come up. In ALL cases you can configure these to happen at a time you select so you can watch it, look to see what is in it and finally when to do any reboots. A simple Google search will list the steps to do this for both home versions and also the server versions too.
If your computer is for work I would hope you have a "test" machine to do the update on first so you do not crash everything just in case?! I the case of a home computer generally most people do not have this BUT can do and setup a "restore" point so you can back up if things go to the pits. You do have a restore point don't you..........
|
I used to back in the day, I am not sure what the settings are on the new one. After initial setup I've been putting it to use from an off line location. The only change to its setup as received, was figuring out how to turn its CPU splitting off that came by default. I found out it was called hyper-threading, shut that down, and it's the only change I've made. Since my software was written for 64 cores, hyper threading was fixing an artificial limit. When physical 64 cores were divided by hyper threading; I was only partially using the abilities of the system.