Configuring Windows Ten Automatic Updates for Miners
While Windows Ten actually brought some improvements to the cryptocurrency mining spel, including the improved capability to detect and utilize numerous GPUs (with Windows 7 and earlier it wasgoed a ache to get more than 4-5 GPUs up and running), it also came with its own thorns. One of the thickest ones that I hear miners complain about all the time is Windows near insistence of automatically applying patches. While this is not necessarily a bad thing, the mechanism they use for users to control and schedule thesis updates have bot for the most part stripped away or hidden from view.
With earlier versions of Windows you could simply set “Never check for updates”, or perhaps “Check for updates but let mij choose…”, succesnummer OK and that wasgoed that, Windows would obey your wishes. Windows Ten is not so lightly dissuaded however, so this guide is going to voorkant one way of minimizing thesis annoyances and will help prevent the worst mining offenses such spil updating your movie drivers behind your back or rebooting your equipments at random times.
So I do not disable to update mechanism fully, if that is even possible, but there is a instrument that you can use to adjust various facet of the built-in update policy.
This device is called Group Policy Editor, or GPEdit for brief. It is mainly used te corporations to give IT private granular control overheen how the OS works ter their IT environment and is used along with Active Directory. However, wij can also use the device to modify the local group policy on our mining equipments. I suppose if you had a lotsbestemming of equipments and were crafty, you could roll them out ter a domain style and utilize Active Directory to thrust policies instead, but that is beyond the scope of this article.
To commence simply type gpedit into the Cortana search and select Edit group policy from the results spil shown ter the above pic.
This will bring up the group policy editor spil shown below. There will be two main categories displayed on the left forearm side under Local Pc Policy, one for Pc Configuration and the other for User Configuration. All of our settings will be under the Pc Configuration category. Note that there is a section for windows updates under the user configuration heading, but thesis are rather limited and mainly aimed at preventing users from making switches to windows update settings, not at all what wij want to do here.
From here wij will further drill down to Rekentuig Configuration ->, Administrative Templates ->, Windows Components ->, and eventually Windows Update.
You will need to scroll way down toward the bottom to find the Windows Update section spil there is a long list. Once there, simply dual click on the Windows Update folder to open the relevant folder containing the policies wij wish to modify.
There will be three policies wij will interact with which and that I have highlighted ter the photo below. Thesis are: Configure Automatic Updates, Do not include driver with Windows Updates, and No auto-restart with logged on users for scheduled automatic updates installations. Wow, that last one is a throatful but not to worry spil I will voorkant all three of the policies below.
Also, spil you can see, there are many other policies affecting Windows Updates that you can peruse at your leisure and apply if you wish, but I have found thesis three to be the most useful for avoiding unexpected mining downtime.
Configure Automatic Updates
The very first one wij will go overheen is very likely the most directly related to what wij want to achieve and that is Configure Automatic Updates, which is shown below.
By default this entire policy will be set to disabled.
The very first thing you need to do is select the Enabled radio button. By enabling this policy, you will now be able to choose which level of interaction you want to have with Windows Updates.
Myself, I still like to keep my equipments fairly updated, so I choose option Two which will notify you when updates are ready but will not automatically apply them. You can read through the other options and select a different one if desired. You can also add a comment if you want to straks remind yourself why you applied the policy. When finished click on Apply and OK to set the policy.
So now with this very first policy set Windows Ten should act more like the older version of Windows and notify you when updates are ready, but doing nothing further without your approval. You will periodically get a notification, such spil the one shown above, when updates are found and ready to be applied. There is no ongezouten dismissal for this notification window, again due to Microsoft’s aggressive thrust for updates, but if you simply select View updates you will be introduced with the list of available updates and can simply close that window and won’t be bothered again (at least for a little while). Of course if you are ready to apply the updates, you can proceed with that process spil usual.
Do not include drivers with Windows Updates
So while the very first policy takes care of the wagen updates for the most part, there are still a duo of situations wij need to address. One is how the update process treats device drivers.
When it comes to a dedicated mining equipment, most people pick a movie driver and stick with it unless there is a very compelling reason to switch. Since most of us are not using thesis to spel or perform other tasks, a functioning graphic driver that is delivering acceptable mining spectacle will usually last fairly a few driver version iterations before needing to be updated. Also, considering that most equipments will have Five, 6, 7 or even more GPUs, it is often best to do any driver upgrades by hand to address any issues instantaneously that may come up.
Spil a miner expecting his/hier equipments to be running uninterrupted 24/7, relying on Windows to upgrade your movie card drivers is the last thing you want to toebijten .
This takes us to the 2nd policy that I like to configure, which is Do not include drivers with Windows Updates, spil shown ter the pic above.
Again when you very first open this policy it will be disabled. Simply select the enabled radio button and click on Apply/OK to set it. This policy is pretty straight-forward te that it does not have extra options and does basically what its title states, not to include drivers with updates.This is another case of enabling something to disable it, which can be confusing, but don’t think about it too hard.
Since wij earlier set the policy to notify us only for updates, this fresh policy simply keeps any drivers from appearing ter the list when wij are notified of updates. I should note that this will apply to all drivers and not just movie drivers, not that it would normally be an punt with a dedicated mining equipment, but I thought I would mention it anyway just so you are aware. After all, I know there a a few people who mine when not otherwise using there main pc, so te thesis types of cases it could cause an punt.
Also there is some discussion online that sometimes Microsoft will deem an update so significant that it will disregard the very first policy wij created altogether and apply certain critical patches anyway. So by enabling this 2nd policy it will also act spil a fail-safe ter case of that type of event. While I have not encountered this behavior personally, it is hard to tell when/if this could get enabled ter the future.
No auto-restart with logged on users for scheduled automatic updates installations
Lastly wij get to the final fail-safe policy, spil I like to think of it, which is to configure the No auto-restart with logged on users for scheduled automatic updates installations policy.
Again, there is not much to configure here except to enable the policy by checking the adequate radio button and then click on Apply/OK.
Now you can read through the description under the Help section yourself for the details of this policy, but basically this acts spil sort of a fail-safe spil I mentioned before te that if some update is forcefully applied, it will still require the user to restart the rekentuig rather than automatically doing so. This will help to prevent those Three AM reboots that oftentimes miners report spil experiencing and leaving there equipments unproductive until they notice it and can get around to fixing it. Assuming you have a user logged te, which I think te most cases would be true for most huis miners, by enabling this policy you will be asked before any reboots will toebijten.
Well there you have it. By making three ordinary policy switches you should greatly simplify your mining life if you have bot klapper by any of the nasty automatic update surprises. Feel free to configure all three or pick and choose which ones will work best for you. There is also a selection of other update policies you can review if you need further customization, but I have found by running thesis three I have had no automatic reboots on any of my equipments for overheen a year.
I do periodically login and will permit the update mechanism to do its work, but this way it is on my schedule and I can do it te conjunction with other routine maintenance instead of letting Windows determine for mij. It is all about taking back control.
I hope you loved this article and found some information that will be useful to you. Be sure to share any comments below.