The description for Event ID 6062 from source Netwtw14 cannot be found

[KirillD]

I keep getting the following error in windows eventlog:

The description for Event ID 6062 from source Netwtw14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP4
Intel(R) Wi-Fi 6E AX211 160MHz

The message resource is present but the message was not found in the message table

I have latest intel drivers installed. Report from Intel System Support Utility attached. 

Any idea how to fix this?

[DeancR_Intel]

Hi KirillD,

Thank you for posting in the Community.

I appreciate your efforts for reaching out and providing details about your issue. I understand how frustrating it can be to deal with this error.

To assist you more effectively, could you please provide some additional information:

1. What are the current network settings on your device (e.g., 802.11a, 802.11n, 802.11b)?
2. Have you tried clean installation of the Wireless Driver 23.110.0? If not, here's the link for reference: Intel® Wireless Wi-Fi Drivers for Windows® 10 and Windows 11*. Follow the instructions here: Clean Installation of Wireless Drivers.
3. Was the Intel Wi-Fi 6E AX211 adapter pre-installed on your device, or did you upgrade to it?

Best regards, 

Dean R. 

Intel Customer Support Technician 

[KirillD]

1. What are the current network settings on your device (e.g., 802.11a, 802.11n, 802.11b)?

If you are referring to advanced properties of the device in device manager, it is set to 

"802.11 a/b/g Wireless Mode"

1. Have you tried clean installation of the Wireless Driver 23.110.0? If not, here's the link for reference: Intel® Wireless Wi-Fi Drivers for Windows® 10 and Windows 11*. Follow the instructions here: Clean Installation of Wireless Drivers.

Yes, did not help. My currently installed driver version is 23.110.0.5

1. Was the Intel Wi-Fi 6E AX211 adapter pre-installed on your device, or did you upgrade to it?

Was pre-installed

Thanks,

Kirill

[DeancR_Intel]

Hi KirillD,

Thank you so much for sharing all these details. I understand how frustrating this situation must be for you, and I truly appreciate your patience. I'll dig deeper into this issue on my end and will get back to you as soon as I have more information. If there's anything else you need in the meantime, please don't hesitate to reach out.

Best regards, 

Dean R. 

Intel Customer Support Technician 

[Blocky_Man]

Intel cant be bothered to fix their drivers.  Here is the solution for you

Re:Windows event logs for Intel wi-fi drivers are broken because of wrong registration of event files - Intel Community

[KirillD]

Hi Blocky_Man,

The post you provided indeed seems very relevant. Intel really should fix it.

As to the workaround provided, I am not exactly sure about a few things. The post is saying:

As a "quick fix" I've changed EventMessageFile to "%SystemRoot%\System32\netevent.dll;%SystemRoot%\System32\drivers\Netwtw14.sys"

and copied Netwtw14.sys to System32\drivers.

I am not 100% sure if I read this correctly.

Does it mean the suggestion is to edit Netwtw6e.INF in the directory associated with the relevant driver and then copy Netwtw14.sys from that directory to %SystemRoot%\System32\drivers? 

If so, should the driver be reinstalled after INF file is edited or windows will pick up those changes automatically?

Also, to me copying to %SystemRoot%\System32\drivers seems pretty risky. This may cause issues if the driver is later updated but I will forget to copy the new version again and who knows what would happen if drivers are mismatched. If anything, I would rather change the path in EventMessageFile to current location in the driver store, this way there will be no conflicts presumably.

What do you think?

Thanks,

Kirill

[Blocky_Man]

So fundamentally the problem is that the registry attribute telling Event Viewer the location of the Netwtw14.sys file is misconfigured and you therefore have two options

1) Change the relevant registry value as detailed in the linked post so that it has the correct path to the Netwtw14.sys file

or

2) You could make a copy of the Netwtw14.sys file a put it at the location that the misconfigured string specifies.

I took option 1 and changed the registry value.

[KirillD · Accepted solution]

So here is what I did, and it solved the problem for me:

1) Open event viewer and make a note of device mentioned in the problematic eventlog entry from source Netwtw14
In my case: Intel(R) Wi-Fi 6E AX211 160MHz

2) Open device manager and find the above device under Network adapters

3) Right click the device -> properties -> Driver -> Driver Details -> make a note of a directory name in front of \Netwtw14.sys
- Go to %SystemRoot%\System32\DriverStore\FileRepository\<directory name from #3>
Make sure Netwtw14.sys exists there and make a note of full path to Netwtw14.sys.
In my case:
C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_477c028818b7a796\Netwtw14.sys

4) Open regedit and go to
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\System\Netwtw14

EventMessageFile key should be present there and its data should look like this:
%SystemRoot%\System32\netevent.dll;%13%\Netwtw14.sys

5) Edit the data in the key EventMessageFile so it looks like this:
%SystemRoot%\System32\netevent.dll;<path from #3>
In my case:
%SystemRoot%\System32\netevent.dll;%SystemRoot%\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_477c028818b7a796\Netwtw14.sys

6) Reboot

7) After reboot check event viewer, events from Netwtw14 should now read properly

[DeancR_Intel]

Hi KirillD,

Thank you for getting back to us. I appreciate your engagement and the feedback you've provided. The steps we shared are part of the troubleshooting methods we typically recommend addressing the issue you're experiencing.

We generally advise against editing the registry, as it can lead to software instability and is more closely related to the operating system.  I will be closing this thread as the issue was resolved on your end.

Best regards, 

Dean R. 

Intel Customer Support Technician