Event Viewer Information re: Wlclntfy

[Kick]

Hi,

 

After each system startup of my Windows 7 SP1 desktop, the Event Viewer reports the following as information (neither a warning nor error):

---------------------------------------------------------------------------------------------------------------------------------------------

96811 Application Information 24/01/2017 19:07:47 Wlclntfy 0 6000 Chris-PC 4 124 The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.

---------------------------------------------------------------------------------------------------------------------------------------------

The computer appears to be working normally afterwards. Searching the computer for a Wlclntfy.dll file yields no results.

- Is it possible the dll file has been removed when an unwanted application that used the file was uninstalled (I use RevoUninstaller)?

- If so, is the dll file a necessary part of Windows 7 or is it only included when certain third party software is installed?

- If it is a necessary part of Windows 7, how can I obtain and add it?

- If it is not necessary and the Event Viewer information occurs because the system is unnecessarily searching for the file at startup, is there a way I can stop it?

 

Thanks, any advice would be appreciated.

[AWS]

Here is the information on that error.

 

https://technet.microsoft.com/en-us/library/cc734033(v=ws.10).aspx

 

This was written for Windows Server 2008, but, Windows 7 and Windows 2008 were built the same. Only difference is all the server tools were stripped out of Windows 7 except for IIS.

[Kick]

Hi AWS,

 

I have previously checked that site along with other sites that discuss the issue. In my case, logging on completes successfully and the computer seems to behave normally afterwards. I've also discovered, if I understood things correctly, that not all Windows 7 systems include the Wlclntfy.dll file and should a program to be installed require it, it would be added during the installation.

 

It's possible that my system resources are insufficient - they are limited on my system but I do not have too many things happening during startup as I've cleaned out all unnecessary items. If the registry is corrupted in any way, it has not affected normal running of the computer. Unfortunately I don't appear to have any restore points or image backups of the C: partition that pre-date the issue. I may try the 'Startup Repair' option although last time I tried it regarding a different issue, I was not successful.

 

Anyway, thanks for your input - I will report back should I make any progress,.

 

Regards.

[DSTM]

Hi Kick.

You said you don't appear to have any restore points that pre- date this issue.

 

Windows makes automatic restore points. You don't have any when you tick the box "Show more restore Points"?

My Windows7 SP1 has.

 

[Kick]

Hi DSTM,

 

I had cleared all but the latest restore point in a Disk Cleanup operation sometime ago before I was aware of the issue. Since then I have built up restore points when I have uninstalled software. After your post, I checked System Restore and there were no restore points at all - I don't know how that happened but now System Restore is behaving correctly again.

 

I'm continuing to look at the options available via my Restoration partition - I'm loath to do a full reinstallation of Windows unless absolutely necessary but hoping 'Startup Repair' may help. As, despite the Event Viewer report information, everything seems to be working normally, I may just live with the situation for the time being. At the moment I inclined to think that an uninstallation of a program that utilized Wlclntfy.dll has caused the problem by leaving something behind in the registry - I use Revo Uninstaller in maximum mode and that doesn't normally leave much behind.

[Kick]

Hi,

 

UPDATE:

'Startup Repair' found no problems so the issue remains. I also created a temporary new user account (administrator level) in case there were any corrupted files in my usual user account - the Event Viewer reported in exactly the same way when logging on to the new account as when logging on to the original account. It certainly seems the issue is harmless - perhaps one day I will get everything prepared for a reinstallation of Windows 7 but I don't want all that hassle at the moment (reinstallation and setting up of programs, Windows updates etc.) and I can live with things as they are and there no major problems developing from the reported issue.

 

I would still welcome comments and advice however particularly if there is anything fairly simple I might try before the big step of reinstallation.

 

Thanks.

[DSTM]

Hi Kick.

If it not causing any issues, I would live with it till one day you do a reinstall.

Sometimes you can make something worse trying to fix a minor issue.

I have done non destructive reinstalls,but would not go that route again.

 

P.S.

I have a silly thing happening with this computer.

My Hard Drive LED usage is not showing on the front of my Computer Tower.

