hat
Enthusiast
- Joined
- Nov 20, 2006
- Messages
- 21,731 (3.42/day)
- Location
- Ohio
System Name | Starlifter :: Dragonfly |
---|---|
Processor | i7 2600k 4.4GHz :: i5 10400 |
Motherboard | ASUS P8P67 Pro :: ASUS Prime H570-Plus |
Cooling | Cryorig M9 :: Stock |
Memory | 4x4GB DDR3 2133 :: 2x8GB DDR4 2400 |
Video Card(s) | PNY GTX1070 :: Integrated UHD 630 |
Storage | Crucial MX500 1TB, 2x1TB Seagate RAID 0 :: Mushkin Enhanced 60GB SSD, 3x4TB Seagate HDD RAID5 |
Display(s) | Onn 165hz 1080p :: Acer 1080p |
Case | Antec SOHO 1030B :: Old White Full Tower |
Audio Device(s) | Creative X-Fi Titanium Fatal1ty Pro - Bose Companion 2 Series III :: None |
Power Supply | FSP Hydro GE 550w :: EVGA Supernova 550 |
Software | Windows 10 Pro - Plex Server on Dragonfly |
Benchmark Scores | >9000 |
Many have, myself included. It is ignored because miners are often bundled with malware.
My report got a nice "won't fix/not an issue" tag.
Which is fine for 99% of consumers honestly. The issue is Windows Defender not STAYING OFF.
Exactly. You want to include WD by default, and also have it enabled by default? Fine, that works for most users. You want to detect miners as malware? Also fine, they are malware for most users, and those that are using them legitimately also know that it can be added to exclusions anyway. Someone disabled WD (in the group policy editor, no less) and also chooses not to run any other AV software, so you bring it back from the dead? Not fine, quit screwing with me.
By the way, I repeatedly mention the group policy editor for two reasons. First and foremost, because it's the way I disabled WD. Secondly, because it's a bit unusual, isn't it? Maybe not for users like us on this forum, but for people in general. How many people out there even know about gpedit.msc? First off, I would suspect most people are probably running Windows 10 Home, which doesn't even have the group policy editor. Secondly, for those that are using the group policy editor, those people should be advanced users who know what they're doing. You don't accidentally wander into the group policy editor and fuck shit up. Why would you mess with those settings, or, in this case, ignore them? I think WD should have a simple on/off switch that either turns it ON or OFF, forever, until changed again by the user, but barring that, there's at least a weird roundabout way to disable it by accessing the group policy editor, which is for advanced users who know what they're doing, on the non-standard (professional) version of Windows... why would you mess with that?
Being optimistic, I can only hope this was some sort of bug that resulted from the nasty rollover that occurs when you install/upgrade one instance of Windows on top of another. As we know, at least in the past, this process is not perfect, and a clean, fresh installation has always been recommended, just to prevent, or cure, weird things that can happen. Being realistic, when Microsoft literally forces this process twice a year with these feature updates, those things shouldn't happen. That means I'd have to perform a clean reinstallation Windows from scratch twice a year, just to prevent any fuckery that might occur due to these crappy rollover upgrades. Being, erm, the guy who uses my own personal computer, Microsoft really annoys me the way they try to force their way on you. Windows Update has gone to hell, between forcing updates (you can only delay them for so long), forcing ALL updates (you can no longer pick and choose which updates you do and do not want), and even forcing driver updates, which have been known to mess with computers by installing some crappy driver that was worse than the one that was already installed. For that last one, there is a setting, in a strange place, that's supposed to prevent driver updates, but that's also been reported to, well, not work. On top of that, you never know when something you changed might suddenly be reset without your knowledge.
At least all Windows 8 had was a crappy UI that could be fixed by installing a simple utility...