System errors and warnings.

[Quantum]

I am having the following, are these something to be worried about? I would like to fix them if possible, can someone lead me in the right direction?

1. Kernel-event tracing, Event ID 2, category: session
Session "PerfDiag Logger" failed to start with the following error: 0xC0000035

2. DistributedCOM, event ID 10005, category: none
DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server:
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}

3. Application Error, Event ID 1000, category:(100)
Faulting application name: SetupAsusServices.exe, version: 1.0.4.0, time stamp: 0x609a3de1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x12cc
Faulting application start time: 0x01d76483f45eb8d6
Faulting application path: C:\Program Files\ASUS\ARMOURY CRATE Lite Service\MB_Home\SetupAsusServices.exe
Faulting module path: unknown
Report Id: cca615ef-d07d-421b-b85e-0497ec894fd1
Faulting package full name:
Faulting package-relative application ID:

4. DistributedCOM, Event ID 10016, Category: none
(lots of these)

5. User Device Registration, Event ID 360, Category: none
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.

6. Perfproc, Event ID 2002, Category: none
Unable to open the job object \BaseNamedObjects\WmiProviderSubSystemHostJob for query access. The calling process may not have permission to open this job. The first four bytes (DWORD) of the Data section contains the status code.

7. WLAN auto-config, Event ID 10002, Category: none
WLAN Extensibility Module has stopped.
Module Path: C:\Windows\system32\IntelIHVRouter08.dll

[plat]

I can make suggestions for a couple on your list.

For #7, try rebooting your router. Are you experiencing drops of your wireless connectivity? You can also check if there's an update for your network adapter.

For #4: these are usually nuisances more than anything. You can delete the offending GUID in the registry, just read the message box first. If it names a specific Windows process, leave it alone. Otherwise, I made a short YouTube video; it's very easy to eliminate most if not all. Just have a backup if you're not sure.

The other stuff you might search for on the 'net.

https://www.youtube.com/watch?v=EutJNEZ6Xms

https://downloadcenter.intel.com/product/59485/Wireless

[Quantum]

plat の投稿を引用：

I can make suggestions for a couple on your list.

For #7, try rebooting your router. Are you experiencing drops of your wireless connectivity? You can also check if there's an update for your network adapter.

For #4: these are usually nuisances more than anything. You can delete the offending GUID in the registry, just read the message box first. If it names a specific Windows process, leave it alone. Otherwise, I made a short YouTube video; it's very easy to eliminate most if not all. Just have a backup if you're not sure.

The other stuff you might search for on the 'net.

https://www.youtube.com/watch?v=EutJNEZ6Xms

https://downloadcenter.intel.com/product/59485/Wireless

Thanks for this, but not that I notice. I just checked my drivers for my adapters and it tells me everything is up to date. I have an intel-wireless ac 9260 and it's on version 22.40.0.7

[Bad 💀 Motha]

Many of those kinds of errors are also simply false.
Such as you having a fast OS startup via an SSD. Then a device is lagging to start because its all ready to go, but its software suite has yet to complete loading in the background; tossing up such errors in the event logs.

[Quantum]

Bad 💀 Motha の投稿を引用：

Many of those kinds of errors are also simply false.
Such as you having a fast OS startup via an SSD. Then a device is lagging to start because its all ready to go, but its software suite has yet to complete loading in the background; tossing up such errors in the event logs.

ah okay so just ignore them?

[Bad 💀 Motha]

First run these in Command Prompt and see if anything gets "fixed"

Search Box > CMD > click on Run As Admin

Then Command Prompt pops up, run these, one at a time.

CHKDSK /F /R
^Will require a reboot in order to run on C Drive.


SFC /ScanNow


DISM /Online /Cleanup-Image /RestoreHealth

[Quantum]

Bad 💀 Motha の投稿を引用：

First run these in Command Prompt and see if anything gets "fixed"

Search Box > CMD > click on Run As Admin

Then Command Prompt pops up, run these, one at a time.

CHKDSK /F /R
^Will require a reboot in order to run on C Drive.


SFC /ScanNow


DISM /Online /Cleanup-Image /RestoreHealth

i just did all of these, hope it helps thanks!

[Bad 💀 Motha]

For the last two, it should have said right on-screen if anything was corrupted and/or fixed.

To see if CHKDSK addressed any problems you'll have to review the Log within
Event Viewer > Windows Logs > Application
CHKDSK checks for and attempts to correct any issues with File integrity, bad sectors on drive, false reading of free space; etc.

SFC verifies and can address corrupted OS core files.

DISM can address issues with the BITS or WindowsUpdates services.

[Illusion of Progress]

I wouldn't hyper focus TOO much on every last entry that event viewer logs. You'll probably see "issues" on most PCs if you go about it that way. If you start having issues, then worry about something.