omg, I think I finally fixed it. Errors and slow boot on Win 10 with APS

[Jimbo93]

Reference this thread for my previous pain now gone (i hope): https://forum.avast.com/index.php?topic=233236.msg1541584#msg1541584

My WMI repository had issues. Not easy to tell actually. And it may have been caused by a WMI repair tool. I had fixed every thing else that it could possibly be. Just now the Avast Premium Security Install and first boot was flawless. Thats a very good indicator. Plus with WMI repaired I can now see other things working that I didn't even think were broke. The missing or broken stuff in the repository had to do with windows defender for the most part.

Here is the miracle script that fixed my repository. Recommended if you need it, and not easy to find. https://docs.microsoft.com/en-us/archive/blogs/fieldcoding/resetting-wmi-repository-dos-and-donts

I also found a great reference for fixing broken performance counters here that I thought Id share: https://xture.wordpress.com/2017/10/30/rebuild-performance-counters/

[DavidR]

It might be handy, to put a link to this topic/resolution at the end of the original topic.

[Jimbo93]

It might be handy, to put a link to this topic/resolution at the end of the original topic.

ok good idea. But I want to make sure I’m right this time. Should know later today.

[DavidR]

No problem, always worth waiting a little while to confirm.

[Jimbo93]

Apparently something is still not right. The windows error reports about disabled AV/AS are back. The NetTCPport sharing service doesn’t want to start up. It’s funny because these problems will just continue to worsen from previous experience. I will uninstall avast again and continue to troubleshoot WMI because I’m still getting a few strange log entries in WMI activity log. One is definitely associated with Avast. It is an event ID 5858 That reads: Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT * FROM Win32_Process Where Name=‘explorer.exe’ AND SessionId=‘1’;ResultCode = 0x80041032; PossibleCause = Unknown

[DavidR]

Might be best to continue in the previous topic and add the additional information.

Hopefully one of the Avast Team can pick it up and they may request logs of some sort.