My problem is I get the above error and I don't even have Wi-Fi on this desktop. I also have WLAN disabled in Services an anything else that is wireless related.
That error will come accompanied by a LwtNetLog ID Error 3 also...they seem to be related.
What could cause this? W10 has stayed up to date along with everything else OS related.
Please Advise.
Something is trying to use it for something. You do not need to disable in Services, just disable in the Network Adapters in Control Panel.
If you show Hidden Devices in Device Manager, you should see a bunch of Virtual adapters for Hyper, which get created if you do not go into Windows Services in Programs and Features. The TAPI's are going to be both IPv4 and IPv6. Make sure that you make an update. Now if you want to check and see if Farbar's Service Scanner or Minitoolbox may work before diving deeper. Download from Publisher page for Farbar
okay...first of all I disabled Hyper-V in services when I first got W10 (8/2015) what I show in Hidden Devices is as follows:
MS Kernal Debug NetWork Adapter
Realtek PCIe GBE Controller
8-WAN mini-port adapters
they all when checking for updates state 'you have the most recent or up to date'
I don't use any 'telephony' and have that set to manual in Services..I don't integrate phone with the OS and don't plan to in the future.
as far as IPv4 an IPv6 go I only use IPv4....not sure what you mean by 'make sure you make an update'
I've tried Farbar, Hitman Pro, RogueKiller,TDSSkiller,Panda CloudCleaner...you name it I've tried it. I also have MBAM Premium running. I don't think it is malware causing the issue...then again I could be wrong...these days so many clowns screwing with things makes that a moot point
@ bro67 I appreciate you taking the time so thanks...what i have done is go to the directory C:/Windows/system32/log files/ WMI an delete all the log files that show up in the .etl errors and that seems to stop it for a little while but then something (the thing I'm trying to sniff out) triggers it again after a spell. It's a head scratcher.
Searching Kernel Event Tracing errors found the reason for the WiFiSession error...in Performance Monitor>Data Collector Sets>Startup Event Trace Sessions..I found WiFi Session was enabled thus giving errors on startup..disabling this feature stopped those errors.
Quote