Windows 10: Event ID 12 ProvXML category 'PowerSettings' failed with '0x800706D9'

Hello all,

I have this error in the event viewer.
- what does this mean?
- is it a "real error" : should I be worried?
- how to solve (if needed)?

All is working well, as far as I can tell.

Thank you!

Kees




Event ID 12
Provisioning Diagnostics
ProvXML category 'PowerSettings' failed with '0x800706D9' at CSP node 'NULL'. Provisioning succeeded

EventData Message1 PowerSettings HRESULT 0x800706d9 Message2 NULL Message3 Provisioning succeeded

:)

 

computer failed to boot - disk error event id 153 + 98


Hi, suggest you try Hard Disk Sentinel (trial) - gives a great quick analysis (SSDs too).

Please post the results.

Event ID 153:
This event may be an indication that the specified drive may be failing soon. This is especially true if the event is recorded regularly. The first step is to run the maintenance utilities related to hard drives, starting with CHKDSK and the utilities available from the manufacturer for that specific brand.

Event ID 98:
Event ID: 98

 

Event ID 2

Well I did search for it on Google and that's one of the suggestions that came up. See: event id 2 Session "" failed to start with the following error: 0xC0000022 - Google Search

It's a bit complicated thought as it seems many things could trigger that error

 

Event ID 10016

Solved Numerous event id 10016 errors win 8 pro 64 bit

Here is the basic outline ...

1. Search the registry for the CLSID
2. Make note of the Default Value, which is the name (ex. ShellExperienceHost, RuntimeBroker) you're going to look for in DCOM
3. Change the Owner to Administrators
4. Give Administrators Full Control
5. Repeat steps 1-4 for the APPID
6. WinKey + s > type in component services > click on Component Services in list
7. Component Services > Computers > My Computer > DCOM Config
8. Change the View to Details
9. Find the name from step 2 (ex. ShellExperienceHost, RuntimeBroker)
10. Right Click on the Name > Properties
11. Select the Security Tab
12. Launch & Activation Permissions > Click Edit
13. Look for the offending user from the 10016 (ex. System, Local Service) and make sure it has the activation requested (ex. Local Activation). If the offending user does NOT exist, you have to add it and give it Local Launch and Local Activation
14. Click Apply
15. Close DCOM and Regedit
16. Reboot PC

Note: Make sure you understand the steps before doing them