WSA Update v8.0.1.165

Auto-updated smoothly

 

Thanks Dermot and both the Closed Beta and Regular Users have been updated to this build!

TH

 

Sincerely hope to see either:

- Non-administrator access restrictions will no longer prevent a non-admin from changing System Cleaner user-specific settings

OR

- System Cleaner settings are now global and not user specific

The way it is right now is kinda silly. Admins can change their own settings but non-admins are forced to use defaults.

 

Man those guys are working hard and no slow down that I can see!

Here is the change log:

161 > 165

- Improved handling in some situations that can be caused by overzealous security software and infections
- Changed "Shut down Webroot" to "Shut down Webroot Protection" to clarify what it actually really does
- Fixed compatibility with Shadow Defender
- Fixed a general issue accessing network shares
- Fixed storing the last scan start time
- Fixed an issue with some corrupt file operations
- Fixed a rare issue caused by changing proxy settings
- Fixed a rare condition that would cause the user process to crash
- Fixed an issue handling some stray file read operations
- Improved performance accessing NAS
- Added approximately 14% more awesomeness
- Added clarification for cases where the user needs to reboot into Safe Mode with Networking rather than just Safe Mode
- Logs are flushed immediately in some cases for support enhancement
- Business Agent improvements
- Fixed some failover handling when things are broken
- Improved system service behavior on Windows XP Embedded
- Substantially improved behavior in cases where certain OS functions are completely missing
- Handled random zombie driver mob seen in one very exceptionally rare case


TH

 

Wonder what this really means.

 

I don't know but the person I get the info from is in the Q&A department and is a very nice guy and quite the character

TH

 

I was going to ask where you got the changelog from because I don't see it on the Webroot Community Forums. Unless I'm looking in the wrong place, of course.

 

I'm not sure if they will or not I always ask for a CL so that I can post updates on other sites to spread the word about the new WSA!

TH

 

I don't have a problem with that even if I don't know exactly what it means...

 

It has to be better by 14% than the .161 version at least that's really awesome!

TH

 

Hehehe...

I really am going to sound like a joy killer here because another great update is great news but I really wish these changelogs were just a tad more formal at this point and were done either in a formal sticky thread (instead of as multiple threads so it is easier to track development) OR as an official updated document on Webroot's site.

And I'm dying to know what the awesomeness is.

And why they aren't fixing the System Cleaner bug since they fix everything else in like an hour.

 

I have not been able to update, has the update been pulled out for some reason?

 

If past experience counts it usually takes a few days for 'everyone' to receive the updates I do not have .165 as yet either....

 

I have updated to 165 and it is now blocking Sandboxie from starting
No change to SB, have been running this version for several days so it has to be something in this update causing the problem.
I keep getting a warning from WSA but it's not showing up anywhere to submit as a False positive.
Anyone else seeing this problem?
WSA wants to run a scan to remove the 'infection' but if I let it do that and it removes SB I lose all my settings. I am not amused.

This is one of the WSA notifications, unable to capture the one from the task bar

 

If you are absolutely sure that it is a false positive you can run a scan again. After that uncheck the file WSA has labelled as infection and press continue. It will take you to another screen where you can set Allow for the file. After you have done this another scan will be triggered with clean result.
OR
You don't need to scan again, just go to PC Security -> Quarantine and under section View Quarantine or Detection configuration change the file to Allow.

 

Did all that before I posted. See new screen shots below - you will notice that "Start exe" which is the problem is now allow but WSA keeps over riding it and blocking SB from starting.

 

Bld .165 has now removed a Sandboxie driver and also mucked up the drivers on my download monitor.
Don't anyone ask for a scan log because WSA is no longer on my system.
I am now trying to repair the damage

 

Check for the file also in Protected Applications and Control Active Processes.

 

What heuristics settings are you using? I suspect you have it blocking every untrusted application, which would cause the behavior you're seeing. This isn't a FP - it just isn't whitelisted.

 

I have my heuristics all set to maximum but "apply before", not the "whitelist" option...

...we'll see what happens when it auto-updates me.

 

Heuristics are were set at high-med-med and warn if any untrusted program tries to run.
Those settings had been unchanged since at least bld 42 and there was no problem with Sandboxie previously. Nor with the Thinkbroadband meter.
Surely if those same versions of SB and the TBBmeter were trusted and whitelisted previously they should still be so if they hadn't changed at all (which they haven't). Come to that there have been plenty of updates to SB that WSA has accepted without a blink.

 

I'm really curious now. A quick Google search came back with nothing helpful. So where are the change logs for other security programs? I tried briefly to find them for Norton (Only had "change logs" that were really advertisement and marketing FUD), McAfee, AVG, Avast, Panda... Couldn't find them on casual investigation. So I wonder if we're lucky that we get any change logs at all.

 

Thanks for the changelog

I agree it would be nice if they posted official changelogs on their site.

Indeed, not many post them on easy to find places, though a lot post changelogs on their forums. Avast keeps one updated on their main site btw:
http://www.avast.com/release-history

 

Those Avast logs aren't nearly as detailed. I found Norton "Change Logs" at one place which look more like an advertisement than tech change logs.

Do we really want "formal" change logs that are very vague or advertisement-like?

 

Hey guys I go out of my way to ask for change logs because we like to see the details but they don't need to supply me one at all so it will stay as it is and there will not be any sticky for CL's! I just want you to know that some Webroot Employees do look at this forum and they are kind enough to give me detailed change logs so please don't complain or these are the kind of logs I will get from now on! And I agree with Techfox1976 that we don't want vague Formal changelogs!

Formal changelog:
- Improved performance in several corner cases
- Improved compatibility with several third party applications
- Corrected some extremely rare crash cases
- Changed some wording for clarity

Thanks,

TH