Error message "<SessionEnv> unavailable" at every bootup

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?

bobsabo said:

See attached txt file.

Thank you for the instructions file. I will try it, and see.
Best regards

Bump. Almost a year later, I am still getting these <SessionEnv> errors.

I have also been trying to get this resolved. If a solution is found by all means pass it on, I will certainly do the same on my end.

gtspeck said:

I have also been trying to get this resolved. If a solution is found by all means pass it on, I will certainly do the same on my end.

Hi sorry for delay in answering, I have been on a golfing week in Portugal
Still looking for the problem, today I did a clean install with only windows and office, and applied all updates. I still get the same symptoms.

I had suspected it was because I 'tuned' the system by deleting the windows apps, and changing services etc, but that can be ruled out after todays attempt... it happens with no user modifications, other than installing device drivers, and the office 2010 Home and Student, rebpoting a thousand times to ensure all updates are finished being applied

megwenda said:

Hi,

Maybe you have already given up after all this time?

The <SessionEnv> is another name for the Remote Desktop Configuration (source: Remote Desktop Configuration Black Viper | www.blackviper.com)

Not a solution yet, but maybe help

Comparing the time stamps in event viewer, I notice that when this error occurs in the applications section, there is also an entry in the system section for "User Logon Notification for Customer Experience Improvement Program"

I have not accepted CEIP, and have disabled it in task manager, so why is it logging in?
And maybe, just maybe, these messages are cause BECAUSE it is rejected/disabled?

mfG
Megwenda

I may have found the solution. Based on your input dealing with CEIP I started lookin in that direction. Try these steps:

RUN dialog box, then type taskschd.msc press enter

Now go to following folders one by one:

Task Scheduler Library -> Microsoft -> Windows -> Application Experience
Task Scheduler Library -> Microsoft -> Windows -> Customer Experience Improvement Program

Both these folders contain various tasks related to CEIP which automatically run at certain intervals and allow CEIP to collect and send your usage data

You just need to disable these tasks. Right-click on each task present in right-side pane of these folders and select Disable option. You can also select all tasks at once and then right-click and click on Disable option.

So far, this worked for me. Hopefully it will help everyone encountering this issue

Unfortunately that didn't do the trick for me

After much testing I have found out some more, and can now cause the messages to appear or not appear consistently.

If one goes into system -> remote settings, and then ACTIVATES the option "Allow remote connections to this computer", then the messages no longer appear in the application logs.... The CEIP logon message is still in the system log, but it doesn't have any problems

Change this back to "Don't allow remote connections to this computer", and the messages are back in the application log

Of course, this solution is no solution, as there is NO way I allow remote connections to my PC.

Question, what does the CEIP have to do with the Remote Desktop (Session ENV)? Is it trying to logon?

So, lets keep looking