{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/22/2023 5:52:02 PM
3
An actual human at Battleye responded to my email! There may be hope after all (although I am not holding my breath)...
=email reply=
Thanks for your additional report, we are aware of that. This merely affects certain old versions of our driver though, not current ones.
The actual issue was related to a Microsoft update this week, which we have since addressed in our FAQ at the very top.
=email end=
As indicated, they have updated their FAQ since my contact. In part it reads:
"While we are working on finding a solution and are also in contact with Microsoft regarding this issue, unfortunately there is no easy or immediate fix for it."
Quote from:
https://www.battleye.com/support/faq/
Which is why I am not holding my breath.
They actually appear to be working on a fix.
Why we should be forced to lower our system security until this is accomplished is still an open question. Now... who to pester about this issue... ???
English
-
Hi there! As noted in the BattlEye FAQ, they are aware of this issue and they are working with Microsoft on it further. You will need to continue to monitor the BattlEye FAQ for updates on this issue. Also, please note that as mentioned in the article, there is no risk to your system. [quote] Please note that by doing so you will not lower the security of your device or expose it to greater risks compared to previously, as this is a new security feature that wasn’t enabled on devices before.[/quote] [url=https://www.battleye.com/support/faq/]Source: BattlEye FAQ[/url] If you have any additional questions or concerns, please reach back out to BattlEye Support.
-
Edited by Nesh: 4/27/2023 2:32:59 AM[quote]Also, please note that as mentioned in the article, there is no risk to your system.[/quote] This is not just irresponsible but plainly dangerous comment. If you are [i]not[/i] experienced (windows) security expert [b]DO NOT ever disable any security feature in your OS just because some POS spyware say it so.[/b] BE like any other vendor, has access to Win11 updates months/years before release and [b]they[/b] choose to not address it (as many other kernel level vendors already did).
-
if you're going to take the word of battleye saying there's no risk because your system ran this way before the latest update... well good for you. i wouldn't take the word of a negligent company that's ignored this for almost a year and haven't worked on compatibility. the presumption on battleye's part in their FAQ, who have no idea of the compatibility impact of rolling back a kernel driver when it comes to the other software on your pc, is kind of rude to their users tbh. to me, it's a huge red flag for a company to come out and say that. plus they're trying to play it off as microsoft's fault saying "we were just recently told this was happening" when that's a load of crap. they've had over a year's notice b/c microsoft put out a bulletin with guidance for game developers wrt how to handle this update in their code even. they went to great lengths to communicate this b/c they have to. this feature's been on computers for at least 2 years now.
