Stuck at Please wait...

[Bassmaster]

I've had this issue happen sporadically on various windows 7 computers.  It does tend to happen more frequently around patch Tuesday updates.  Its not related to folder redirection, roaming profiles, etc because the "Please Wait" issue occurs prior to the user ever getting the Control Alt Delete screen to log in.  Those policies are normally  applied after the login.  You should not have to disable avast, or run a repair to get past this nuisense problem that Avast needs to resolve.  2 things that always have worked for me.  1. Log in using Safe mode with networking.  And do a system restore back to the latest restore point.  After the reboot, the system should boot up normally.

2. Another option that works for me is to again login in using safe mode, but login in locally with the local admin account (needs to be enabled prior to trying this when system is functioning normally) Go to MSConfig and choose diagnostic start up-reboot.  Boot back into safe mode and login locally again and go to MSConfig and now select normal startup.  The PC should reboot and start normally again.

[paradox183]

What about roaming profiles?

Don't use those either.

Its not related to folder redirection, roaming profiles, etc because the "Please Wait" issue occurs prior to the user ever getting the Control Alt Delete screen to log in.

Most of the time it happens at "Please Wait...", but occasionally the user will press Ctrl-Alt-Del, enter their username/password, and then get stuck at "Welcome".

[Michael Due]

What really really #"¤"#¤#%  me off is the lack of responses from an Avast official.

Gues they dont #"¤"#¤"#4! For people who's been loyal customers for over 6 years.

Never ever ever recommending this product again!!!!! and i used to do it all the time in my last 10+ years as IT Admin to personal and company use.

And i usually never flame forums believe it or not, so above statement all though crude and childl'ish is just a symbol of how FRUSTRATED we are with you or should i say the LACK of you and your responses Avast!!!

[drace1111]

For the record, I can list some things that this problem is NOT related to:

- Folder redirection (we don't use it)

What about roaming profiles?

We're not using roaming profiles, so it's not related to that either.  Other than folder redirection, everything that paradox183 listed is true for us as well.

[Avosec-UK]

Okay guys, can you do following:

• Select a machine which has the problem.
• Boot into safe mode.
• Go to "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\" or "C:\ProgramData\AVAST Software\Avast\" depending on the OS.
• Open the "FileSystemShield.ini" and find the "ProviderEnabled" setting and set it to "0".
• Open services and disable the "avast! Net Client Service" or "avast! Enterprise Client Service" services.
• Reboot the machine in normal mode and report here.

If the machine boots up normally:

• Go to "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\" or "C:\ProgramData\AVAST Software\Avast\" depending on the OS.
• Open the "FileSystemShield.ini" and change the following settings:
  
  • "ProviderEnabled" to "1".
  • "ReportName" to "fs"
  • "ReportRecords" to "Infected;HardErrors;SoftErrors;OK;Skipped"
• Reboot the machine.
• Try to login.
  If you you were able to login:
  
  • Go to "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\report" or "C:\ProgramData\AVAST Software\Avast\report" depending on the OS and get the fs.txt file.
  Else:
  
  • Boot into safe mode
  • Go to "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\report" or "C:\ProgramData\AVAST Software\Avast\report" depending on the OS and get the fs.txt file.
• Attach the fs.txt file here in your next reply.

[PetrP]

Hello,

we still cannot reproduce this issue, but we are looking into it. Sorry for the inconvenience!

One idea is to disable the sandbox driver.
Execute the following command from cmd (start cmd as administrator with disabled avast self-defense):

sc config aswsnx start= demand

Which will block aswsnx to load.
Or/and, you can try to rename aswsnx.sys under Windows\system32\drivers\..

Let me know if it helps.

[1tb]

.  2 things that always have worked for me.  1. Log in using Safe mode with networking.  And do a system restore back to the latest restore point.  After the reboot, the system should boot up normally.

Try doing this on a production server!

[Dewg]

I've had a massive problem with this today - dozens of computers.

Has anyone tried the following:

Go into the Avast console.  Edit the configuration of the catalog/group.  Go go Policies: avast! Antivirus.  Go to the Troubleshooting section.  There is a checkbox "Load avast! services only after loading other system services".  If you check that box, does it solve the problem of the "Please Wait" ?

[.: Mac :.]

I've had a massive problem with this today - dozens of computers.

Has anyone tried the following:

Go into the Avast console.  Edit the configuration of the catalog/group.  Go go Policies: avast! Antivirus.  Go to the Troubleshooting section.  There is a checkbox "Load avast! services only after loading other system services".  If you check that box, does it solve the problem of the "Please Wait" ?

yes its been tried and no it does not usually help

[Dewg]

Now that 8.0 has been out for a while - has anyone who's upgraded to it found the Please Wait problem go away?

[brianeme]

We upgraded to 8.0 but left the avast! Enterprise Client Service as Automatic (Delayed Start), I haven't had a chance to test with this service set back to just Automatic on Windows 7/2008 systems yet.  Anyone else test this with 8.0?

[Bassmaster]

I've not seen the Please Wait issue re-occur once we upgraded to version 8.  Hopefully this is now resolved!

[.: Mac :.]

No issues here since the upgrade to v8.0.x 

[nannunannu]

No issues here since the upgrade to v8.0.x 

Didn't want to jinx it, but I think enough time has passed...  Issue seems to be solved here as well. 

Ditto for the hard lock every time you access a unc path with sufficient numbers of files to scan.

[cairol220]

Sorry to slow down your euphoria, but this issue still exists with version 8. We had a customer complained about 2 PCs with windows updates freezing at 51%, who had never any problems with that back in version 4 for years.

Support tells us, this is not an avast-related issue since virusprotection is not active in this state of the boot process. Strangeways we always did the following: turn off the pc, restart in safe mode, uninstall avast, reboot, install windows updates, reinstall avast. Not a real solution but it works and the customer can continue with his work.

But we'd really like to solve this annoying issue since we discover freezed pcs while installing windows updates every month.