Thanks Milos and the Avast teams for the temporal bypass via the geek:area, yet i do have a question on this regard.
Since you started with a “for now” in your answer, does it means that the avast teams are working on a fix to be implemented in a near future to solve the problem ?
Also, on a side note, it appears that another question brought by [chris…] in regard of the availability of the geek:area, since it appears that he do not have the ability to access the geek:area in his Avast application on his Windows 7 computer. (A problem which may perhaps need a topic of its own, a suggestion i will make to him on a private message.)
Edit : Personally, i do have access to the geek:area and spotted, like shown, the option for the WindowsRE scan. (When i do have some more time, i will try to do a boot scan to see how it work. Unless a more reliable fix is released in the meantime, of course^^.)
Again, i thanks all who participate on the subject of the topic and i thanks the developpers for the hard work they do in order to improve Avast.
a small adjustment:
I do have access to geek:area with W7 ;), however, it’s just the new option “the Win RE used for Boot-time scan can be disable” that is not available on my W7
Hey there I have the same problem else u the same message Error unable to start service aswmonflt mine it’s does it all the time when I do a Boot time scan I thinking to switch back to previous version of avast if the problem continues its really annoying I needs to be fixed
This may (or may not) provide a clue to the problem:
I found that when I did a “cold” boot (shut down the PC completely, wait, and then start it up) it would boot normally, completely bypassing the boot-time scan.
When I did a “Warm” boot (Restart), the above-discussed problems occurred.
In the past, it didn’t matter which way I booted; it always worked.
When you do a Shutdown / Startup (assuming Fast Start is in use) the PC does not do a full clean boot.
Only when you do a Restart does a full boot occur.
That is why you are asked to do a “Restart”, not a Shutdown / Startup following a software update etc.
Interesting. Many years ago, I was told the opposite: shutdown/startup is a clean boot and restart isn’t.
I guess things have changed…
But then why, before the present boot-scan issue cropped up, would it work no matter which type of boot I used?
You probably know more than I, having run it once already. I rarely run on-demand scans (outside of forum questions and when I did use the beta stream) and less so boot-time scans.
The whole idea is to get away from the god awful boot-time display.
I gave your info on the French forum where the problem had been reported.
One person replied that the problem was still not solved(with v22.9)
He had previously checked the “Run in Windows Recovery Environment” box via the hidden menu.
Maybe there are still some versions of W10 that have problems?
I haven’t read all this, but FWIW I ran a boot-time scan on Win10 pro PC by loading the definitions, scan at next restart, then restarting. When it restarted, the PC was in a loop: “avast antivirus is loading”
I did a hard restart by pressing the power button until shutdown then restarted with the power button. The PC restarted normally with not boot scan. I’ve run many boot scans and never had this problem. In fact I simultaneously ran a boot scan on a Win11 laptop with no problem. My avast version is 22.12.6044 (build 22.12.7758.769).
This PC is well protected so I’ll wait for a version change to run another boot scan.
so I'll wait for a version change to run another boot scan.
I'm not sure if the next version will solve the problem (avast seems to settle for the solution in "geak:area") :-\
https://forum.avast.com/index.php?topic=321784.msg1695700#msg1695700
old issue.
there are links above in this thread explaining how to revert back to the old version of boot time scan.
you need to find the hidden geek area. untick a box and reboot. then you will be able to run the old version of boot time.
after reading all the links posted about this issue it actually is not an issue or fault but an included update in the latest avast version.
Milos posted about the Geek area (post 15) here https://forum.avast.com/index.php?topic=320643.0
by unticking the box highlighted in his picture (Boot time scan: Run in windows recovery environment) and restarting then going to UI and clicking on run boot time scan on next bootup and the old version of run time scan runs as normal.