Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Looks to be a powershell script running that's pulling CPU data every 20 seconds, I would hope that this is a testing bench mark tool used in house that got bundled into the update/release code accidentally, I hope. I would also hope it's hot fixed sooner rather than later..
I wouldn't be keen on renaming or removing powershell from your system32 as whilst it might fix this issue I suspect it'll end up causing your windows os further issues down the line.
Also the anti-virus is while annoying doing the right thing by flagging powershell being used and removing the game files again as annoying as that is... this game shouldn't be needing kernel level access
It may well have reduced the overhead on your cpu as the malwarebytes would have been blocking powershell requests from rivals, the requests will now be happening unimpeded which may well be impacting different processors differently, by this I mean not necessarily high end vs low end processors.