Small issue after upgrading to creator's update

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Posts : 48
    win10
       #11

    Vaio 7 said:
    Hi,

    I fixed the issue, it does not cure the problem, until MS releases a hotfix BUT it prevents those entries from appearing in Event Viewer logs. Simply go to Regedit, (Admin), navigate to:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\{f1ef270a-0d32-4352-ba52-dbab41e1d859} and modify, to the right pane the "Enabled" value from 1 to 0.
    REBOOT.
    No more logging. Do the same for each GUID giving you an error or warning. Enjoy!
    I did not have to change any value in Services. Also, if in Event Viewer the error category is under "System" then navigate to:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System and do the same for the GUID giving you the problem. You can find the GUID if you see the Details view of the error, example:
    - System
    - Provider
    [ Name] Microsoft-Windows-AppModel-Runtime
    [ Guid] {F1EF270A-0D32-4352-BA52-DBAB41E1D859}
    EventID 37
    Version
    Level 2
    Task
    this works better then turning the log off it self, though there was no guid entry in the EventLog-System for me
      My Computer


  2. Posts : 95
    W7 x64 & W10 Pro x64 (Dual boot)
       #12

    tsunami2311 said:
    this works better then turning the log off it self, though there was no guid entry in the EventLog-System for me
    For me it was:

    - System
    - Provider
    [ Name] Service Control Manager
    [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
    [ EventSourceName] Service Control Manager
    - EventID 7000
    [ Qualifiers] 49152
    Version
    Level 2
    Task
    Opcode
    Keywords 0x8080000000000000
    - TimeCreated
    [ SystemTime] 2017-04-07T16:04:25.304980900Z
    EventRecordID 566
    Correlation
    - Execution
    [ ProcessID] 864
    [ ThreadID] 1060
    Channel System
    Computer
    Security

    - EventData
    param1 CldFlt
    param2 %%50
    I edited my previous post, the method I described was for Event id 37 and other Warnings I had in Event Viewer, for this particular error cldflt, I had to modify:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CldFlt and set startup type to 3. Now Event Viewer is clean...
      My Computer


  3. Posts : 25
    Windows 11 Pro x64
    Thread Starter
       #13

    Vaio 7 said:
    Hi,

    I fixed the issue, it does not cure the problem, until MS releases a hotfix BUT it prevents those entries from appearing in Event Viewer logs. Simply go to Regedit, (Admin), navigate to:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\{f1ef270a-0d32-4352-ba52-dbab41e1d859} and modify, to the right pane the "Enabled" value from 1 to 0.
    REBOOT.
    No more logging. Do the same for each GUID giving you an error or warning. Enjoy!
    Also, if in Event Viewer the error category is under "System" then navigate to:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System and do the same for the GUID giving you the problem. You can find the GUID if you see the Details view of the error, example:
    - System
    - Provider
    [ Name] Microsoft-Windows-AppModel-Runtime
    [ Guid] {F1EF270A-0D32-4352-BA52-DBAB41E1D859}
    EventID 37
    Version
    Level 2
    Task

    As for the Cldflt error, I modified:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CldFlt and set startup type to 3. No more errors or warnings of any kind...
    Doesnt this do the same thing that I said for event id 37 but through the registry?:)

    Looks like it just turns off logging to the event viewer just like if you would turn off the log in event viewer.
      My Computer


  4. Posts : 1,902
    Windows 10 Pro x64
       #14

    Lost my LifeCam-Cinema webcam with the upgrade............
    How can I get it back, it worked ok in the previous Win10..........?
      My Computer


  5. Posts : 4
    Windows 10 Pro x64 1703 / 15063 - Creators Update
       #15

    Vaio 7 said:
    For me it was:

    - System
    - Provider
    [ Name] Service Control Manager
    [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
    [ EventSourceName] Service Control Manager
    - EventID 7000
    [ Qualifiers] 49152
    Version
    Level 2
    Task
    Opcode
    Keywords 0x8080000000000000
    - TimeCreated
    [ SystemTime] 2017-04-07T16:04:25.304980900Z
    EventRecordID 566
    Correlation
    - Execution
    [ ProcessID] 864
    [ ThreadID] 1060
    Channel System
    Computer
    Security

    - EventData
    param1 CldFlt
    param2 %%50
    I edited my previous post, the method I described was for Event id 37 and other Warnings I had in Event Viewer, for this particular error cldflt, I had to modify:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CldFlt and set startup type to 3. Now Event Viewer is clean...
    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.
      My Computer


  6. Posts : 4
    Windows 10 Pro x64 1703 / 15063 - Creators Update
       #16

    Black Faith said:
    Doesnt this do the same thing that I said for event id 37 but through the registry?:)

    Looks like it just turns off logging to the event viewer just like if you would turn off the log in event viewer.
    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.
      My Computer


  7. Posts : 5,478
    2004
       #17

    alphamachina said:
    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?
    0-2 start at various times, 3 sets it to manual startup, 4 disables it.

    Small issue after upgrading to creator's update-capture.png
    Start
      My Computer


  8. Posts : 41
    Windows 10 Pro
       #18

    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.
      My Computer


  9. Posts : 5,478
    2004
       #19

    Sayjimwoo said:
    I set it to 3, so is that okay?
    Guess so. As Black Faith said earlier in post #4 it was failing on startup so not starting it is just the same.
      My Computer


  10. Posts : 4
    Windows 10 Pro x64 1703 / 15063 - Creators Update
       #20

    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.
    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).
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:59.
Find Us




Windows 10 Forums