Reliability Monitor Keeps Logging the same error everyday

Ali Abbas 1 Reputation point
2022-01-17T01:01:22.98+00:00

Hi guys, I am running out of options, I have googled regarding the error message shown below, tried everything everything I have read for this error and I am getting no where. If anyone can help me that would have great. This error message is getting logged everyday and I cant stop it, The closest I got to what this relates to is regarding updates, my pc functions and works fine, updates install fine. I have re installed the OS multiple times did a clean install by wiping the OS via a format of the nvme drive and then used a iso to do a clean install and the issue still happens. I have done in place upgrade and installed .net updates and again the error still occurs. I was on windows 10 this did not happen once, even when i upgraded to windows 11 (Clean install) this did not occur, this happend around last month (windows 11) when I looked in reliability monitor and saw the error, at first I thought nothing of it and removed it and it was from there it is just getting re logged everyday randomly at random times. Google has shown a few people on windows 10 with this issue but no fix, am just getting sick of this error, Please help. I believe a update may be the cause, because I have made zero changes to the hardware or software since last month and only have installed the updates windows has provided but cant figure out what the cause is.

Windows Modules Installer Worker

Problem signature
Problem Event Name: CbsPackageServicingFailure2
Stack Version: 10.0.22000.345
Package: Microsoft-Windows-Foundation-Package
Version: 10.0.22000.1
Architecture: amd64
Culture: unknown
Status: 800f0922
Failure Source: Execute
Start State: Installed
Target State: Installed
Client Id: DISM Package Manager Provider
OS Version: 10.0.22000.2.0.0.256.48
Locale ID: 2057

Extra information about the problem
Bucket ID: 2bd4f1668ad4845725de867551353e1f (1575844758057991711)

Specs: i9 9900k 32gb ram z390, gtx 1070 850 wat psu

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 39,916 Reputation points
    2022-01-24T09:03:25.937+00:00

    Hello AliAbbas,

    Thank you for your question and reaching out.

    I can understand you are facing issues with Reliability Monitor logging events.

    It can happen due to .Net framework updates which can not be update after you have in-place upgrade from Windows 10 to 11.

    I will suggest you to follow below steps which should be helpful in your case.

    Please check %windir%\Logs\CBS folder\ to check for potentially filename having this event.

    1. Run sfc /scannow
    2. Run below DISM command from elevated prompt to repair windows comonents.

    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth

    1. Disable any Antivirus program or Windows firewall you may have for temporary purpose.
    2. Cleanup below Temp folders
      C:\Windows\Temp\
      C:\Windows.old\
      %USERPROFILE%\AppData\Local\Temp
    3. Try to uninstall Microsoft-Windows-Foundation-Package from Control Panel -> Programs and Features

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Ali Abbas 1 Reputation point
    2022-01-24T21:23:30.237+00:00

    Thank you for your reply.

    I just wanted to say I have ran every dism command, I have ran SFC, all come back with no issues, I have cleared temp files re installed Dot Net files, addtionally I have reinstalled the OS multiple times using the fresh install method by formatting the entire nvme and re downloading the iso and starting from scratch and the issue is still present in every install. I have found the cause after doing multiple tests and by looking at the cbs.Log file there is something happeneing with defender and the Microsoft-Windows-Foundation-Package is trying to excute but it cant as shown in the original post. I disabled defender for 3 days, I did not get a single error, but soon as i re enabled defender the error comes back at random times but gets logged every day. As for the last statement you put which was to uninstall Microsoft-Windows-Foundation-Package, I am kinda shocked since you class yourself as a expert. I have lost some credability towards you because of this statement you made, offical Microsoft docmentation states Microsoft-Windows-Foundation-Package can not be removed or changed, it is part of the Windows features and gets installed when u install a fresh copy of windows OS, or when u re install windows on a new drive, it is not a program that is registered in uninistall or change program list, it is something that only gets installed when u install the OS, with the Microsoft-Windows-Foundation-Package you can only add addtional features or remove any addtional features u installed using DISM. The foundation cant be altered or removed, I have spent 3 weeks on this and the simple answers you provided, I have done on day one with no avail. If you can please take a look at my CBS log and tell me what is exactly happening with windows defender and how to solve it, I would be ever greatful. In my eyes i believe this is a bug with a current update, because prior november I had zero issues, it was in novmember I found the error log in relibility monitor, and since then its been loging everyday at random times, I have made zero changes to my software or hardware, everything is fully updated and exactly the same, also since I even bought a brand new NVME drive exact same as the one I allready own, and did multiple fresh re installs of the os, every install eventually gave me the error. I have added my CBS. Log please if you could assist me and tell what is defender moaning about I would be greatful.168016-cbs-error-log.txt

    Thank you regardless

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.