Right-click on Local Area Connection crashes Explorer.exe

[keastland]

Hi, I'm having an issue with a computer that is proving to be a pain in the arse.

This laptop is getting a default IP of 169.x.x.x and I am unable to access our network and/or the internet from it. When I go to check the network properties, as soon as I right click on the Network connection Explorer.exe crashes... unless I disable the network device first.

I have run both Malwarebytes and SuperAntiSpyware, which found and removed some tracking cookies, but that's it. I've also run CCleaner which didn't appear to help at all.

I have also logged in in Safe Mode but the issue is present then too.

I'm considering doing a Windows Repair as my next option, but wanted to see if anyone has any idea's first.

Thank you in advance.

 

[Stratos]

Which version of Windows?

 

[keastland]

I should've probably mentioned that this laptop is running Win7 Ultimate.

I also just found out that even when I can actually get into the properties of the connection (with the device disabled) if I click on the Sharing tab, Explorer.exe crashes and prompts me to restart the program.

After that happens, I get a pop-up that Windows Help and Support can't start.

This certainly appears to be some sort of Adware/Spyware problem, but the software I'm using isn't finding anything and the issue is happening in Safe Mode also.

 

[keastland]

Which version of Windows?

Sorry, I was entering that as you asked.

32-bit with 2 Gb's of memory also.

 

[Stratos]

Does the problem only occur when you right click on Local Area Connection or does it crash when you right click anything else?

 

[keastland]

Does the problem only occur when you right click on Local Area Connection or does it crash when you right click anything else?

I've only had it happen on the network connections so far. Since I found older Google hits on similar issues, I've tried right-clicking on the desktop, but that works as it's supposed to.

I tried a couple other random ones (random program shortcut and right clicked on "Computer") and both worked as they should.

Thank you.

 

[keastland]

Oh! I forgot... I can't get into look at the Event Viewer either. I get a pop-up that says, "Event Log service is unavailable. Verify that the service is running." This is both in normal and Safe Mode. When I try to start that service (Windows Event Log) I get another pop-up; "Windows could not start the Windows Event Log service on Local Computer. Error 1747: The authentication service is unknown."

 

[James Colbert]

Hello Keastland. Welcome to the forums.

Try solving the Event Viewer problem first. Here are a few links that should help:

Try this one first, as the proposed solution is packaged as an article, making it easy to follow. The winsock reset seems to resolve the issue for many:

Repair and Reset Windows Vista TCP/IP Winsock Catalog Corruption » My Digital Life

These other links contain a few different solutions and also include the solution in the first link:

Event Viewer Service problem

Unable to start event viewer/event log service on vista - Error 3

Fix for Event Log Service Startup Error 1079 - The Winhelponline Blog

And a google search:

Event Log service is unavailable. Verify that the service is running - Google Search

Again, follow the steps in the 1st link first. Create a System Restore point before making any changes.

If this works, see if your 'Right-click on Local Area Connection crashes Explorer.exe' issue is resolved.

If not, make sure your NIC is using the latest driver. Post back and let us know.

James

 

[keastland]

I tried a Startup repair, but that didn't find any issues. I'm now in the middle of a Windows Repair. Once that's finished I'll update with whether or not it resolved the issue and, if not, try the last advice.

Thanks for the feedback.

 

[keastland]

Looks like the Windows Repair did the trick.

As it turns out, the user has now told me that he was having an issue with a particular application when the issue started (love to find that out after I've gone to the extent of doing a Repair), so maybe UNinstalling/REinstalling that app might have worked. I'll never know now.

Thanks for the efforts.

 

[James Colbert]

Looks like the Windows Repair did the trick.

As it turns out, the user has now told me that he was having an issue with a particular application when the issue started (love to find that out after I've gone to the extent of doing a Repair), so maybe UNinstalling/REinstalling that app might have worked. I'll never know now.

Thanks for the efforts.

Full disclosure is a rare event.... Good that you got it sorted, anyway.

James