Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

KB2821895 update for Windows 8 causes System File Checker to hang, eats up resources

Share this post:
sfc_fehler_patchday_r1_c1

​During the June 2013 Patch Tuesday, which took place June 11th, Microsoft rolled out a high-priority non-security update KB2821895 via Windows Update. This “servicing stack update” was available for Windows RT, Windows 8, and Windows Server 2012. However, after installing the update, some users are experiencing some major resource consumption issues when it comes to the System File Checker.

After installing the update and running the System File Checker, the process hangs at 100% CPU utilization while eating more RAM than necessary. This process eventually ends after roughly 30 minutes and states that it was “unable to fix problems” while generating a large CBS.log file that repeatedly states “Cannot repair member file.” Microsoft has not addressed this issue just yet so we will have to resort to an alternative means to bypass this update since we cannot manually remove it.
In order to fix this issue, run the following command as an Administrator:
DISM /Online /cleanup-image /RestoreHealth
Source: Drwindows.de
Share this post:

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.