event ID error 14332 after todays updates

Hello all.

I have a bit of a head scratcher for the clever ones in relation to today's Microsoft updates (I think its connected).

Until I installed today's updates my system ran without any errors listed in the Event Viewer. Now I get the following.

Log Name: System
Source: Microsoft-Windows-WMPNSS-Service
Date: 27/03/2013 00:07:33
Event ID: 14332
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: AndyKeeble-PC
Description:
Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80004005'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMPNSS-Service" Guid="{6A2DC7C1-930A-4FB5-BB44-80B30AEBED6C}" EventSourceName="WMPNetworkSvc" />
<EventID Qualifiers="49165">14332</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-27T00:07:33.000000000Z" />
<EventRecordID>41558</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>AndyKeeble-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="ServiceName">WMPNetworkSvc</Data>
<Data Name="ErrorCode">0x80004005</Data>
</EventData>
</Event>

Has anyone else had the same problem?

I have Googled the Event but it is way above me i'm afraid. The only option I can see is to uninstall the updates but this doesn't seem the right way of dealing with it.

Andy

Well I'm no expert on this but I do see some things.
Are you the administrator? (0x80004005)
WMPNSS-Service is not starting. (Windows Media Player Network)

You could do this. It might help and won't hurt.

SFC /SCANNOW Command - System File Checker

This also might be fixed when you run sfc /scannow.

Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.

Layback Bear said:

Well I'm no expert on this but I do see some things.
Are you the administrator? (0x80004005)
WMPNSS-Service is not starting. (Windows Media Player Network)

You could do this. It might help and won't hurt.

SFC /SCANNOW Command - System File Checker

Thanks for this and running it as we speak.

Andy

Well like I said I'm not a expert on Windows Updates but if it doesn't fix your problem we have experts that will be along. Just hang in there.
--------
I do know what you mean. Some of the fixes include doing things in the registry and I'm not the one to guide you through the registry.

Layback Bear said:

Well like I said I'm not a expert on Windows Updates but if it doesn't fix your problem we have experts that will be along. Just hang in there.
--------
I do know what you mean. Some of the fixes include doing things in the registry and I'm not the one to guide you through the registry.

All help is gratefully received thank you.

SCANNOW done and no problems found so at least that's one box ticked!

Andy

Here is another option. Bring your computer back to a time right before the updates were installed. Restore Point.

System Restore

Layback Bear said:

Here is another option. Bring your computer back to a time right before the updates were installed. Restore Point.

System Restore

I decided against this as I have just downloaded and installed the latest NVidia drivers which, as you know, are a pain to sort out properly.

I have found a solution that gets rid of the event and that is to disable WMPNetworkSvc in services.msc.

Does anyone know what effect disabling that feature will have as I am a bit confused, its an age thing!

Andy

Windows Media Player Network Sharing service allows sharing your media library over a local network or the internet - if you're not doing this, you don't need that service.

Thank you cluberti for catching this thread. I have been gone for awhile. I do agree with cluberti; if your not using Media Sharing then disabling it should not hurt anything.

Well that's sorted then. Thanks to all who have replied and lets hope that Microsoft come out with an update that fixes this as I have found lots who have had the same problem.

Andy