Windows 10: Weird process running - "Monitor Virutal Wlan Service"

Appreciated but a tad technocal for this oldie!

At which location and which .inf file is this referring to?

Just checked device driver for Broadcomand there may be a problem:

Attachment 45813
most likely referring to the original pre-sale install of the operating system etc.

As of now and after several reboots to check stability, everything seems fine.

A quick check of the EVENT LOG shows a lot of Error occurences. For example:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

in the Window's System log (along with many similar).

Is there such a program that can be run to check the stability of a computer and its newish Windows 10 for any obvious errors/problems, missing problems, setting that are necessary or is that asking too much?

Cheers and thanks

 

Sorry about that. Bottom line is I don't think you have to worry. If all works with the service disabled leave it disabled.

However to answer your questions...

You have it in your third picture in post #5 but it is renamed from bcmwl63.inf to bcmwl63.inf.bak (for backup) for some reason. You can still look at it with notepad if you are interested.

I can't see that picture but the message in event viewer is nothing to do with drivers. At the risk of going off on a tangent is because Local Service doesn't have authority to the RuntimeBroker. You can tell this by scanning in regedit for {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}





It is an old problem (not new to Windows 10) and happens on clean install with no third party drivers installed.

I couldn't find a link but to fix it you can follow these steps. There is no real need to fix as it doesn't seem to cause any issue it but it makes the event viewer logs cleaner.

Take ownership of this registry key HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276} as described in option 4 step 3 here

Then go to control panel > administrative tools > component services.

Browse to Computers > My computer > DCOM Configuration > RuntimeBroker and right click. Then select Properties > Security tab, edit Launch and activation permissions then add LOCAL SERVICE and tick Local Launch and Local Activation.

Not really. that will help you with testing and fixing Windows corruption but will not help with drivers.

There are 3rd party driver checking utilities but I'd recommend not using them. If it works, leave it *Smile

 

Thank youhalasz. I am more timid than a hare when it comes to anything registry so I think I will give it a miss.

I have run SFC several times in the past during my Win 7 life time that enabled the resident Seven Forum experts to provide help. I will give that a whirl during the week.

Again, thanks for your generous help.

 

Just an update, should anyone be interested.

sfc /scannow

has been run successfully. Nothing untoward to report and no repairs done.

Thanks for your help.

 

Good evening. I thought I should follow up the earlier SFC with another run.

There were a number of problems but hopefully they are minor and most were fixed by the automated process.

Should anyone feel the urge to have a gander at the CBS file, I have zipped it as an attachment to this post.

Cheers, thanks and regards.

 

That looks fine Code: [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired[/quote] It is only if it says "Unable to repair" you have to worry *Smile

 

It is only if it says "Unable to repair" you have to worry *Smile[/quote]
Cheers! Couldn't find a "relief" smiley! *Smile

 

Here I'll give you one, just save as...