Error Event Id 36887
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Event ID 36887 error Windows 7 event id 36887 schannel 46 IT Pro > Windows 7 Miscellaneous Question 0 Sign in to vote
Event Id 36887 Fatal Alert 48
Hi all,After boot-up this error showed up in the System Event Log :Source : system Event ID: 36887 event id 36887 schannel fatal alert 42 " the following fatal alert was recieved :47I researched it and from what I understand it may be a security certificate issue?? I havent installed any new programs or hardware,
Event Id 36887 Schannel 20
The computer is part of a workgroup not a domain. checked Windows update... computer fully updated. I did a complete shutdown... waited 5 to 10 min and restarted and the error didnt show up. I was curious on what this error means. I sent detailed feedback to Microsoft and also copied the details of the error here. Anyone else have event id 36887 schannel fatal alert 49 this error? System - Provider [ Name] Schannel [ Guid] {1F678132-5938-4686-9FDC-C8FF68F15C85} EventID 36887 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2009-03-02T13:18:52.866643400Z EventRecordID 7757 Correlation - Execution [ ProcessID] 524 [ ThreadID] 560 Channel System Computer Windows7-PC - Security [ UserID] S-1-5-18 - EventData AlertDesc 47 Monday, March 02, 2009 2:46 PM Reply | Quote Answers 0 Sign in to vote hi,thx for the input....I will monitor the processes and see what happens. So far the error hasnt reoccured. Strange! maybe just a wierd monday glitch :-)if I figure it out... will post :-)thx again Marked as answer by Mark L. FergusonModerator Monday, March 30, 2009 3:03 PM Monday, March 02, 2009 5:25 PM Reply | Quote All replies 1 Sign in to vote I couldn't find anything significant in my searches either. I'd suggest monitoring the process to see if it recurs. FWIW, check the process with PID 524 (Task Manager...Processes tab...View...Select Columns...PIDBe aware that the current PID may not be the same as the PID was when the error happened. B
Kingdom United States ZDNet around the globe: ZDNet Belgium ZDNet China ZDNet France ZDNet Germany ZDNet Korea ZDNet Japan Go Central Europe Middle East Scandinavia Africa UK
Event Id 36887 Schannel Fatal Alert 70
Italy Spain more Estonia European Union Mobility Hardware Innovation See All Topics White Papers
Event Id 36887 Schannel Exchange 2010
Downloads Reviews Galleries Videos Newsletters All Writers Log In to ZDNET Join ZDNet About ZDNet Manage Profile Newsletters Author Alerts event id 36887 schannel 40 Discussion Alerts Recent Activity Log Out Go Menu Central Europe Middle East Scandinavia Africa UK Italy Spain Estonia European Union Mobility Hardware Innovation See All Topics White Papers Downloads Reviews Galleries Videos Log https://social.technet.microsoft.com/Forums/windows/en-US/aa2776a5-a8ef-4241-bd71-0a0d672e18b0/event-id-36887-error?forum=w7itprogeneral In to ZDNET Join ZDNet About ZDNet Manage Profile Newsletters Author Alerts Discussion Alerts Recent Activity Log Out eu Asia Australia Europe India United Kingdom United States ZDNet around the globe: ZDNet Belgium ZDNet China ZDNet France ZDNet Germany ZDNet Korea ZDNet Japan Microsoft warns of problems with Schannel security update The mysterious and critical Schannel vulnerability also contained some new TLS ciphers which are causing http://www.zdnet.com/article/microsoft-warns-of-problems-with-schannel-security-update/ problems. Here's how to work around them. By Larry Seltzer for Zero Day | November 16, 2014 -- 23:08 GMT (23:08 GMT) | Topic: Security Microsoft has issued a warning in the knowledge base article for the MS14-066 update released this past week. The company has provided a workaround, but is not recommending that users avoid the update or uninstall it. The update fixed at least one critical vulnerability in Schannel, Microsoft's implementation of SSL/TLS encryption. It has widely been considered highly critical and last week we urged users to apply the update as soon as possible. But some users who apply the update are having serious problems. The issues occur in configurations in which TLS 1.2 is enabled by default and negotiations fail. When this happens, according to Microsoft, "TLS 1.2 connections are dropped, processes hang (stop responding), or services become intermittently unresponsive." There may also be an event ID 36887 in the System event log withe description "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40." What's Hot on ZDNet Samsung suspends Note 7 production in the wake of more fires Serious security: Three changes that c
& Malware White Papers Endpoint Security CybercrimeCyberwarfare Fraud & Identity Theft Phishing Malware Tracking & Law Enforcement Whitepapers Mobile & WirelessMobile Security Wireless Security Risk & ComplianceRisk Management Compliance Privacy Whitepapers Security ArchitectureCloud Security Identity & http://www.securityweek.com/microsoft-warns-issues-recent-schannel-update-patch-away Access Data Protection White Papers Network Security Application Security Management & StrategyRisk Management Security Architecture Disaster Recovery Training & Certification Incident Response SCADA / ICS Home › Network SecurityMicrosoft Warns of Issues With Recent SChannel Update, But Patch Away! By Mike Lennon on November 17, 2014 Tweet Last week, Microsoft released 14 security bulletins as part of Patch Tuesday for November 2014. The updates contained four rated event id as critical, but one has been receiving the most of attention: A vulnerability that affects Windows Secure Channel (SChannel) security package in Windows. While Microsoft released the update (MS14-066) to address the Schannel Remote Code Execution Vulnerability (CVE-2014-6321), the software giant has reported that some users who have applied the patch are having issues, including a fatal TLS error. “We are aware of an issue in certain event id 36887 configurations in which TLS 1.2 is enabled by default, and TLS negotiations may fail,” Microsoft noted in a knowledge base article. “When this problem occurs, TLS 1.2 connections are dropped, processes hang (stop responding), or services become intermittently unresponsive." Microsoft warned that some users may receive an error message that resembles the following in the System log in Event Viewer: Log Name: System Source: Schannel Date: Date and time Event ID: 36887 Task Category: None Level: Error Keywords: User: SYSTEM Computer: ComputerName Description: A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40. Fortunately, Microsoft provided awork around for the issue, which involves deleting certain cipher entries in the registry, but warned that serious problems might occur if users modify the registry incorrectly. Microsoft did not pull the patch, which it has done previously with botched updates, and has not suggested that users avoid applying the patch. The Microsoft Schannel Remote Code Execution Vulnerability, which some have referred to as “WinShock”, allows attacker to run arbitrary code on a target system by sending specially crafted packets to a Windows Server or workstation (client) that is running an affected version of Schannel. W