en[EVENT2002] Eap method DLL path

SC2 2018-02-10

2021-09-09

このサイトを検索 | Search this site

,Japan

This article is about Event ID 2002.

"Eap method DLL path" error was recorded 12 times in the event log of VAIO upgraded to Windows 10.

According to me,

This is because there is a setting in the registry that loads a Cisco /Intel driver that does not exist on the PC.

I am able to repair it and I will share the steps I have taken.

I'm glad if you can use it as a reference.

Event Log

The event log is reprinted.

Event Log
message	Skip: Eap method DLL path verification failed. Error: Type ID=43, Creator ID=9, Vendor ID=0, Vendor Type=0
log name	Application
Source	EapHost
Event id	2002
level	error
user	system

Categorizing the errors ...

The 12 errors are classified as follows.

Eap method DLL path error
Creator ID	Type ID	folder
9	43, 25, 17	C:\Program Files (x86)\Cisco
8086	23, 21, 18	C:\Program Files\Intel\WiFi\bin

Example of type ID and creator ID error

Skip: Eap method DLL path verification failed. Error: Type ID = 43, Creator ID = 9, Vendor ID = 0, Vendor Type = 0

Skip: Eap method DLL path verification failed. Error: Type ID = 25, Creator ID = 9, Vendor ID = 0, Vendor Type = 0

Skip: Eap method DLL path verification failed. Error: Type ID = 17, Creator ID = 9, Vendor ID = 0, Vendor Type = 0

Skip: Eap method DLL path verification failed. Error: Type ID = 23, Creator ID = 8086, Vendor ID = 0, Vendor Type = 0

Skip: Eap method DLL path verification failed. Error: Type ID = 21, Creator ID = 8086, Vendor ID = 0, Vendor Type = 0

Skip: Eap method DLL path verification failed. Error: Type ID = 18, Creator ID = 8086, Vendor ID = 0, Vendor Type = 0

Event Viewer snapshot

What is the cause?

This is because the registry database has settings that load Cisco /Intel drivers that do not exist on the PC.

When I was using Windows 7, I didn't check the Event Viewer at all, so it's not possible to determine if the upgrade was due to Windows 10.

Registry location

It is recorded in the following location.

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eaphost\Methods

Registry value

Reprint the registry value.

Intel /Creator ID: 8086

C:\Program Files\Intel\WiFi\bin\folder did not exist in my environment.

The registry was registered to load the following files:

Type ID: 18
PeerFriendlyName: EAP-SIM

C:\Program Files\Intel\WiFi\bin\eapui.dll
C:\Program Files\Intel\WiFi\bin\eh_eap_sim.dll

Type ID: 21
PeerFriendlyName: EAP-TTLS

C:\Program Files\Intel\WiFi\bin\eapui.dll
C:\Program Files\Intel\WiFi\bin\eh_eap_ttls.dll

Type ID: 23
PeerFriendlyName: EAP-AKA

C:\Program Files\Intel\WiFi\bin\eapui.dll
C:\Program Files\Intel\WiFi\bin\eh_eap_aka.dll

Cisco /Creator ID: 9

In my environment, the C:\Program Files (x86)\Cisco\folder existed but the contents were empty.

It was registered in the registry to load the following files:

Type ID: 17
PeerFriendlyName: @C:\Program Files (x86)\Cisco\Cisco LEAP Module\CiscoEapLeap.dll, -117

C:\Program Files (x86)\Cisco\Cisco LEAP Module\CiscoEapLeap.dll

Type ID: 25
PeerFriendlyName: @C:\Program Files (x86)\Cisco\Cisco PEAP Module\CiscoEapPeap.dll, -119

C:\Program Files (x86)\Cisco\Cisco PEAP Module\CiscoEapPeap.dll

Type ID: 43
PeerFriendlyName: @C:\Program Files (x86)\Cisco\Cisco EAP-FAST Module\CiscoEapFast.dll, -30119

C:\Program Files (x86)\Cisco\Cisco EAP-FAST Module\CiscoEapFast.dll

Repair procedure

[procedure]

Back up the registry keys (8086 and 9)
Delete the registry keys (8086 and 9)

When using this article as a reference, make sure you're using the correct key to delete.

Registry operations are at your own risk

Before working with Registry Editor
Make a backup copy of your registry in case something goes wrong.

As a result of the removal, only Methods> 311> Name: Microsoft became available.

Summary

How to deal with EventID2002 log.

Check the path of the driver logged
Consider deleting the registry key if the path is a non-existent or empty folder
Take a backup before deleting the registry key
... Self-responsibility ...

Intel driver bug?

2018/02/17

When updating the Intel driver, the value that refers to the Cisco folder (this time only creator ID = 9) was re-registered in the registry, and the error in the event log was recovered.

Be careful when updating the Intel driver.

The following drivers.
Intel (R) Dual Band Wireless-AC 7265

Validation: Windows 10 Pro Fall Creators Update, v1709

：SC2