Windows 10: Event 360 user id ??

Description:
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.

<EventID>360

:)

 

Warnings with Event ID 200, 202 and 360 after a Windows update 1809...

After the latest Windows 1809 update I am getting these 3 errors/warnings in event viewer log on Windows Boot-up/Restart.

The Network List Manager reports no connectivity to the internet: Event ID 202
A connection to the Windows Update service could not be established Event ID 200

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.

Event ID 360



These are of-course harmless warnings but they started happening after some Windows 10 update. Actually, it happened when I freshly reinstalled Windows 10 Pro 2 weeks ago when I activated Windows 10 Pro with a genuine license. After installing Windows 10 Pro from the official website with the most recent 1809 update.

Ever since I have noticed these 2 warnings commonly appearing in the Event log.
The Network List Manager reports no connectivity to the internet: Event ID 202
A connection to the Windows Update service could not be established Event ID 200

Nothing is broken with Windows Update everything is running fine and I have no connection problems and I even port forwarded all the relevant ports, disabled Windows Firewall as an experiment, etc.

Can someone tell me how I can get rid off these warnings from appearing in event viewer on windows startup restart? They are really annoying even if they are just cosmetic errors.

- - - Updated - - -

I solved the damn problem! *Biggrin

For Event ID 360. Open Regedit go to this key - Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\{23b8d46b-67dd-40a3-b636-d43e50552c6d} and change the value for the DWORD "Enabled" to 0 from 1.

For Event ID 200 solution found from here. https://answers.microsoft.com/en-us/...79736f4?auth=1

Control Panel\All Control Panel Items\Programs and Features Turn Features On or Off and uninstall Microsoft XPS Document Writer, Internet Printing Client, Microsoft Print to PDF and Windows Fax and Scan.

Since I've done that upon restart/boot I no longer receive A connection to the Windows Update service could not be established Event ID 200

This also naturally fixed the The Network List Manager reports no connectivity to the internet: Event ID 202

That issue also disappeared along with Event ID 200. These seem to be interconnected. Basically these items are located in Control Panel\All Control Panel Items\Devices and Printers. When Windows Update fails to install drivers for these items maybe due to some corruption I don't know. This is what triggered those Event ID 200 and 202.

At first I tried to simply remove Microsoft XPS Document Write, Windows Fax, etc from Devices and Printers but that didn't work. But uninstalling them from Programs and Features Turn Features On or Off has solved the problem.

Now I have done several experiments and these warnings are no longer appearing in my Event Log Viewer!

 

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

 

ESENT Event ID 508,510 and 533 warnings in Event Viewer

Hello Summez,

We appreciate the time and effort you have put in to resolve the issue.

If the ESENT Event Ids have stopped logging in Event Viewer, we might be looking at a positive picture here. Also, certain Windows components were fixed after running SFC and DISM tools.

However, if you still see any issues, I suggest you to check if the same issue occur when logged in through a different Local Administrator user account.



Follow the steps mentioned below:

• Assuming that you are already logged on to your user account in Windows 10, click the Start button.
• From the Start menu, click your name from the top of the left pane.
• From the displayed options click Sign out.
• From the login screen, click to the different user account you want to switch to.

However, if you do not have a separate user account, I suggest you to create another Local administrator user account by referring to the Microsoft article here: Set
up accounts.

Write to us again, in case you need further assistance on the issue.

Thank You.