Windows 10: Error message "<SessionEnv> unavailable" at every bootup

**
At every bootup of Win 10 64-bit, I have the Event Viewer "Information" message:
"The winlogon notification subscriber <SessionEnv> was unavailable to handle a critical notification event."

This has Event ID 6003.

The "Details" are the following:

- System
- Provider
[ Name] Microsoft-Windows-Winlogon
[ Guid] {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}
[ EventSourceName] Wlclntfy
- EventID 6003
[ Qualifiers] 32768
Version 0
Level 4
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2015-08-19T12:20:24.000000000Z
EventRecordID 1609
Correlation
- Execution
[ ProcessID] 0
[ ThreadID] 0
Channel Application
Computer Opti7010Win8
Security
- EventData
SessionEnv
D9060000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 000006D9
In Bytes
0000: D9 06 00 00 Ù...
By the way, on the last four bootups, there have been NO "Errors" or "Warnings". (The above is in "Information".) Also, on the last bootup, the above appears twice, seven seconds apart.

What do you think?

:)

 

Error message "<SessionEnv> unavailable" at every bootup - Win 10 Pro 64-bit

At every bootup of Win 10 64-bit, I have the Event Viewer "Information" message:

"The winlogon notification subscriber <SessionEnv> was unavailable to handle a critical notification event."

This has Event ID 6003.

The "Details" are the following:

- System

- Provider

[ Name] Microsoft-Windows-Winlogon

[ Guid] {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}

[ EventSourceName] Wlclntfy

- EventID 6003

[ Qualifiers] 32768

Version 0

Level 4

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2015-08-19T12:20:24.000000000Z

EventRecordID 1609

Correlation

- Execution

[ ProcessID] 0

[ ThreadID] 0

Channel Application

Computer Opti7010Win8

Security

- EventData

SessionEnv

D9060000

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

Binary data:

In Words

0000: 000006D9

In Bytes

0000: D9 06 00 00 Ù...
By the way, on the last four bootups, there have been NO "Errors" or "Warnings". (The above is in "Information".) Also, on the last bootup, the above appears twice, seven seconds apart.

What do you think?

 

Error message "<SessionEnv> unavailable" at every bootup - Win 10 Pro 64-bit

Ms. Kishore - Apparently my earlier reply was erased by your forum.

I resent your answer. I really do. This is why I wish there were an alternative to MS.

Your product has a problem, you give me no useful information at all, and you want me -- and I am NOT a tech person -- to do a lot of work to try to find out what's wrong. And that technet link is useless to me.

Your product has an issue. Please fix.

I am NOT on a domain.

What is SessionEnv?

By the way, the message said that the unavailability of SessionEnv means that I missed a "critical notification", so this is serious.

Please tell me what to do to fix this. Thanks.

 

This is something I wrote about Win7 and Win8.1. I am surprised that windows 10 suffers the same issue.
I was a Win 10 Insider, but didn't look for the nefarious Wlclntfy issue.

Here is the post:
Hello,
I running Win7 pro but I noticed a reference in your text referring to "Wlclntfy" I have the same error.
There were 3 registry entries related to a file "Wlclntfy". The file DOESN'T/DIDN'T exit on my system, so I began to wonder about it. I have 2 genuine installation disks for Win7 and 1 for Win8.1.
I used a program 7-zip and "deconstructed" the entire disks, i.e. looked at every file on both the Win7 & 8.1. It is NOT on any of the disks. How did it get into the registry???
So I ran 3 anti-virus programs and 3 anti-rootkit. My system is clean.
I called M$ tech support and they "blew me off". I reported the incident to M$ as abuse, but got nowhere.
Here is the registry entry that I deleted and a subsequent Event Log entry as a result.
THERE IS NO FILE CALLED Wlclntfy

Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\eventlog\Application\Wlclntfy]
"EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
5c,00,77,00,69,00,6e,00,6c,00,6f,00,67,00,6f,00,6e,00,2e,00,65,00,78,00,65,\
00,00,00
"TypesSupported"=dword:00000007
"providerGuid"="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}"
Event Viewer:
The description for Event ID 6000 from source Wlclntfy cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, the display information had to be saved with the event.


The following information was included with the event:


SessionEnv
Any thoughts on who to contact a M$ Headquarters??????
Regards,
Bob Sabo

 

I deconstructed WIN 10 just now. There is no file with the name Wlclntfy.

 

bobsabo - I'm not a tech, but maybe the following info is helpful to you (and me):

Doing a regedit search now for "wlclntfy" in my Win 10 Pro 64-bit. This is what I find:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\Wlclntfy
Class Name: <NO CLASS>
Last Write Time: 7/10/2015 - 7:05 AM
Value 0
Name: EventMessageFile
Type: REG_EXPAND_SZ
Data: %SystemRoot%\System32\winlogon.exe

Value 1
Name: providerGuid
Type: REG_SZ
Data: {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}

Value 2
Name: TypesSupported
Type: REG_DWORD
Data: 0x7
By the way, the above is the SAME as HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\Winlogon.

Also see:

Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Winlogon
Class Name: <NO CLASS>
Last Write Time: 7/10/2015 - 7:05 AM
Value 0
Name: EventMessageFile
Type: REG_EXPAND_SZ
Data: %SystemRoot%\System32\winlogon.exe

Value 1
Name: providerGuid
Type: REG_SZ
Data: {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}

Value 2
Name: TypesSupported
Type: REG_DWORD
Data: 0x7
which is the same as HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Wlclntfy.

There are no other "hits" in regedit for for "wlclntfy".

Does this mean anything?

 

In answer to your question, it doesn't mean sh**, just refusal on the part of M$ to respond to legitimate questions. When they blew me off, I considered filing a "small claims court" suit to get an adequate response. And I consider myself a 9 of 10 on Win operating systems. I manage 6 of my relatives computer remotely via Team-viewer. This disregard is offensive to me. I am 73 years old and computers are my hobby. This "information" event has been going on for 5 years.

I think a lawsuit would get their attention. I am 73 y/o and attended Law School in the 1960's. Never finished because it was too boring. However I am 6 for 6 since then on big issues.

Should I decide to do this, would you consider being a co-plaintiff??? It would be fun............
Regards

 

babsabo - yes it would be fun. Well, I happen to be a lawyer and have enough law all day long. But go for it. You'll finally get their attention.
Just that these error messages, by themselves, have not done us any damage. So what's your claim?
But if you start in small claims court, at least MS will have to assign someone to defend, and that person can be the conduit to getting this fixed.

 

It took awhile, but I don't give up. Update KB2775511 starts the problem. Get rid of it. However, you have to good at working the registry, because there is more to do. But it can be done. If you want to give it shot, let me know.
Regards

 

bobsabo - by all means send your steps, including registry. Thanks.

 

I will create .txt file with the details. Then get to you via the forum.

 

See attached txt file.

 

bobsabo - thanks.

As far as I can tell, KB2775511 was never installed on my Win 10 or my Win 7 Pro 64-bit. It's not in any update list on my dual-booting PC.

Also, while I'm sure your registry cleanup would help eliminate the error messages, I'm concerned because the error message (top of this thread) says that <SessionEnv> is not available to handle a "critical notification". I actually want to get <SessionEnv> working to see what is the "critical notification" I've been missing.

 

The notification verbiage is dramatic, but if you look at "event" it,s a "information" notice at best, not a warning nor an error. Remember you will have two rescue backups, whole windows and whole registry backup in reserve.

 

bump. anyone else find a solution?