Instead it is showing all the time in my monitor start button. The front panel wires are correct on the motherboard. I just live with it.

edit. Fixed in a fashion.:)

[DSTM]

Further.

In your first post, Kick, it says:

 

"96811 Application Information 24/01/2017 19:07:47 Wlclntfy 0 6000 Chris-PC 4 124 The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event."

Going by that looks like your OS needs that .dll, and somehow it's been deleted.

I presume your Windows system is 32bit.

The Wlclntfy.dll can be downloaded and installed if you so wish.

Would stop that event viewer entry, I would guess.

A question for Techies.

"The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible."

 

I think this should work in "Kicks" case.

He may have to run a couple of times.

It should put that .dll back?

What are your thoughts????

[Kick]

Hi DSTM,

 

Another UPDATE:

 

I downloaded the wlclntfy.dll and placed it in the system32 folder in Windows but could not register it - I got the following message from RegSvr32 (run at administrator level):

 

The module "C://Windows/system32/wlclntfy.dll failed to load.

Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL file.

The specified procedure could not be found.

 

A bit more searching online found the webpage for which this is a link: http://www.processlibrary.com/en/directory/files/wlclntfy/322375/

I don't know if it adds more light to my situation.

 

I'll persevere with sfc /scannow, I've run it a few times but that has been in different sessions - I'll try some back to back runs to see what happens.

 

Thanks for your continued interest, regards Kick.

[Tony D]

Run sfc /scannow.

 

btw: that dll may have to be registered. Instruction from MS are here https://support.microsoft.com/en-us/help/249873/how-to-use-the-regsvr32-tool-and-troubleshoot-regsvr32-error-messages

[Kick]

Hi Tony,

Runs of sfc /scannow (I've just tried three in succession) all give the message "Windows Resource Protection did not find any integrity violations." I have looked at the link you gave and followed the advice in it without success.

Thanks for your interest and suggestions, regards, Kick.

[plodr]

I searched for <SessionEnv> instead of the dll. It has to do with Remote Desktop.

Look at the service and perhaps changing it will remove the error

http://www.computerstepbystep.com/remote_desktop_configuration.html

 

I just checked my 64 bit netbook. I have the service, though I have NEVER done anything using remote desktop. I think it is included so tech support can help.

 

According to this

http://www.blackviper.com/service-configurations/black-vipers-windows-7-service-pack-1-service-configurations/

Manual is the default. I have that but you can tweak it to disabled.

[Kick]

Hi Plodr,

 

Thanks for your suggestions. I disabled the Remote Desktop Service but the information report (it is only marked as information, not a warning or error) still appeared in the Event Viewer after the next startup. I re-enabled the service to manual. The service was, as expected, in the stopped state so I started it and then closed my session and restarted the computer. Normally the Event Viewer shows two identical reports concerning wlclntfy.dll (one appears when closing down to restart the system and one on restarting the system) but this time the report on closing down did not appear - only the message on startup appeared. This would seem to confirm the issue does indeed relate to the Remote Desktop Service as you have suggested even though disabling the service does not stop the report. I could try setting the service to automatic but if that stops the report appearing, it does not actually resolve the issue.

 

It looks like the missing wlclntfy.dll is the culprit but so far, nothing I've tried to register the copy of the file I have downloaded, seems to work.

[Kick]

Hi All,

 

UPDATE: I have got no further in resolving this issue but am satisfied that it is not really a problem and does not cause operational hiccups. A friend of mine has exactly the same version of the operating system and he has no copy of the wlclntfy.dll file on his system so Windows appears not to need the file - I guess the issue relates to a program I have uninstalled and that the uninstallation process has left something behind in the registry relating to wlclntfy.dll even thought the file was removed during the uninstallation. I use Revo Uninstaller in its most severe mode which is usually pretty good at cleaning up leftovers. A re-installation of Windows & is likely to clear the issue but as I am experiencing no problems, I'll wait to do that until I have more reasons - I am prepared though with copies of my key program installers, drivers and Windows Update rollups etc. all handy.

 

Thank you to AWS, DSTM, TonyD and Plodr for your help and suggestions.

 

Regards, Kick.