Anyone know why the KUC-State for KB2856657-v2 and KB2780342 still gets flagged as OK/INFO instead of REMOVE? Both of these fixes have been superseded so I would think OK/INFO would no longer apply. KB2780342 is needed to satisfy WU. Code: [KB#] [Version] [State] [Release Type] [Install Time] [Package Identity] [Language] [Filename] [Superseded] [SupersedingUpdates] [KUC-Type] [KUC-State] [KUC-StateRemarks] [NotInstalledSupersedingUpdates] 2856657 6.2.2.0 Install Pending Hotfix 7/22/2013 07:29 2856657 Windows8-RT-KB2856657-v2-x86.msu yes 2865658 OK/INFO Additional steps are required. You may have to change some registry entries. Look at the KB for details. New: 2013-07-10 0.5.8.279 Al
KB2873013 is the new one that komm/KUC had (along with KB2879488). KB2871318 was in the "Integrate to Installation Media" folder, but komm found that it causes errors during setup if certain drivers aren't found, so it's being moved to the main folder. I also added KB976002 for the sake of completeness. Repo Updated Added: KB976002 (Additional/Browser Choice for EU Users) KB2873013 (Additional/IIS) KB2879488 (IE10) Removed: KB2771770 (Additional/IIS) (superseded by KB2873013) Moved: KB2871318 from Additional/Integrate to Installation Media folder to main folder ------------- abbodi1406: Thanks. I knew you'd find that extra one in KUC.
I tried start /wait and still had the same problems. I wrongly assumed that RunOnceEx was the cause of this problem. Each of the subject fixes waits for the next fix to finish using RunOnceEX. After a few trials, it seems that the sequence order in which the fixes were installed was causing the problems that I encountered. If I chose to install KB2821895 before KB2770816 and KB2853772 via the SetupComplete.cmd, neither of the latter 2 would install. If I moved KB2821895 to be installed last, all fixes installed without any problems. Al
One of the main improvements listed for KB2821895 is that compresses unused files to free disk space. But since I never see that the huge Reserve.tmp file it creates is removed and due to all the install problems it seems to create, I'm tempted to do like NICK@NUMBER11 does and just use KB2771431 instead. Win8 went RTM August 1, 2012 and several updates were released within a week of that date. So we may start seeing them for Win8.1 very soon. Edit: I reviewed the repo's changelog and my comment above may be incorrect. The first confirmed RTM update I can find was built on Sept 1, 2012 (one month after RTM). The earlier updates listed in the changelog have long been superseded and are no longer offered by MS so I can't confirm that the four added on August 7, 2012 were for RTM or for a preview release (I wasn't helping with the repo back then).
Interesting.. New ServicingStack update will be released on tuesday: KB2871777 - Supersedes KB2821895
I suspect its in preparation for 8.1, for almost all servicepacks there has been a servicing stack update
I'm surprised MS hasn't already pulled KB2821895. Here's what I've seen with it: I had file corruption within Windows and couldn't repair it, so I recently formatted and re-installed everything. I then noticed Windows had corruption again within a day (HD had no problems). So I started testing things in VM installs. I installed updates in groups of ten, running "Dism /Online /Cleanup-Image /ScanHealth" after each batch to check things. All updates installed with no problems. I started checking other things. I ran "Dism /Online /Cleanup-Image /StartComponentCleanup"- still no problems. Then I did a defrag, and afterwards, I noticed the corruption again. After several more install tests (on both x64 & x86), I narrowed it down to this simple routine to produce corruption: 1. Install Win8 2. Install KB2821895 3. Run "Dism /Online /Cleanup-Image /StartComponentCleanup" 4. Do a defrag Then run "Dism /Online /Cleanup-Image /ScanHealth" to see the msg "The component store is repairable" (meaning there's file corruption). Note: I tried three different defrag utilities (including Windows' own) and all three caused the problem. Running "DISM /Online /Cleanup-image /Restorehealth" does repair things when only KB2821895 is installed, but it was unable to repair things when all updates were installed. The other issue with KB2821895 is that the huge Reserve.tmp file it creates never seems to be cleared. I'm looking forward to trying the upcoming KB2871777.