Solved

Explorer.exe using up to 300mb RAM.



Show first post

365 replies

Userlevel 7
Badge +56
I reported it to the Microsoft Community Support Forums and it seams this KB3000850 has broken Avast but fixed it for us: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/major-issues-with-kb3000850/5cb4cddd-52da-44af-9fd5-3ae1a72b0b1a?page=5&tm=1417020252172#LastReply
 
Cheers,
 
Daniel 😉
Userlevel 7
Badge +56
Your very Welcome! I think @  has allot on his plate ATM till the end of the year maybe he will stop by and say hello!
 
Thanks,
 
Daniel 😉
Userlevel 4
Badge +17
Dear Triple Helix
Thank you very much..
Is Baldrick Around ?? Did not hear from him for a while ???
Userlevel 7
Badge +56
@ wrote:
I have a question please:
Inside my Computer: C-Program Files- Webroot. There is a folder called WRData, and There is an Green Icon Called WRSA.
So technically do I have to renames this or not ??
Thanks
No don't do anything in there as it's needed as that's where the processes run from!
 
Thanks,
 
Daniel ;)
 


 
 
 

Userlevel 7
Badge +56
@dtouch wrote:
I just noticed the optional update in windows update and did it. And yes it seems to have reduced the memory used.
Awesome so KB300850 fix this long time issue ever since they release Windows 8.1 x64 as Windows 8 x64 never had that issue before 8.1!
 
Thanks,
 
Daniel 😃
Userlevel 7
Badge +56
@ wrote:
I also, updated that window update, and I notice my Explorer is using around 48 MB
Thanks
Excellent it's been said since Win 8.1 x64 came out it was never WSA's fault now Microsoft have to add this fix to the new Win 10 Preview x64 hopefully by the release of it!
 
Thanks,
 
Daniel 😉
Userlevel 4
Badge +17
I also, updated that window update, and I notice my Explorer is using around 48 MB
Thanks
Userlevel 6
Badge +24
I just noticed the optional update in windows update and did it. And yes it seems to have reduced the memory used.
Userlevel 4
Badge +17
I have a question please:
Inside my Computer: C-Program Files- Webroot. There is a folder called WRData, and There is an Green Icon Called WRSA.
So technically do I have to renames this or not ??
Thanks
Userlevel 6
Badge +24
I will try that TH
Userlevel 7
Badge +56
@dtouch wrote:
My windows 8.1x64 is fully updated. But still  explorer takes 300mb+
Did you install this Optional Update from Windows Update also check to see if you have it installed? KB3000850 http://support.microsoft.com/kb/3000850
 
Thanks,
 
Daniel 😉
Userlevel 6
Badge +24
My windows 8.1x64 is fully updated. But still  explorer takes 300mb+
Userlevel 7
Badge +56
@ wrote:
@ wrote:
Also on Windows 10 Preview x64 Latest Build 9879 still has this issue.
 
Daniel
 
 
 
 
Well, that is a bit odd I would think.... though being in a trial build they may not have did whatever to it that they did in the Win8.1 Patch I guess?
 
Actually Win 8.1 Pro Update 2 x64 and this November's patch Tuesday KB3000850 http://support.microsoft.com/kb/3000850
 
Daniel
Userlevel 7
@ wrote:
Also on Windows 10 Preview x64 Latest Build 9879 still has this issue.
 
Daniel
 
 
 
 
Well, that is a bit odd I would think.... though being in a trial build they may not have did whatever to it that they did in the Win8.1 Patch I guess?
 
Userlevel 7
Badge +56
Also on Windows 10 Preview x64 Latest Build 9879 still has this issue.
 
Daniel
 

Userlevel 7
That is a pretty darn big change!
Userlevel 7
Badge +56
I can confirm as well as I just updated my Win 8.1 Pro x64 but I'm not sure it's because of the update KB3000850? But see it was the way Windows was handleing WRSA.exe and Windows Explorer very interesting!
 
