Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
General Security Discussions
(Meltdown and Spectre) Windows antivirus patch compatibility
Message
<blockquote data-quote="Deleted member 65228" data-source="post: 702915"><p>It's not because they don't know how to change a registry key. They can't just change the registry key, that would be extremely inappropriate, irresponsible and unacceptable. Some vendors did this, and then they caused all sorts of hassle for people who could update allegedly.</p><p></p><p>CrowdStrike need to make sure that their software works as intended after the recent patch, fix any issues into their code-base for support for after the update, and then they can change the registry key. Only, and not a second before, testing, testing and testing to make sure there are no problems.</p><p></p><p>Imagine a business using a solution of theirs, who updates because they changed the registry key without caring and doing proper checks. Now they get hit with a bunch of random BSODs and this crash causes data corruption on their system, potentially causing a lot of money being lost.</p><p></p><p>I don't understand what people expect here. A patch is released, vendors have hardly any days to prepare for the upcoming changes, all they were told in advance was that they needed to change a registry key. Security software can do all sorts of things depending on the functionality, both high and low level. Some solutions are built on millions of lines of code. They can't just magic out a fix for their software the same few days a patch is released out of thin air, it can take weeks or longer sometimes when big changes are made to built-in parts of Windows close to the software, in this case, the Windows Kernel itself being changed for various things.</p><p></p><p>Microsoft are to blame for this rubbish with AV products IMO. Microsoft should not have kept security vendors in the dark until it was too close. They should have notified the vendors at least a month in advance and let them know what exactly the changes were.</p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 702915"] It's not because they don't know how to change a registry key. They can't just change the registry key, that would be extremely inappropriate, irresponsible and unacceptable. Some vendors did this, and then they caused all sorts of hassle for people who could update allegedly. CrowdStrike need to make sure that their software works as intended after the recent patch, fix any issues into their code-base for support for after the update, and then they can change the registry key. Only, and not a second before, testing, testing and testing to make sure there are no problems. Imagine a business using a solution of theirs, who updates because they changed the registry key without caring and doing proper checks. Now they get hit with a bunch of random BSODs and this crash causes data corruption on their system, potentially causing a lot of money being lost. I don't understand what people expect here. A patch is released, vendors have hardly any days to prepare for the upcoming changes, all they were told in advance was that they needed to change a registry key. Security software can do all sorts of things depending on the functionality, both high and low level. Some solutions are built on millions of lines of code. They can't just magic out a fix for their software the same few days a patch is released out of thin air, it can take weeks or longer sometimes when big changes are made to built-in parts of Windows close to the software, in this case, the Windows Kernel itself being changed for various things. Microsoft are to blame for this rubbish with AV products IMO. Microsoft should not have kept security vendors in the dark until it was too close. They should have notified the vendors at least a month in advance and let them know what exactly the changes were. [/QUOTE]
Insert quotes…
Verification
Post reply
Top