Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 3117 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

System Event Notification error after update to version 10

tmanstls

We have a client machine that after it updated to version 10, when the computer is powered on in the morning, it takes the user 3 times before they can login. The first 2 attempts gives the error "Widnows Could not connect to the System Event Notification Serice service". The commputer OS is Windows 7 Ent 32-bit. After login, there are no major errors about this in the event log. Any help is appreciated.

:27709


This thread was automatically locked due to age.
  • 0

    HI,

    Can you post the comtents of the output files (winsock.txt and products.txt) from running the following commands (run them from an administrator command prompt):

    netsh winsock show catalog > winsock.txt

    wmic product get name,version > products.txt

    The second command can take some time.

    Regards,

    Jak

    :27715
  • 0

    from a command prompt type netsh and then winsock reset

    :27971
  • 0

    I ran the commands and looked at the installed programs and network settings. Nothing seemed out of the ordinary. Again this started happening right after the sytem automically updated to version 10. As a test, I uninstalled Sophos endpoint protection and installed MS Security Essentials to see if it would fix the problem. For the past 2 days the machine has not given that error and the user was able to logon each morning. My next step is to remove MSSE and reinstall Sophos as opposed to an upgrade from the previous version and see if the problem comes back.

    :27983