2019-05-13T02:22:57Z kzstock [Event ID 2002] EapHost: Eapmethod DLL path verification failed. (SYSTEM) | Repair procedure
Scrap 2nd.
3

[Event ID 2002] EapHost: Eapmethod DLL path verification failed. (SYSTEM) | Repair procedure

1st:
2: 2019-05-13
Verification: Windows 10 Pro Fall Creators Update, v1709



The above image is a snapshot of the registry editor subkey Eaphost used to fix Event Viewer EapHost errors.


This post is about Event Viewer Message, Event ID 2002.

As a result of investigation, it turned out that it is because the setting which loads the driver of Cisco / Intel which does not exist in the personal computer is registered in the registry database.

Since I was able to repair, I will write down the details of the survey results and the repair method.

Event viewer message
messageSkipping: Eap method DLL path verification failed. Error: Type ID = 43, Creator ID = 9, Vendor ID = 0, Vendor Type = 0
Log nameApplication
SourceEapHost
Event ID2002
levelerror
usersystem


Example of an EapHost Error

I found that Eap method DLL path error was recorded 12 times in the event viewer of VAIO upgraded to Windows 10.

It is as follows when classified.

Eap method DLL path error
Creator IDType IDfolder
943, 25, 17C:\Program Files (x86)\Cisco
808623, 21, 18C:\Program Files\Intel\WiFi\bin

Example of error of type ID, creator ID
Skipping: Eap method DLL path verification failed. Error: Type ID = 43, Creator ID = 9, Vendor ID = 0, Vendor Type = 0

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

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

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

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

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


Event Viewer Snapshot

Event viewer

Cause of recording event ID 2002

The reason is that it is registered in the registry database to load the Cisco / Intel driver that does not exist on the personal computer.

Unfortunately, when using Windows 7, I did not check the Event Viewer at all, so I can not identify the cause of the upgrade to Windows 10.

Registry location

It is recorded in the following places.

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

Methods 9-Cisco

Registry value

The registry keys that referred to non-existent folders pertained to Intel and Cisco.

Intel / Creator ID: 8086
The C:\Program Files\Intel\WiFi\bin\folder did not exist in our 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 our environment, C:\Program Files (x86)\Cisco\folder exists but the contents are empty.

The registry was registered 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

Event ID 2002 repair procedure

Delete the registry keys (8086 and 9) referencing the non-existent folder after backup.

If you're reading this article and wanting to do the same thing, be sure to scrutinize the Event Viewer log to make sure you don't get it wrong.

Registry operation is at your own risk
Before operating the registry editor
Make a backup of the registry in case of unforeseen circumstances.

As a result of deletion, Methods> 311> Name: It became only Microsoft.

Methods: 311 Microsoft

Restart your computer and check the event viewer

After restarting the computer, I checked the Event Viewer and "Eap method DLL path confirmation error" is no longer recorded.

2018/02/17

It seems that the registry may be restored when updating Intel drivers.

When updating the Intel driver, the value that refers to the Cisco folder (in this case, Creator ID = 9 only) has been re-registered in the registry, and an error has been recorded in the Event Viewer.

The corresponding key has been deleted in Registry Editor.
Intel (R) Dual Band Wireless-AC 7265


end
次の投稿 前の投稿 ホーム

0 件のコメント:

コメントを投稿

にゃんつくばっと