Some Windows users are reporting that their computer randomly locks up and they have to do to Hard Reset to get it back on track. When they did a bit of probing in the Event Manager, they saw “Session SenseNdrPktmon failed to start” message with error code 0xC0000035. In this article, we are going to see some ways to fix this error.
What is SenseNdrPktmon?
The error message SenseNdrPktmon failed to start with the following error 0xC0000035 is seen when folks open the Event Log on their Windows computer after experiencing issues such as the computer getting locked up or stuttering. SenseNdrPktmon is the Data/Session name. There are a lot of reasons that can cause the error and we will talk about them hereinafter.
What does Session SenseNdrPktmon failed to start mean?
It is a Network-related error that is seen in the Event Logs. It could be a corrupted WiFi Driver or Adapter or an issue with the NAT address. Outdated Printer drivers can also cause this error.
Fix Session SenseNdrPktmon failed to start error
Updating the Printer drivers as well as Network devices related drivers can help. Remove all Network Drives and change their NAT address and see if that helps. There are reports that the issues were caused by the NAT address being: 0.0.0.0 or 255.255.255.255 (by default). If this does not help, read on!
Start by updating your computer to the latest build of Windows. Sometimes updating alone can rectify the issue. But even if it doesn’t there is no harm in keeping your computer up-to-date.
These are the things you can do to fix Session SenseNdrPktmon failed to start error.
- Use Ethernet instead of WiFi or vice versa
- Run Network Adapter Troubleshooter
- Restart IPv4 and IPv6
- Run Network Reset
- Repair Windows System Image
Let us talk about them in detail.
1] Use Ethernet instead of WiFi or vice versa
The first thing you should do, if you can, is to change the way you use the Internet. If you are using WiFi, then use Ethernet. Whereas, if your system is connected to an Ethernet cable, connect it to WiFi. To do this, and check if the issue resolves.
2] Run Network Adapter Troubleshooter
The issue can be network-related, therefore, running the Network Adapter Troubleshooter can rectify the issue. Since we are not certain what exactly is causing the error, we need to do a few network troubleshooting and see if the issue is fixed.
First of all, run the Network Adapter Troubleshooter. You can follow the given steps to do the same.
- Open Settings by Win + I.
- Go to Update & Security > Troubleshooter and click Additional troubleshooter.
- Click Network Adapter > Run the troubleshooter.
Let the process complete and the issue will be fixed.
3] Restart IPv4 and IPv6
Next up, we are going to restart both the Internet Protocol version and see if that fixes the issue for you.
To do that, follow these steps
- Open Control Panel and click Network & Sharing Center > Change adapter settings.
- Now, right-click on the connected network and select Properties.
- Untick both Internet Protocol Version 4 and Internet Protocol Version 6.
- Restart your computer and reenable these services.
Hopefully, you are the issue will be fixed.
4] Run Network Reset
Next up try running Network Reset and see if it fixes the issue. To do that, open Settings, go to Network & Internet > Network Reset, and click Reset Now. Wait for the process to complete and check if the issue is fixed.
5] Repair Windows System Image
Finally, as mentioned earlier, the issue can be because of the corrupted system image. Hence, we have a command for you that can help in resolving the error. So, run DISM to fix the Windows System image and see if the issue persists.