Windows 10: Small issue after upgrading to creator's update

So, is it startup type = 3 or as the OP said startup type = 4? Does it really matter? I guess anything above 2 but below 5 disables startup? Obviously, there would be at least 3 standard switches:

0 = off (startup disabled)
1 = normal/default (where default is usually /on/ but can be set to /off/ via other means [outside of registry])
2 = on (startup definitely enabled)

So what does 3 or 4 do? Enable startup but without error reporting? Or, are 3 and 4 not recognizable functions within the variable, so they confuse the system and it reverts to disabling startup anyway? Where did you guys get your information?

And even then, there's another function within the Cloud Files Filter service control set, "ErrorControl" which is set to "1" (on) Would disabling this (setting it to "0") disable error reporting but allow the service to run? I'm not willing to test that theory outside of a VM environment.

 

Seems more to me that it's completely stopping the service from running on startup, removing the chance for the error in the first place. Either that, or it's still running on startup, but the variable 3 or 4 causes it to startup without reporting errors, like a silent mode. The standard variable would obviously be 0 through 2, 0 being startup disabled, 1 being startup enabled, and 2 being startup enabled with an extra function? So, it stands to reason that the latter variables, 3 and 4, might be startup silently? Not sure.

 

0-2 start at various times, 3 sets it to manual startup, 4 disables it.



Start

 

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.

 

Guess so. As Black Faith said earlier in post #4 it was failing on startup so not starting it is just the same.

 

I'm getting this same error, along with a slew of others. I honestly have no idea what's up with this install. I built a brand new Z270X system with i7 7700K, 32GB RAM, Samsung 960 EVO 500GB system drive, a fresh install of Creators Update, and with only drivers and chipset drivers installed along with the basics like browser, etc. I've got a massive list of errors and warnings piling up. I'm an IT specialist and I've never seen anything like it. I'm getting paging errors for my system drive, even though my pagefile is managed by Windows.

Here are some:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Lexar&Prod_USB_Flash_Drive&Rev_1100#AA9EI30DGQMJFL5N&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

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

Activation context generation failed for "c:\program files\amd\cim\bin64\SetACL64.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",vers ion="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis

Display driver amdkmdap stopped responding and has successfully recovered.

An error was detected on device \Device\Harddisk4\DR80 during a paging operation.

Failed with 0x490 modifying AppModel Runtime status for package Microsoft.SkypeApp_11.13.133.0_x64__kzf8qxf38zg5c for user PC/USER (current status = 0x0, desired status = 0x20).

 

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.

 

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.

 

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

 

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,

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.*Smile
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).

 

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.

 

Thanks Redbatman.