WSA v8.0.2.109

New version out and a change log will follow ASAP. I just assuming it corrects the BSOD issue on Windows XP.

TH

 

If you are running the closed beta versions, it appears this version has not been released to the closed beta channel, so if you want it you will probably have to download the regular version and do a manual install.

 

True as I checked both Download links!

TH

 

We haven't yet released this over the closed beta download link but the only fix is related to Windows XP's latest update, so you won't be missing any new functionality.

 

Change log

Version 8.0.2.109 (Released February 13th, 2013)

Improved

• Compatibility with new Windows XP Updates

TH

 

Is the beta version also going to be updated today or tomorrow (BSOD fix)? - Or should people which are using right now the beta version really do install the live version if they are in fear of BSOD's on WinXP? - So isn't the current v8.0.2.105 beta "cloud fixed" yet? Will users with this .105 beta version still probably have a blue screen event? Or is it safe now even with this .105 beta release?

p.s.: I do wonder why there is a change in the client (necessary), I always thought such things would be fixed behind the curtain, high up in the cloud?

 

Hello Webroot?

Anyone at home? I saw you guys online minutes ago?

I would really like to have an official answer on that. Is the beta version .105 safe now regarding the blue screen on XP? - Or is .109 mandatory in this case?

TIA!

 

The fix required a software change so it will need to be updated to 109. You may want to just move off of the beta build for the time being (by just running the new live release build).

 

That isn't always indicative of me actually being online I usually have Wilders open in multiple tabs on multiple devices

 

So the .109 build is just for the BSOD on Windows XP? Seeing some workstations updating here at work.

Thanks.

 

Thank you for that important information! - I will do that on the XP system I have to do maintenance on. - First installing the new .109 over the beta version and then maybe rebooting. And after all that I will try to be very brave .. installing the latest MS updates.

I understand. So one could say then you are quite addicted too. - Good feeling not being alone (just using one device though) ..

 

Yes (it also includes the changes in 105 which are much more globally relevant).

 

JFYI - all went fine after upgrading to 109 ... a quick reboot .. and recent MS updates weren't rejected but welcomed on the XP system .. totally without blue screen / loud scream! - Just a small sigh when I heard the good news from a distance. - After all with blue screens it can get impossible to do remote-maintenance and I really didn't feel like traveling today.

 

Glad to hear it! This ended up being less of an issue than we feared it might turn into but we made sure we got on top of it very quickly anyway.

 

yup all fixed here got the boot loop fixed and installed 109 and all is good..

 

Hello,

