What does that even mean..? An "advanced user" may use automatic updates to save time, so they can get on and do something productive.
An advanced user, will look at the updates, research them for possible issues, verify updates and apply them as needed.
In a Pros and Cons shared system, not taking the time to do this could cost a user more time. Installing an update that causes issues or incompatibilities to find out after installation by someone sharing the system with you, and having to hunt down, find and fix issues, can also be very time consuming, if not more so then delaying an update long enough to research it. So really, i would state it is dependent upon set up and uses of system. How many updates have MS pushed, that had to be rolled back, or simply left many users with serious issues. Patched systems are a must to avoid potential exploitable avenues, but sometimes those patches are worse then what they are patching.
Just do like the genius users, use Rollback RX
Am i to assume i would not have issues with Rollback RX and updates/upgrades of windows OS, or would i have to as in the past, uninstall RX every time a major change comes along, because this would also be time consuming, and not really geniusJust do like the genius users, use Rollback RX
Installing/removing RX takes 2mn, and you do it only when a new Windows build is released every 6 months, anyway in such case good practice suggest a clean install. So it doesn't matter.Am i to assume i would not have issues with Rollback RX and updates/upgrades of windows OS, or would i have to as in the past, uninstall RX every time a major change comes along, because this would also be time consuming, and not really genius
I managed to find one of those little hiccups once with RX, that transitioned into a full wipe of the drive and reformat, RX while handy in some cases, has never been completely issue free. Myself, i clean install my Host every major iteration of W10, and do all my testing in a contained Virtual machine so as to not effect my Host in any way, even keep my Guest machines stored on a separate partition, for main drive maintenance without issue, and makes a clean install of the main without loosing saved work in guest machines quite efficiently as well..
It all balances out, pros and cons to both, it really is just a matter of preference.. I tend to set my guest machines up as close to a normal system as possible, including items like older framework ect. I like being able to keep my testing contained from effecting my main system no matter what, so daily tasks are never interfered with. My significant other, well, she 2nd's this, with one of those looks like i better keep em separated "song just flashed through my head lol"...
A solid and light configuration there my friend. I too use EIS. I will have to take a lot at the SysInspector. While I do not have any doubt over the detection and removal capabilities of ESET, I do wish ESET had some more prevention features which Kaspersky Internet Security has like the System Watcher and the Application Control because I believe that Prevention is Better than Cure. One thing you could keep is the free version of Malwarebytes as an on-demand scanner and use it to scan once a week in case ESET misses anything(although I highly doubt that it will miss any) and since you know what you are doing with your computer, you yourself are the best defence
