mEtRiX, our forum moderator had an annoying computer problem for weeks which is it takes longer than usual to log on to Windows. He has already scanned his computer with Kaspersky Internet Security 2009 and Spybot but it did not fix the problem. He was only able to tell me that this slow logon issue is caused by executing wlnotify.dll file on startup. Searching in Google about wlnotify.dll reveals that it is a process info for Common DLL to receive Winlogon notifications.
To know which file is causing the slow logon problem, you’ll have to enable verbose status message, a hidden feature in Microsoft Windows. Although we already know which file is the cause of the problem, we’ve had a pretty tough time trying to fix it as it wasn’t that easy. We couldn’t even find any solution to this problem in Google and other tech forums. So it’s up to us and yes, we finally found the reason why the “Windows is starting” screen get stuck because of wlnotify.dll file.
I’ll write the troubleshooting steps so you’d know what to do when you have a similar problem. Sometimes when we need to troubleshoot a problem, we’ll have to go through step by step to narrow down the problem.
1. Virus, trojans and spywares.
- I know mEtRiX is very careful not to simply run any untrusted program, so it shouldn’t be a virus or spyware that is causing this. Moreover, he has already ran a full scan with KIS 2009 and Spybot.
2. Windows Safe Mode
- Booting into safe mode is very important because it shows that whether this problem is caused by some software or drivers. Unfortunately the problem still exist when he tried booting into Safe Mode.
3. wlnotify.dll file
- Another possible cause for this problem is a corrupted wlnotify.dll file. We’ve both checked the size of the DLL file and it matches at 92,672 bytes.
4. Deleting wlnotify.dll
- Tried renaming the file and Windows automatically replace a new wlnotify.dll file in C:\Windows\System32\ folder.
5. Disabling Network Adapters
- Safe Mode loads up networking support. Since wlnotify.dll file is for winlogon notifications, so I thought maybe Windows calls home whenever it is trying to log in. Both wireless and wired adapters are disabled in Device Manager, boot to Safe Mode again, still the same problem.
6. TuneUp Utilities
- mEtRiX mentioned that he has TuneUp Utilities and he guessed that it might be the settings there that is causing the problem. So I installed TuneUp Utilities on my test system and configured everything the same as he has configured on his computer. Restarted and my test system was able to boot up without issues.
When I nearly ran out of idea on what else to check, I figure that I should also try to look for any errors in Events Viewer. Went to Control Panel > Administrative Tools > Event Viewer. Clicking on Application, Security, System or Internet Explorer shows “Unable to complete the operation on “System”. The interface is unknown.”. Turns out that mEtRiX had Event Viewer disabled from services. I asked him to enable back Event Viewer from services and then restart. Amazingly the slow logon problem which is caused by wlnotify.dll is gone! I tried replicating the problem on my desktop by disabling Event Viewer on my test system and indeed the log on time did take slightly longer than usual. Re-enabling Event Viewer solved the problem.
If you’ve enable verbose status message and found that wlnotify.dll takes very long to execute, you should check your Event Viewer service and make sure that it is started. To check, go to Start > Run, type services.msc and click OK. Look for Event Log at the name column and double click. Make sure that the Startup type is set as Automatic and Service status is Started.
Try ALT-TAB. It worked for me.
What? ALT-TAB is what looks at other windows. I looked carefully after three times and realized I had a popup right before the above notify dll thing. Well, it was waiting for me to press OK, but that window was no longer there. I tried ALT-TAB, the window came back, I pressed OK, and then vuala, I got to log in.
I have the wlnotify.dll slow logon problem, and none of the above suggestions worked. My Event Log service is enabled. It turns out that this is caused by the Google Chrome browser! A new account with no Google Chrome installed, has no wlnotify.dll logon delay. Install Chrome, and with it comes the wlnotify.dll logon delay. Remove Chrome, and away goes the wlnotify.dll logon delay. This is fully reproducible on my XPsp3 Dell machine.
It should also be noted that the wlnotify.dll logon delay occurs once after cold restart. Once one user has logged on, login out and in as other user, or swicthing users exhibits no wlnotify.dll logon delay.
The question is /why/ it was disabled. The *only* reason I can find to do so is to get GTA IV working: superuser.com/questions/288366/turning-off-windows-event-log Not surprisingly, the consensus seems to be that Rockstar is absolutely wrong for telling users to disable the event log. I wonder if mEtRiX has GTA IV.
I had this issue and it was related to auto login.
Thank you for the article Raymond. :)
Too bad that it’s not going to help me. :/ I already have all settings as described, but the wlnotify.dll is still causing the windows to logon for ages…
Hey, Raymond. My Windows also got this problem but the Event Log already automatic and started by default and my Windows still slow at executing wlnotify.dll when logon. Any ideas or different way to fix this?
Thanks Ray.. It solved the problem here
hi Ray
i am also having the same problem but my event log is enabled and startup is automatic and it is shown as started in sevices properties dialog box… i also have scned my compouter with kaspersky,avg,avira,tdsskiller and no luck so far.. help me.
thanks
I had to turn the Alerter Service back on in order to avoid the hang on startup.
I also have problem with executing wlnotify.dll. I need to reopen several times.
Hola primeramente es lo mas conveniente ver el visor de sucesos, e ir pestaña por pestaña en las opciones, a veces puede ser por que tenemos instalados otras cosas como Windows VistaAparience, etc, etc. Pero a una computadora que repare tenia un virus Win/Worm32. svhost… No se como actua.. pero con Nod Eset Antivirus lo elimino, y utilizando otras herramientas GNU antivirus logre en algo solucionar este inconveniente, ahora despues de eso me salio Directiva de Grupo /windows/system32/wlnotify.dll
Probe con el visor de sucesos y encontre el error, no fue en lo que tiene que ver a un servicio de red, al parecer fue como dije una directiva de grupo, revise en otra maquina con Xp y copie y pegue en donde esta esa y fin del problema….
Suerte a todos, ah yo no uso Windows, uso GNU/Linux, pero aya los problemas son de otro tipo y no de virus ;)
It’s works.Thank’s man.Also error message “printer not found “in word gone. Works on win xp x64
My computer’s Event Log is enabled and starts automatically, yet I get the wlnotify.dll slowdown business. I’ve searched many other forums after checking this one, and I come back here. Is there any other way to stop it from slowing the system down on startup? Shutdown is a non-issue in this regard, it’s just the startup that gets bogged down by this .dll process. I just reformatted my computer and re-installed XP yesterday and already this problem has become a monkey on my back, so help along this line would be greatly appreciated. Thank you.
my event log detect application eror here is copy from clipboard
Event Type: Error
Event Category: None
Event ID: 1500
Date: 12.12.2009
Time: 20:31:32
User: NT AUTHORITY\NETWORK SERVICE
Computer: K7N2-XH3ESUIURM
Description:
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator.
DETAIL – Not enough storage is available to process this command.
For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.
Event Viewer’s start up type is already set as automatic and the service status is started.
My start up issue with wlnotify.dll isn’t as severe as the examples mentioned, but it still delays Windows from fully loading for 15 to 20 seconds – it never used to do this. I guess I’ll just have to put up with it.
Is it really this easy? Dang now I can’t wait to try to boot up again. Thanks
Really. there is not a word to describe you other than
“GENIUS”
thanks man. the event log service was disabled for me.
now it works
what a relief to finally find the culprit! I tediously checked a number of other google searches before finally getting the answer right here. Thanks a bunch for saving me from mentaling out Raymond.
me too,, my event log was already set in automatic,,,, and it is started… but still i cant log in,, and sometimes it takes to 15 minutes to 20 to log me in,, can anyone help me on this one,,, send me a message in my e mail plss doukeshi_koichi@yahoo.com.. thx in advance,,, and very much.
I have the same issue when shutting down the PC, when I try and shut down it sticks on executing wlnotify.log for around 15 minutes. Any ideas why this might be?
Thank You Raymond !!! :) I did some tuning of Windows services. Now I known, that Event Viewer should not be disabled. From 1 minute of startup, to 1 second, delicious :)
you are really genius.Today; if i have some tricky or good knowledge about computer problems that is just for you.
Thanking u from the bottom of my heart…..make ur website more imformative.god bless u “RAY THE GENIUS”.
wow i also tried killing wlnotify on autoruns etc.
so that is why my services stripping paid for.
Brilliant diagnostic explanation Ray. Well done and thank you for that time saver !
Thanks Raymond.
You are indeed a genius.
This my first time here. Very informative website. I’ll be back to learn more. Keep on posting, ray !