Mon, Jul 15 2013 23:44
Beware of KB2821895
KB2821895 Windows 8 x64 Update 06.11.2013 problem - Microsoft Community:
As of July 15, 2013, this "servicing stack update" which used to be labeled as for Windows 8, RT *and* Server 2012 - and is now only labeled as a servicing update for Windows 8 and RT is still on the Microsoft download site.
Yet it clearly indicates in the KB known issues that it causes and issue with sfc /scannow
The following known issues may occur after you install update 2821895:
- The update may be displayed multiple times on the View update history page in Windows Update. However, the update was only downloaded and installed one time. This causes no issues.
- When you use the System File Checker tool to run the following command, you may receive an error message that states that there are corrupted files. The error message also states that you must restart the computer to repair the files.
To work around this issue, use the DISM tool to repair Windows
After you repair Windows, run the System File Checker tool again. If you still receive an error message that states that there are corrupted files, your system may contain corrupted files. In this situation, contact technical support
for more help.
If you want to deploy an operating system image after you install update 2821895, use the DISM tool to repair Windows
before you deploy the operating system image.
Furthermore, I have information that a IT consultant caught this on a Server deployment and it cause him to have issues deploying the RDS role on the server. Because the update is not uninstallable, he had to roll the deployment back.
The good news is the update is not offered up to Servers.
The bad news is that it's still there on Microsoft update, offered up -granted not checked, but for someone that manually checks for updates, they will get nailed.
Microsoft shame on you. You know this has issues. You clearly know this causes major issues with Servers, yet you leave it up there for workstations.
I realize you guys are busy with 8.1 but this is no way to treat customers. Pull this off of all deployment and get this thing fixed.
Filed under: Rants