KB2821895 Windows 8 x64 Update 06.11.2013 problem

Got the same results as you did I think

 

6-21 snipping tool shot and CBS and DISM logs are now at this link, too:

https://www.dropbox.com/sh/us3boba6essu21b/JMKQ7gA_Kj

 

Both commands completed. Scanhealth took about 4 minutes and found

no store corruption. Restorehealth command took about 10 minutes (total 32GB SSD

about 20GB occupied) and says it successfully repaired corruption.

 

So where are we now?

Obviously the 2821895 update caused some problems, at least for my Acer W510 tablet.

 

Not installing this update has left me with a clean or at least repairable system.

 

Is there any chance, Microsoft, that I will be able to use Windows 8 because its footprint

can be successfully reduced for a 32 GB mobile device, or at least this Acer W510?

 

That's still my question. You sold me Acer's device and the keyboard dock through your

MS Store. Hope I get to use it. Purchased tablet in November 2012 and keyboard dock in June

2013 just before patch Tuesday. Would like to continue forays to Starbucks for news, books,

and other computer activities. Thanks.

 

 

 

If you run sfc /scannow, does it report any corruption?

No. Ran sfc scannow twice with restarts inbetween. No integrity violations either time

Found this gem of a  tip on the eightforums.com in a tutorial on using scannow. Unfortunately,

didn't note the URL while I was copying. This text code does work and will extract info from your

CBS log on corruption repairs by sfc:

How to See and Read Only the "SFC" Scan Results from the CBS.LOG

NOTE: When SFC runs, it logs it's actions into the C:\Windows\Logs\CBS\CBS.log. The steps in this option will

show you how to see only the specific SFC entries with the [SR] tags in this CBS.log. This can be helpful to

show you what files SFC could not fix automatically if you wanted to try and manually replace them.

1. Open an elevated command prompt in Windows 8.
2. In the elevated command prompt, copy and paste the command below and press Enter.

NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the

CBS.LOG in it.

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

3. Close the elevated command prompt.
4. Open the sfcdetails.txt file on your desktop to see the SFC scan details in the CBS.LOG.
5. When finished, you can safely delete the sfcdetails.txt file afterwards if you like.

Tip

The import of the tutorial also stated that one runs sfc /scannow first until you get your

integrity violations fixed. May take up to three attempts with restarts inbetween.

Then if scannow can't fix it, run DISM /Online /Cleanup-image /Restorehealth and see if

that will cleanup store corruption.

Is that other people's understanding, that the proper order is run sfc /scannow first and then

if that does not work, DISM?

Thanks.

Are there any results to update on Microsoft KB2821895 and whether or not it is

safe to use?

Is the only proposed solution:

update KB2821895

run sfc /scannow

if indicates corruption, run: DISM /online /cleanup-image /restorehealth

and hope that works?

That's all for those of us who have had issues with the update?

Thanks

The problem with the upgrade mentioned has been confirmed.  But since the message below appears on two systems with the problem, it would seem to be highly unlikely all those components became corrupted overnight.  It would seem more likely the information/database the SFC uses to check the files was altered in some manner. 

I have repaired my system with the /RestoreHealth switch, so this post is basically just info.

From extracted SFC log:

"[SR] Committing transaction

[SR] Cannot commit interactively, there are boot critical components being repaired

[SR] Repairing 11474 (0x0000000000002cd2) components"