http://s020.radikal.ru/i710/1310/58/6460089d2a94.jpg
http://i031.radikal.ru/1310/d4/ecd121410c70.jpg
Best answer by Rakanisheu Retired
View originalBest answer by Rakanisheu Retired
View originalMy experience was the same as you stated, showed up after the Win 8.1 upgrade. Good luck! Looking forward to seeing what you find!@ wrote:
Lucas has answered the Question and the issue only showed up on Win 8.1 x64 I didn't see any issues with Win 8 x64 and it continues with Win 8.1 Update 1 x64 so as Lucas said and Joe Microsoft must of added some extra protection with Win 8.1 x64 I will see if I can get any info I can share from my Microsoft MVP channels and hopefully they can point me to an article so wish me luck!
Daniel
Spot on Daniel, the finger points at something changing on the MS front between Win 8 and Win8.1, and if it is something fundemental then of course Webroot will be looking to react but it may not be a simple something to deal with, hence why time is being taken to get to the bottom of this.@ wrote:
Lucas has answered the Question and the issue only showed up on Win 8.1 x64 I didn't see any issues with Win 8 x64 and it continues with Win 8.1 Update 1 x64 so as Lucas said and Joe Microsoft must of added some extra protection with Win 8.1 x64 I will see if I can get any info I can share from my Microsoft MVP channels and hopefully they can point me to an article so wish me luck!
Daniel
I have not seen any other 64 bit processes (non Microsoft) being effected on my 64 bit system. Could you please provide details on these other 64 bit processes?@ wrote:
There seems to be some confusion with my post. Some here said that neither MBAE nor EAM seem to inject into explorer. That may be right but that was not what I was intending to say. WSA causes this memory behavior in many third party 64bit applications. Most people don't see it on Win 8.1 x64 because the only affected program for most is explorer. The other native 64 bit processes of Windows are probably not monitored by Webroot and hence there is no issue with them.
........ this seems to be an issue with 64 bit processes that are monitored by Webroot,
Welcome to the community AndersF!@ wrote:
Did anyone with this "problem" also get a message that physical RAM was low?
I've got 16 GB, but still the analyzer reports that physical RAM is low.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.