This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After installation of optional update KB3022345, executing sfc.exe /scannow throws the following result message (see attached screenshot):
I can reproduce this on three different machines, all Win 8.1, all fully patched, they are a mix of 64 and 32 bit systems.
The error disappears on all my machines when I uninstall the KB3022345 update.
Moderators please feel free to move this message to an other board in case I posted this in the wrong one.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you for responding.
I appreciate you are trying to help me, but as I said in my opening post I 'fixed' this by uninstalling an optional update.
As this occurred on three different machines and could be corrected on all machines by uninstalling this update my guess would be there is something wrong with the update.
I was just offered this update from Windows Update today. I saw the size of the update and immediately was curious. I chose not to install the update at this time. Now I am wondering if it would be best not to install the update.
Herman,
This is most useful thankyou!
There are a couple of other threads here at the moment with other issues from recent Updates (WIndows "behaving intermittently" which was mine and Windows "Flashing" which was Caul72 from memory)
In my case running sfc.exe resulted in exactly the same issue as you report which is very frustrating when you are trying to fix an update problem!
Will investigate this further and remove said update.
Thanks
RichardJC57
I did write a quick fix guide (this will repair the issue if you want to keep the update)
http://thetechcookbook.com/windows-8-update-kb3022345-causing-corrupt-files/
The files must be become corrupt after the installation is complete, if the files were corrupt before hand they would not have been installed. This is where the Kernel Transaction Manager and Component Based Servicing (CBS) comes in, the job of KTM is to create the transactions (A transaction is all the file changes, creations, deletions etc (TxF) and any registry creations (TxR))-> apply the transaction -> if one tiny thing goes wrong/or is not correct with the transaction -> it will rollback. This of course is a very simplified definition.
Due to the integrity checks of Windows Updates the files would also not have been installed if the they did not have the correct SHA256-B64 hash, there is a check on each Windows Update file to make sure the hash matches what it is supposed to be.
As to why it is occurring, I dont have an answer for that, I am trying to reproduce this corrupt on my my own machine.
Thank you once more for your offer to help me getting this update to work!
In the KB description it is stated:
This update enables the Diagnostics Tracking Service in Windows 8.1 and Windows Server 2012 R2. This tracking service collects data about functional issues in Windows components.
It seems to me that the update installs some telemetry function, which could explain why you find corrupted telemetry-related files.
Before I started this topic I spent the best part of a day in hunting down this update as the culprit for the sfc error I showed in my opening post.
I think I can live without the telemetry function, so I am not very keen to spend more time on this.
I'd rather wait for Microsoft to address this.
