Windows 10: 132G of windows event logs in 24 hours

Discus and support 132G of windows event logs in 24 hours in Windows 10 Ask Insider to solve the problem; Hello, I woke up to a disk space full error today. Looking through my files, I see that I have ver 100Gb of windows event logs. Any idea what could be... Discussion in 'Windows 10 Ask Insider' started by /u/Dfarni, Jan 7, 2020.

  1. /u/Dfarni Win User

    132G of windows event logs in 24 hours


    Hello, I woke up to a disk space full error today. Looking through my files, I see that I have ver 100Gb of windows event logs. Any idea what could be causing this, or even where to look?

    I'm getting a mix these 2 error types:

    Fault bucket 1949361935140419175, type 5 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 8007045B P2: 21 P3: 3 P4: windows.repositoryExtension P5: 10.0.18362.356 P6: 306 P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppXDeploymentServer_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppXPackaging_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-StateRepository_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppReadiness_Admin_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppReadiness_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-SettingSync_Debug_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-SettingSync_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-Store_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-WindowsUpdateClient_Operational_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\System_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\Application_6BD55AF1-9435-0006-2020-D66B3594D501.evtx \\?\C:\WINDOWS\TEMP\AppxErrorReport_6BD55AF1-9435-0006-2020-D66B3594D501.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD326.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD327.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB04.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB15.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_8007045B_e88675bb6aef1de62bcbd6d821fe149ee6146697_00000000_43c085f7-8dc5-4da3-85ea-14f7cc6cca92 Analysis symbol: Rechecking for solution: 0 Report Id: 43c085f7-8dc5-4da3-85ea-14f7cc6cca92 Report Status: 268435456 Hashed bucket: 5d7e0b0c956b180ddb0d865a12b67667 Cab Guid: 0

    and

    Fault bucket , type 0 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 8007045B P2: 21 P3: 3 P4: windows.repositoryExtension P5: 10.0.18362.356 P6: 306 P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppXDeploymentServer_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppXPackaging_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-StateRepository_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppReadiness_Admin_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-AppReadiness_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-SettingSync_Debug_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-SettingSync_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-Store_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Microsoft-Windows-WindowsUpdateClient_Operational_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\System_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\Application_6BD55AF1-9435-0003-13E7-D56B3594D501.evtx \\?\C:\WINDOWS\TEMP\AppxErrorReport_6BD55AF1-9435-0003-13E7-D56B3594D501.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER562E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER562F.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E0C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E1C.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_8007045B_e88675bb6aef1de62bcbd6d821fe149ee6146697_00000000_cab_ff22b643-1367-4e16-b21f-cd106c9be344 Analysis symbol: Rechecking for solution: 0 Report Id: ff22b643-1367-4e16-b21f-cd106c9be344 Report Status: 4 Hashed bucket: Cab Guid: 0
    submitted by /u/Dfarni
    [link] [comments]

    :)
     
    /u/Dfarni, Jan 7, 2020
    #1

  2. Windows 10. 12 to 24 hours

    Hi Sandra,

    Thank you for posting in Microsoft Community.

    To change the time format from 12 hour to 24 hour in Windows 10.

    Follow the steps:

    • Navigate to Control panel.
    • In the category view of the control panel, click on the
      ‘Change date, time, or number formats’.
    • Change the short time to HH:mm from the drop down.
    • Press Apply to make the changes.
    • Now your time format will change to 24 hour format.
    Hope this helps, let us know if you need further assistance.


     
    Rakesh Narayanaswamy, Jan 7, 2020
    #2
  3. Windows apparently froze, "gap" of 26 hours between event log entries

    Running Win10 Home 1709 build 16299.192.

    A couple of years ago, I built a desktop PC from components. Recently replaced the MOBO. Everything was running well for over 2 weeks. I've left it on 24/7 except for the occasional restart to update.

    Today I noticed that the monitor was showing no signal. All lights on the tower were normal. Tried to "wake" the system, but nothing happened.

    I turned the PC's power off and back on again, but there was no signal on the monitor, not even showing startup (BIOS) messages.

    This was about 20:00 (8pm) today (1/18).

    I swapped in a different monitor, which displayed the Windows logon screen.

    I swapped the old monitor back in, and it showed the Windows screen. This seemed very odd after it had not worked a few minutes before.

    Looking at Windows system log, there was an error saying the previous shutdown at 17:37 on 1/17 was unexpected. That was over 26 hours ago.

    Event log entries stopped at 17:24 on 1/17 (about 13 minutes prior to the reported shutdown). The last entry from 1/17 was event 19 from WindowsUpdateClient stating, "Installation Successful: Windows successfully installed the following update: 9WZDNCRFJ364
    Microsoft

    SkypeApp."

    The next earlier event was for the beginning of that installation.

    .

    There were no events logged between then and 20:02 today.

    I didn't find any dump files, either.

    Questions:

    • Any idea what happened?
    • Are there any places other than the event log that I can look for clues about what happened?
     
    VanKnowles, Jan 7, 2020
    #3
  4. 132G of windows event logs in 24 hours

    Windows apparently froze, "gap" of 26 hours between event log entries

    Hi Van,

    Based on your description, your wasn't properly working because when you plugged in a different monitor, it worked as it is. The reason why there are no event logs found in the span of 26 hours is that your
    CPU is up and running as expected. Windows event log is a record of a computer's alerts and notifications. Microsoft defines an event as
    any significant occurrence in the system or in a program that requires users to be notified or an entry added to a log.

    That being said, faulty monitors would not be detected to the event log. Changing your monitor is a step that you have made to isolate the issue. It means that the issue is just the monitor itself and not a system crash.

    Let us know if you have other concerns.
     
    Janeane Cru, Jan 7, 2020
    #4
