AIS/Windows 7 Prof SP1 reboot hangs

 After updating to AIS 7.0.1456 on this computer running Windows 7 Professional, with SP1, I've had nothing but problems. I've spent countless hours trying to reinstall, repair or update and it hasn't helped.

 It does not shut down properly and when rebooting and gets to the "Welcome" window, it just hangs forever. Uninstall Avast and everything is fine.

 Any help would be appreciated

 Thanks.

I had exactly the same problems. I’m also running Windows 7 Pro with SP1. I updated Avast recently to the latest version and the pc behaved strangely since, starting with network problems and periods where everything froze for a few seconds. (I don’t reboot my pc very often, just hibernate it, so might not have rebooted since the update).

Today I had to reboot my pc as it behaved erratic after being woken from sleep mode. After rebooting my pc seemed to run with only a minimum set of drivers, task manager only showed about ten processes running. I tried all kinds of things to get it running properly again but could not run commands like msconfig or open network settings. Even Taskmanager, when clicking the “Show processes from all users”, would freeze up. Eventually I had to restore it back to a previous state before the update and it worked fine again.

I’m now reinstalling the update again and hopefully this time there won’t be any problems.

I can definitely say now that it is the latest update that caused the problems. After running the update again my computer refused to boot and I had to run repair and restore again to a previous point.

Same here. I can’t think of how much time I messed around with this. And the ONLY way I could reboot, was in Safe Mode. I just got fed up, did a clean un-install and I hate to say it, but installed Microsoft Security Essentials for the time being and all runs just fine.

Here are some of the ERRORS from the Windows System log, when it hung (in case they help).

  1. “The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
    The dependency service or group failed to start.”

  2. “DCOM got error “1084” attempting to start the service WSearch with arguments “” in order to run the server:
    {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}”

  3. “DCOM got error “1068” attempting to start the service netprofm with arguments “” in order to run the server:
    {A47979D2-C419-11D9-A5B4-001185AD2B89}”

  4. “The following boot-start or system-start driver(s) failed to load:
    AFD
    aswFW
    aswRdr
    aswSnx
    aswSP
    aswTdi
    CSC
    DfsC
    discache
    NetBIOS
    NetBT
    nsiproxy
    Psched
    rdbss
    SASDIFSV
    SASKUTIL
    spldr
    tdx
    UimBus
    Uim_IM
    Uim_Vim
    vpcnfltr
    vpcvmm
    Wanarpv6
    WfpLwf”

  5. “The SMB 2.0 MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error:
    The dependency service or group failed to start.”

  6. “The SMB 1.x MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error:
    The dependency service or group failed to start.”

  7. “The SMB MiniRedirector Wrapper and Engine service depends on the Redirected Buffering Sub Sysytem service which failed to start because of the following error:
    A device attached to the system is not functioning.”

  8. “The IP Helper service depends on the Network Store Interface Service service which failed to start because of the following error:
    The dependency service or group failed to start.”

  9. “The TCP/IP NetBIOS Helper service depends on the Ancillary Function Driver for Winsock service which failed to start because of the following error:
    A device attached to the system is not functioning.”

  10. “The DNS Client service depends on the NetIO Legacy TDI Support Driver service which failed to start because of the following error:
    A device attached to the system is not functioning.”

  11. “The DHCP Client service depends on the Ancillary Function Driver for Winsock service which failed to start because of the following error:
    A device attached to the system is not functioning.”

I hope this information is helpful to the TECH people, as it doesn’t mean much to me, other than, something is wrong. Since I’ve un-installed Avast and installed MSE, I haven’t had a single error or any issues re booting. This, I would think is pretty concrete evidence that the latest Avast update has something in it, that doesn’t play real nice with the operating system.

I am having the same problem. Running Win7, update to AIS 7.0.1456 results in very slow load times upon boot, and ie9 webpage initial loads very slow or fail completely, laptop messed up. Did system restore to 6/12/12 and no problem. Everything works fine. Then update AIS again and problems return. Do another system restore and problem solved. There is definitely something wrong with this latest update. I have wasted alot of time dealing with this. Not happy. >:(

Same problem here with avast free version. I didn’t notice any update message recently, it just happened at once. Had to disable avast. Also, I have Win 7 64b without SP1 .

Why are you posting in an old thread ??? Current version is 7.0.1474.

Because it happened to me on this version. I wanted to report the bug so that the devs can make sure it will be fixed and thus avoid wasting their clients time. I can provide more detail about my system if needed.

Why not update to the latest version ???