That doesn’t answer his/her question. 
There’s only one beta at a time, so there basically is no other choice than the latest one. 
We’re getting off topic but that isn’t the users question. Allow Avast to answer his question.
Jiří Šembera already answered him and asked to test the beta, see Reply #14…!!
Jiri didn’t answer his latest question.
Nope, but I did.
The question was, Does the beta specifically address the users problem or, is the user supposed to try the beta and see
if it may solve his problem.
I can’t find your answer to that question. I can’t answer the question only Avast can.
Bob, feel free to PM me. No need to clutter up this thread with our chit chat.
The only chit chat is your insistence on not allowing Avast to answer the users concern.
I believe his question wasn’t addressed at either of us but at Jiri.
See Reply #14.
I installed the most recent beta. Another quick question, just to make sure: Would a shut down instead of a restart be just as valid? Or does it need the actual reboot call?
Both will work.
Thank you. I thought as much but wanted to make sure. The boot time for this machine is fairly long so wrapping up this session as normal and letting the installation finish up tomorrow is ideal.
I will post results in the coming days as they manifest.
You’re welcome.
Certain changes in Windows only take effect if you use the restart.
Unless you’ve turned the Quick Start function off in Windows, a shutdown may not be sufficient.
Day one, already a crash.
Would the avast staff like the crash log?
Yes please upload *.mdmp file to our ftp i will take a look.
Thank you.
Uploaded under the filename “Greatfox422_5_2019.zip”
As a side-note, both on boot and after I did a restart of this machine, I noticed the Avast installer suddenly taking up power. I’m not sure why; maybe it’s a delayed virus definition update since the days match but not the times (even if the computer was running during the noted time), though I’m not sure how that works or if this is worth being concerned about.
Okay I think I can confirm that this shouldn’t be happening. IT just did it again half an hour after boot, despite no further updates being displayed.
I worry if this might not be causing damage to the harddrive.