Just checking if anyone else has noticed or effected by this.
I'm still using kaspersky based aol anti-virus shield it had been working and updating fine since they change to mcafee though my signatures i've noticed are set at 8/31/2007 and when i try running update it goes "update is not required"
Is this all normal behavior ? or has aol officially slashed kaspersky based updates and i need to move to something else cause damned if i'm touching mcafee again :|
Finding it funny that MS is urging IT admins as if this was a big, significant update. No new features, just an enablement package that will bump up the build number again, which is a shame considering 22H2 and 24H2 were significant updates. Technically, 25H2, 26H1, and the upcoming 26H2 are all the same with different support schedules.
The era of Windows being in the backburner continues, and this 26H2 update feels like an afterthought.
After I installed those, my older but capable Win 11 laptop (16GB RAM) reported it as 26H2 26300.8697.
Then I installed it on my big laptop (128GB RAM! Hehe sorry), it reported it as 25H2 26220.8690. Ugh. Do I have to switch Insiders channels from Release to Beta?
Question
Digitalx
Just checking if anyone else has noticed or effected by this.
I'm still using kaspersky based aol anti-virus shield it had been working and updating fine since they change to mcafee though my signatures i've noticed are set at 8/31/2007 and when i try running update it goes "update is not required"
Is this all normal behavior ? or has aol officially slashed kaspersky based updates and i need to move to something else cause damned if i'm touching mcafee again :|
Link to comment
https://www.neowin.net/forum/topic/585299-aol-killed-kaspersky-avs-updates/Share on other sites
18 answers to this question
Recommended Posts