Should 3.1.1.1722 Beta Have Auto-Upgraded to 3.1.2.1733 Release?

[NoelC]

I ask because it didn't; I kind of expected it to do so.

Do betas update themselves to other betas, or just not at all?

I'm actually awaiting the release of a fix where the service doesn't get into a state where it gets stuck on exit after having done a root kit scan.  What strategy should I take in order to be aware of when that is fixed (presuming it isn't in 3.1.2.1733)?

I'd like to be a beta tester; is there a way to join a program?

-Noel

[NoelC]

Update:

With 3.1.2.1733 after having done a manual Threat Scan, then gracefully quitting from the Tray icon, the service still hangs around, but crashes out and restarts after a short time.  Then closing it via the Tray icon AGAIN causes the service to exit along with the tray executable.

-Noel

[dcollins]

@NoelC the update from 3.1.1.1722 to 3.1.2.1733 will happen eventually, but updates are given out in a lottery type format (IE: We choose X computers each hour/day/etc to get upgraded). If you want the update sooner, you can download and install it manually.

If you're experiencing an issue with 1722, I would recommend upgrading to 1733 and verifying if your issue still exists. If it does, please let us know so we can continue researching it.

[NoelC]

Thanks.  Our posts crossed in the wire I guess.  It does still happen in 1733, though the hang turned into this:

-Noel