Thema:

132G of windows event logs in 24 hours

Loading...
  1. 132G of windows event logs in 24 hours - Similar Threads - 132G event logs

  2. The screen on time is 24 hours.

    in Windows 10 Software and Apps
    The screen on time is 24 hours.: Hello. When I turned on my laptop today, I found that the screen on time was 24 hours. Last night I decided to turn off fast startup 1 time, holding down the shift. Tonight I found a very long screen on time. Tell me is it okay?...
  3. 24 hour clock

    in Windows 10 Gaming
    24 hour clock: The bug riddled Windows 11 cannot seem to even support a 24 hour clock. While civilians use the AM/PM the military uses 24 hour time. Windows 11 cannot so this so its time to stuff it in the stockade....
  4. 24 hour clock

    in Windows 10 Software and Apps
    24 hour clock: The bug riddled Windows 11 cannot seem to even support a 24 hour clock. While civilians use the AM/PM the military uses 24 hour time. Windows 11 cannot so this so its time to stuff it in the stockade....
  5. 24 hour clock.

    in Windows 10 Customization
    24 hour clock.: I am trying to change the format for time from AM/PM to using the 24 hour clock. I have gone to settings but this is not offered as an option for setting time display. How or can I make this happen?...
  6. 24 hour clock

    in Windows 10 Customization
    24 hour clock: I am using Windows 10 Pro and can't find the setting for using the 24 hour clock. I am getting only AM/PM. I work in the Fire/EMS/Rescue field and all our times are 24 hour based. Can anyone point me in the right direction? Thank you...
  7. 10 BSOD in 24 hours

    in Windows 10 Support
    10 BSOD in 24 hours: Windows version 1909, HP Spectre x360 Alright, so I should preface this by saying I know next to nothing about the internal workings of a computer. It took me over an hour to set up windbg, including having to figure out why the tutorial commands weren't working (TIL:...
  8. 24 hour clock

    in Windows 10 Customization
    24 hour clock: How so I change my clock to 24 hour time in windows 10 ? I am a nurse and I think and function in 24 hour clock time. Thanks https://answers.microsoft.com/en-us/windows/forum/all/24-hour-clock/29c261f8-f080-45c4-b623-c85ff5634165
  9. 24 hours - It was a long haul

    in Windows 10 Installation and Upgrade
    24 hours - It was a long haul: I bought a re-furbished tablet. Its a nice little guy made by ASUS. Its got a 10.5" screen and comes with an attachable keyboard. It was on sale for a price that I couldn't turn down. The 24 hours started this way. It came with a uninstalled "Windows 10 1607 14393.315"....
  10. Windows 10 – The First 24 Hours

    in Windows 10 News
    Windows 10 – The First 24 Hours: It has been an incredible 24 hours for Windows and our fans. We’re humbled and grateful to see the response to Windows 10. We have seen unprecedented demand for Windows 10, with reviews and customer feedback overwhelmingly positive around the globe. We are doing everything we...

Users found this page by searching for:

  1. Event Name: AppxDeploymentFailureBlue

    ,
  2. microsoft-windows-store_operational files

    ,
  3. Microsoft-Windows-SettingSync_Operational_