Please Wait Loop

[kennysarmy]

Has anyone else had issues similar to this:

 

 

 

If a computer is hanging on the "Please Wait…" or the "Welcome" screen it could be because of corrupted or overly large WBEM Repository files. Windows is instructed to render out these files each time the computer starts; usually these are relatively small however, in some cases it can be upwards of 800+ megabytes that needs to be loaded. This method has been effective in multiple cases and is worth trying if it is on the verge of being re-imaged because of the slow load times.

 

To fix the issue, follow these steps:

 

+ Boot into Safe Mode - Networking

 

+ Open Services

 

+ Set Windows Management Instrumentation and Security Center startup to "Disabled"

(This service is constantly running, and as such you cannot shut it down whilst Windows is running)

 

+ Restart the computer normally without safe mode

 

+ Navigate to Local Disk (C:)\Windows\System32\wbem

 

+ Check the file size of the Repository directory

 

(If larger than 100 - 200MB it could cause problems)

 

+ If this is the case, delete the Repository directory completely

 

+ Set Windows Management Instrumentation startup to "Automatic (Delayed Start)"

 

+ Restart the computer

 

+ Check to see if the issue has been resolved

[kennysarmy]

I am wondering about testing this:

 

Disable Resultant Set of Policy logging to improve logon performance

 

Resultant Set of Policy logging writes information to the WMI database for each user who logs on interactively. This causes the WMI database to grow, and can cause WMI database corruption.

 

From this site:

Notes on MS Integration, Administration, and Management: Disable Resultant Set of Policy logging to improve logon performance

[Cache]

I am wondering about testing this:

 

Disable Resultant Set of Policy logging to improve logon performance

 

Resultant Set of Policy logging writes information to the WMI database for each user who logs on interactively. This causes the WMI database to grow, and can cause WMI database corruption.

 

From this site:

Notes on MS Integration, Administration, and Management: Disable Resultant Set of Policy logging to improve logon performance

 

I do this on our RDS servers because otherwise they eventually just fall over completely for some reason, never got an answer as to why or the root cause of it (there is still another big issue on one of ours which I've not discovered after almost 3 years).

[Manny21555]

Hi Guys,

 

We had the same problem (mainly with windows x64 PC's). We have got some remote software called "Impero" which we thought the issue was.(we needed inject some files into PUA list from Sophos, we contacted Impero support to help us with that). We also install the KB below which might help you. I have added two pictures for you - thats if you use Impero but these are the changes we have made and since then the "please wait" and "Welcome has not happened"

 

Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7

 

After spending more time i found some KB fixes from Microsoft. Install them to the correct system and it should fix the issue!

 

Hope this helps!

 

Cheers,

Manny

Edited March 27, 2014 by Manny21555