Maybe it is just me, but the handling of this update definitely lowers my confidence level in Webroot. The windows update issue was serious enough where Joe even advised users on XP to hold off on updating on XP for the time being. Then when a solution was found, the update was NOT pushed out to all users. I am sure that several closed beta users were on XP as I know 3 personally (not to mention my laptop). I would have thought that this update was critical enough (BSOD's when windows updates on XP) that all users should have received it. Instead the closed beta users were completely shut off from this update and by doing so several users have encountered major issues. Not all that participate in the closed beta visit here at Wilders every day. I am really disappointed that this update was not pushed put to ALL users as it was critical. My confidence in Webroot now has and will suffer for this decision. Closed beta users deserve the same protection and respect as the normal update channel. Instead they must jump through hoops by watching the threads here, manually downloading and installing the new version when and if they learn of it, and then, if they want to continue as a closed beta tester, watching the threads here again for a new beta to be released, and manually downloading and installing once again. IMHO it was a huge mistake for Webroot not to push this critical update out to ALL users. Webroot has now shaken my confidence that they are still providing the absolute best and safest protection to me. I am quite disappointed.....

 

I couldn't get 105 to cause a problem on XP VM testing after the change in cloud determination without pulling the network "cable" from the VM after downloading the updates and before they started installing. The 109 fix corrects that case as well.

 

My diminished confidence level in Webroot stems from the past practices of always updating the closed beta channel to the newest version once there is no beta version. For some reason, Webroot made the decision NOT to upgrade the beta channel to 109 but only the normal channel. This caused the potential for BSOD issues/windows update problems to the closed beta users that have XP. I do not see why such a decision would be made to leave the closed beta channel users exposed to this issue. It has caused my daughter serious issues at school that I am still in the process of remedying.

 

I understand your concern but as the issue was determined to only occur on a single reboot right on the update, and we have had zero other reports, we chose to just not publish it out to some download locations, the closed beta link being one of these, because of other testing which is currently taking place on the closed beta download link which needs to remain exactly on 105 for the time being. I suspect any issues your daughter is having are unrelated to WSA at this point, but in any case, I strongly urge you to not have early beta software running on live machines like this.

You can always run the new build manually to upgrade over, but this issue shouldn't be causing any residual problems now or after you've finished updating. Our initial assumptions of the issue were overly cautious as we thought the scope would be wider, but it turned out to be more limited.

Again, the closed beta link should not be used on production machines - we roll out new functionality much faster to it in the assumption that it will be used exclusively under testing scenarios to the select group of only about a thousand highly technical external users, and if users are using it on live machines, we may need to reassess how we send out the updates.

In the meantime, I strongly suggest manually running the wsainstall.exe 109 build over it on any non-test machines to prevent the possibility of instability in the future.

 

what happened in my case is the win xp file was set to block for some reason. and since i could not get in to change it i got the boot loop. i ended up temporarily using an older version of the file and copying it into win xp the on the next reboot i could boot up and update wsa and then run the xp update again to add the newer version. this was the only machine i saw this on which was weird. but wasnt to much trouble to fix it. and i did not received any other calls about it from any clients i only have maybe 25 clients with wsa on xp most are on win 7. so i would say it was fixed pretty quickly

 

But IIRC In the past there were quite often situations when a "live" (non-beta) version was released and newer than the current beta version for a certain amount of time. And beta people weren't upgraded to that live version. - I don't understand this either (and also not why certain versions aren't beta-tested as it seems?) but if I understood Joe correctly in his posting above they do keep beta testers on purpose on "old" versions to test certain things a while longer?

I can live with all that because I like always to have the newest code (on my only = "production" machine and it's MY risk doing that!) and sometimes .. well .. either I have to wait or I have to switch to the live version for a few days.

I am happy to be in that beta group from the beginning and so far (using Win7) I had NEVER any severe problem let alone really big ones like those BSOD's mentioned here.

I did install the beta version on a system of a relative just to test immediately the @@-bugfix there (worked!) and then recently the BSOD topic started. But luckily in my case MS updates weren't installing automatic, so no harm done. That mentioned XP system is now back on live version of course as it should be. - But I am not installing live versions here on my Win7 system. It has to be the newest beta. No risk, no fun! - I will patiently wait for the next release.

 

It depends on exactly what we're looking for feedback/testing on. Sometimes builds won't need a beta phase as we've tested the reproducible issues and we trust the changes going out, and other times we'll want it to be tested by the closed beta group for a while before it goes out further. In other cases, we have the closed beta on an older version number because of other external testing which is ongoing or because we still want feedback on the slightly older set of code.

If there's anything which was urgent enough to warrant a global update, we would of course push it out everywhere. We have 50+ different download locations and spread releases out between them depending on severity/demand/individual testing.

 

Thanks for taking the time to make your reasons clear!

Well ... that must be pretty complicated to have an overview over 50 DL locations!

If there is a possibility got get an even earlier (newer) beta (not alpha) build just let me know and I will run that with the closed beta key and report things.

 

It's not affected my confidence in WSA. For example yesterday Mbam pushed out a sig update that quarantined all my active uninstallers & more which caused quite a few people a lot of hassle & lots of phone calls, but these things happen & always will. Will I stop using Mbam? Of course not - Also never run beta software on any PC that's critical.

The best protection of all is to have regular full C:\ images on all your PC's, you are pretty well covered then, it's never let me down.