While the Windows 10 Creators' Update isn't officially rolling out until
April 11, Microsoft has released it early via their Windows Update
Assistant Tool for those brave souls who just can't wait until April 11
to install it. I'm not sure if I'm a brave soul or just a foolish and
impatient one but I decided to install the update this morning. I had a
few hiccups which were eventually solved. However, one thing that I
noticed was that Windows Defender, now wrapped up in something called
the Windows Defender Security Center, was enabled. As I'd prefer that
Kaspersky protect my system I disabled WDSc but then I was warned that I
had no antivirus program protecting my system. Confused, I checked
Kaspersky and it did seem to be fully enabled. I even tested it by
downloading Eicar, which is, essentially, a fake antivirus program, a
program which is not truly a virus but which makes your antivirus
program think it's an infected file, which you can freely try by going
to www.eicar.org.
Anyway, Kaspersky picked it up and seemed very active, but the Creators
Update doesn't actually see it as a valid antivirus program. Once I
turned off WDSC, restarting my computer turns it right back on again,
since Windows thinks that I have no protection and so it starts WDSC up
as a default. I have mixed feelings about this oddity. I acknowledge
that I'm running the Creators Update of Windows 10 before Microsoft
really intends the general public to use it, although if they really
felt that way they shouldn't release it publicly in the first place.
However, one could argue in Kaspersky's favor that they can't be held
responsible for not fully working with an update which isn't even
officially out yet and I have a small bit of agreement with this. On the
other hand, the Creators Update has been out for a while for Windows
insiders and I can't help but wonder, considering this, why it's
actually taken Kaspersky this long to fix this. Then again, I know that
code can change overnight and perhaps Creators introduced something at
the last minute which caused it not to play nice with Kaspersky.
I did some research and came up with the following article from
Kaspersky's support site. As I recall, Kaspersky had similar issues when
Windows 10 was first released. Here's the article.
Limitations in Kaspersky Anti-Virus 2017 after upgrade to Windows 10
Creators Update (Redstone 2)
Back to "Windows 10 support"
2017 Mar 20 ID: 12931
If you upgrade to Windows 10 or install Kaspersky Anti-Virus 2017 on
Windows 10 Creators Update (Redstone 2), at the first startup Kaspersky
Anti-Virus 2017 will run the adaptation process. During this process,
protection will be paused: only File Anti-Virus and Self-Defense of
files and registry will be functioning. The interface will be
temporarily unavailable.
After the process has been completed, protection will resume, but the
following component may work with limitations if the drivers do not
support Windows 10:
• Self-Defense of the product UI and protection of the product's
processes at their startup.
• System Watcher.
• Detection and disinfection of malware in the system memory.
• Protection against cryptolockers and ransomware.
• Protection against the attacks of the type Time-of-Check Time-of-Use
(TOCTOU).
Microsoft Edge does not support the On-Screen Keyboard and the Kaspersky
Protection extension in Kaspersky Lab products.
