Small issue after upgrading to creator's update

alphamachina · 11 Apr 2017

Windows Hello has to do with Cortana. Have you disabled anything having to do with Cortana? I disabled Cortana in group policy, then did some tweaks with search indexing to remove web search, excluded some directories and rebuilt my index. Searches are much faster now. I'm thinking of disabling indexing all together, considering the directories I'm searching are much smaller than average.

At any rate, Windows Hello, from what I understand, has to do with the voice-activation and voice-biometrics of Cortana. It seems as if EventID 360 has more to do with checks and balances of whether or not Windows Hello is governed by Active Directory, any kind of group policy, or enterprise settings. I don't think it's anything to worry about.

Redbatman · 11 Apr 2017

I too have been getting the event id 37 errors too as well as event id 2 errors
Session "Microsoft.Windows.UniversalNotificationPlatform" failed to start with the following error: 0xC0000022
Anyone else get this too?

thearchitect · 11 Apr 2017

Redbatman said:

I too have been getting the event id 37 errors too as well as event id 2 errors
Session "Microsoft.Windows.UniversalNotificationPlatform" failed to start with the following error: 0xC0000022
Anyone else get this too?

I've got this as well, in addition to id 37 and id 2 errors.

Redbatman · 12 Apr 2017

I found the culprit for Event ID 2.
Uninstall Widows Update and Privacy from control panel.

thearchitect · 12 Apr 2017

Uninstalling Windows Update and Privacy stopped Event ID 2 from occurring for me, also seemed to restore boot times to what they were in AU (they seemed slower with CU up until the uninstall).

Vaio 7 · 12 Apr 2017

Sayjimwoo said:

I set it to 3, so is that okay?

On a slightly different topic, my Event viewer is completely empty now apart from one more error (below), I am using Windows 10 Pro and I am seeing this on every boot since installing the Creators Update.
I disabled the logging for it to remove it, but I am wondering if everyone else is seeing it?

EventID 360:
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.

Hi,

I was seeing that one too, but removed the logging.
I've already explained in my previous posts the way to prevent this event from logging in Event Viewer, event id 360
Simply modify a value in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger seek for the appropriate GUID and modify a value from enabled 1 to 0. Reboot pc and the error is gone.:)
Same applies for Kernel PnP Event id 219 events, ( The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM) and event id 37 (AppContainer profile failed with error 0x800700B7 because it was unable to register AppContainer SID).

JoeMcLutz · 12 Apr 2017

thearchitect said:

Uninstalling Windows Update and Privacy stopped Event ID 2 from occurring for me, also seemed to restore boot times to what they were in AU (they seemed slower with CU up until the uninstall).

Hi!
What's this "Windows 10 Update and Privacy Settings"? Is it safe to uninstall it?
Thank You.

Redbatman · 12 Apr 2017

JoeMcLutz said:

Hi!
What's this "Windows 10 Update and Privacy Settings"? Is it safe to uninstall it?
Thank You.

Its basically the program Microsoft installed on your computer before the creators update. It lets you change your privacy settings on what you wanted Microsoft's Telemetry to collect on you. Once you installed the creators update I believe you don't need it anymore. I went ahead and uninstalled it and so far things seem alright. Only worry is if Microsoft may do something.

But it got rid of the error so I believe you can go ahead and uninstall it.

JoeMcLutz · 12 Apr 2017

Redbatman said:

Its basically the program Microsoft installed on your computer before the creators update. It lets you change your privacy settings on what you wanted Microsoft's Telemetry to collect on you. Once you installed the creators update I believe you don't need it anymore. I went ahead and uninstalled it and so far things seem alright. Only worry is if Microsoft may do something.

But it got rid of the error so I believe you can go ahead and uninstall it.

Thanks Redbatman.

Hanzales · 14 Apr 2017

To get rid of the error in event log I have navigated to:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-User Device Registration/Admin]
and changed "Enabled" to "0"
:)