MBAM's Service was the most active, and so I have to assume it was responsible for all the disk activity I was seeing. While I could see the avast emergency update listed among the still-active tasks, it seemed to be using no CPU. After waiting a few minutes, I decided it was finally time to hit CTRL-ALT-DEL, to see if I could access Task Manager. I could see the hard disk chugging-away, so I figured I'd wait a bit for the update to do its job.

The cursor was 'alive' (=movable/responsive), but there was no background/Desktop (Explorer). But this morning was very different: My Win7 (primary) system, after I typed-in the password, booted to a black screen, with only a white cursor showing. And several of these updates were offered repeatedly, perhaps to make sure that no one inadvertently 'escaped' from updating.ĭepending on the nature of the update, it's to be expected that, upon (required) rebooting, there may be a SMALL lag as some of avast's system files are updated/replaced. I believe some of these updates were considered 'stepping-stones', in preparing the path for avast8 users to upgrade to avast2014. Users (myself included) have been inquiring about the nature of an abundance of so-called 'emergency' updates, without ever getting an adequate explanation. It was rarely ever needed.Īt some point late last year, apparently they decided to use 'emergency' updates more frequently, for NON-emergency tasks. Originally, the concept of emergency update was supposed to allow avast to 'easily fix' any major glitches that inadvertently happened to manifest themselves, without having to update the entire program, nor cause undue hardship to its many users. Well, Avast pushed another 'emergency' update this morning.

Avast update problems xp