Windows 10: W10 Creators update Event viewer error Event ID 360

I have updated Windows 10 Pro to the Creators update. I have had a few event viewer errors which I managed to fix. But I don't know what this one is, I guess everyone is seeing it, does anyone knoe how is it resolved? Thanks.

"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
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."

:)

 

How can I find what was uploaded or downloaded on my computer?

Hi Dave, Good morning.

I checked the version of Windows in my PC, it is version 1703 build 15063.726. Can you please explain Falls Creator Update? Is there a way to check in the event viewer if it was the Falls Creator update? I will take another look in the event viewer to see
if there are any entries from Falls Creator.

Here are some event viewer details during the download:

-Successfully scheduled Software Protection service for re-start at 2117-10-23T23:02:33Z. Reason: RulesEngine.

-Received Scan fail

-The description for Event ID 0 from source dbupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.

　

If the event originated on another computer, the display information had to be saved with the event.

　

The following information was included with the event:

　

Service started

-The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Thank You Dave,

Paul

 

App Container profile failed with error 0x800700B7 because it was unable to register the AppContainer SID.

No you're not missing anything. The AppModel-Runtime Event ID 37 was introduced with the Creators Update and no one has a solution so far. The error is displayed twice on every boot even on a clean install. The only way to get rid of it is to disable the
AppModel-Runtime log in event viewer settings, but that's rather a workaround then a real solution.

The people who marked the reply as 'Solved' are simply ignoring it.

 

Only workaround if you are fine with it.
Managing Windows 10 Creators Update rollout for a seamless experience - Page 7 - - Windows 10 Forums