Thanks,
 
Daniel ;)
 


 
 


 
Greetings community.
 
I think since the release of the KB3000850 update this infamous bug seems to be resolved, or at least in my case. It looks like something on Microsoft's end has changed. I have not been able to reproduce this bug since. Explorer is back to normal and other 64-bit applications, which are injected with wrusr.dll, are no longer affected as well.
 
Great news.
Userlevel 5
Badge +16
The issue of 'C:Program' is related to Webroot, but unrelated to the 300MB Memory issue in this thread.
The issue of C:Program is a truncated WRSA install, that while running, isn't quite running correctly. To resolve it:
If WRSA is running from Program files, uninstall it, and reboot
Rename the file to C:Program.exe
From a CMD line run: C:Program.exe -showgui
You'll see the WRSA UI
From a CMD line run C:Program.exe -uninstall
Follow the uninstall prompts, and reboot
If this doesn't work, please let me know via a PM your email address via so that I can track your case down and we can setup a remote session.

Thanks,
Lucas Moore
@ 
@ 
 
Thank you both providing useful suggestions and yes, I have putting in tickets with the poor Support Techs on and off since the begining of September.  They are working on it and have been great, as I have said, no problem with customer satifaction on that end.  
 
Photoshop, ohhh yes, can suck the life out of your system 😉 which is why I finally splurged and gave myself the.gift of this computer a few months ago, I am trying to teach myself 3D graphic design and loving it, woohoo!!!  The problems only occurring since the WR update last month :(
 
They did collect a log when the first issue began and it worked like a charm, so maybe that needs to be done again, will see what they say on Monday.
 
Thanks to all those who have had to read through my rants and those who have tried to offer help!!
 
Slowly backs out of the discussion....
Userlevel 7
Badge +13
If anyone is subscribing to Adobe Cloud,i can see the need for maybe whitelistening components,as there are a great many apps downloadable,each with a great many processes that are all regularly updated,and aren't always known to the cloud.I will say,however,that Webroot doesn't take very long in getting files classified G(good) should you play the wait game and not open a ticket.Frequently when doing web design/development,there will be a need to have many Adobe apps open at once,I've done it,my wife is in school for web design/development,and i can say firsthand they can have a significant system impact.Even with several apps open at any given time,i have not had a single issue with Webroot.Even with explorer.exe showing high ram usage,it's just does not  affect system performance in any way whatsoever on my win 7 x64 machine or win 8.1 x64 machine.Even running some ram hungry MMO type games,i have not confronted a single issue where explorer's ram usage showing 300+ megs would affect performance in any way.I have shutdown webroot and run games and software,and have enabled Webroot and ran software,and have seen no difference in performance.Not ever.The only thing i have ever seen affect the performance of any software on the system is when a file is new to the cloud(U),and as a security measure i'm fine with that.It's better to be safe than sorry.It usually won't take long to get those files classified good,but it surely doesn't hurt opening a ticket and getting the ball rolling.
Userlevel 7
@   Sorry not to be able to help, and I wanted to stress that there wasn't an incompatibility per se. Which doesn't mean that individual issues cannot occur..
My guess would be that some files on your system probably need whitelisting, which would show up in logs. You didn't say if any whitelisting or log collection was done.
Although I don't use it, I'd imagine Photoshop uses a lot of resources?  Optimize performance | Photoshop CS4, CS5, CS6, CC
 
The issue you're seeing is surely a matter for individual support, as already advised.   Submit a Support Ticket
LOL, I did read that, it was what I was replying to.  You guys are too funny, ok, ok, I give up, there's nothing wrong, no compatibility issues, they work perfectly together, which would also mean, there is no MS faulty coding issue 🙂 again, no blame guys and definitely commend the loyalty of the group!!
 
Anyway, this wasn't the major concern of my issue, just another thing that came up when running WR tools after the c:program file name warning came up and I did, as always submit a support ticket, which I mentioned a few times here 🙂 it worked for a day and now is coming about the suggested rename from support....
 
Over and out, you win, I'm done :)
 
Userlevel 7
 
Hello gambs. Firstly, you can be absolutely assured that there is no actual incompatibility between the two softwares, and SecureAnywhere is protecting your Windows 8.1 system at the deepest possible level, maintaining complete integrity. It shouldn't affect anyone with sufficient RAM. They will fix it for sure, but it isn't of the highest priority, since there are no serious issues evident.
 
I'd ask you to go back and consider fully some postings by JoeJ and  TechToc.
 
Specifically these may help:
        "Ultimately this issue isn't one with WSA, it is one where Microsoft has coded in a fault tolerance limit for Explorer (or other processes) to prevent crashing. The additional memory usage (mostly reservered and not written by the way) is just a way to ensure your shell doesn't crash when something goes wrong." (page 27)
       "The behavior of Explorer is a result of Microsoft building fault tolerance into their software to prevent against crashes. This IS a good thing. It increases the overall stability of the operating system.
While we can control what we do, we have no control over what Microsoft chooses to do as a result. The Explorer process detects the inclusion of a non-Microsoft injected DLL and adds some additional buffers in place in the event that DLL causes a shell crash." (page 30) 
   "the higher Explorer RAM is allocated by Windows in such a way that it will not impact system performance in any measurable or noticeable capacity. If you're experiencing any system performance degradation, I suggest writing into our support team so that they can inspect your logs and correct the issue." (page 5)
 
Thank you for the reply, I genuinely appreciate getting additional knowledge and background info on anything.
 
Let me reiterate, I really am not looking to fault Webroot, their products or point a finger in either direction regarding why or where the issues stem from.  As a consumer I just want the product to work, point blank.  I don't want warnings popping up at all but since I don't live in a perfect world, stuff happens.
 
A bit more history....
 
I looked into properties, saw the file in question belonged to WR, naturally I contacted WR for advise and a resolution.   When I was logged on with a Geek Squad Tech, he repeatedly told me this was not from WR, was not covered and I would need to sign up for an additional membership with them to have my system checked.  During the remote session I showed him the file (which he was unable to locate), the properties and stated that I did indeed feel it was.  He didn't agree. I thanked him, put in an additional request regarding that session and sent a message to Webroot directly.  The Webroot Support Team, who really provide excellent customer service, on a scale of 1 to 5, they'd get a 10, absolutely no complaints regarding their speed of return reply and suggested resolutions.  That applies to this and the issue earlier in the month with the WR Upgrade that caused havoc on my system, I feel that was the start of these issues.  
 
Honestly, I don't, nor should I be expected to care one way or the other where the fault lies or the reasons why there is a problem, that doesn't resolve my computer issues.  
 
WR did get back to me right away, suggested the rename and reinstall of WRSA.  It worked great for a day. Now I have an additional file name warning but it's for the renamed file of c:program.exe, am I to rename and reinstall WR daily?  
 
From my perspective, yes, only my perspective
 
I have two products...
 
- Product A (computer with Windows 8.1, 64bit OS)
- Product B (Webroot)
 
from what I've read here...Product B states they are working on a fix to the ongoing issue that has been caused by Product A.  
I don't think Product A is going to adapt to accommodate Product B anytime soon.  So, the fix then falls onto Product B if they want to be considered as a viable component for use with Product A.  If they cannot fix it, there is a problem at this present time and therefore they are not completely compatible, simple math, it a yes or no, without explanation of where it initiated from.
 
We cannot eliminate Product A and am sure WR is doing what they can to resolve it.  However, in the meantime, at minimum it would be appropriate to state there "could" be compatibility issues running the application on this system.  It's documented here that at this time WR cannot resolve.
 
Sorry for my very long winded reply but I am getting frustrated and concerned about system integrity due to the ongoing issues.  
 
Thanks

Reply