Ah thanks, this log is more helpful than windowsupdate.log. The problem with my installation seems to be caused by a driver file, wdmaudio.inf: Code: 2012-10-11 00:01:44, Info CBS INSTALL index: 11, phase: 2, result 13, inf: wdmaudio.inf 2012-10-11 00:01:44, Info CBS Doqe: Recording result: 0x8007000d, for Inf: wdmaudio.inf 2012-10-11 00:01:44, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2012-10-11 00:01:44, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
Run Code: DISM /Online /Cleanup-Image /RestoreHealth to restore the corrupt data and now try to install the updates again.
I tried installing the three updates manually on a Server 2012 installation after a failed update through WSUS, and always ended up with the same error, 0x800f081f (CBS_E_SOURCE_MISSING), indicating the updater can't find a file required for patching. %systemroot%\logs\cbs\cbs.log shows errors such as: Code: 2012-10-12 00:45:32, Error CSI 00000012 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #1223# from Windows::ServicingAPI::CCSITransaction::AddCatalog(Flags = 0, CatalogPath = [101]"\\?\C:\windows\CbsTemp\30255106_498887889\Package_2_for_KB2764870~31bf3856ad364e35~amd64~~6.2.1.0.cat")[gle=0x80070002] (missing file highlighted). Extracting the update package .cab from the .msu, and then the update files from the .cab (wusa.exe updatefile.cab /extractir) extracts all the files from the package, but something seems to cause it to not copy all of those files into the "CbsTemp" directory when running the update installer. I'm sure there's a better way to do this (installing a package from the extracted files, perhaps?), but what I did then was to start the .msu installation, watch CbsTemp for the newly created (randomly named) temp folder, and paste all of the extracted package files into it. If you manage to do this before the installer attempts to read the files, it will find the required files and install the package. This of course was for an installation error during "online" install, but if integrating the update fails because of the same issue (look through cbs.log) it may help for that as well.
I doubt the driver files are corrupted. It's the update that hasn't been tested thoroughly enough and is now causing problems. Still, I ran dism /Online /Cleanup-Image /ScanHealth and it didn't find any corruptions.
Scanhealth is better to use that restorehealth. If you use scanhealth it tells you whether it is corrupt or not, then you can dealt with it. If you use restorehealth it will always say that the component store corruption was repaired, even if there were no fixes required.
I took your advice Paul and did a clean install today. I was then able to activate and install all available updates without any errors. I noted that the updates installed much faster too. My previous version was the original RTM version that surfaced in early August. I have continued to use it since I installed it on August 6th. That is until replacing it with the MSDN version today. Thanks for the suggestion.
Had my fill of this lousy KB2756872 now, have spent many hours over the past couple of days/nights trying to get it installed. After trying umpteen things (see previous posts), I finally bit the bullet and backed up my system, quick formatted my boot drive and did a perfectly clean install of Win 8 Pro and restored activation. Legit RTM ISO - hash checked, and legit activation (as was previously). So, a perfectly clean install, no software installed, and not dual booting this time, all I did was disable UAC. Applied the lousy update and still got exactly the same scenario as in my previous posts, still failing at 98% !!! I've seen others post of the same thing in that MS answers thread, clean install and it still fails, therefore it seems obvious that there are serious issues with this update. Restored drive and won't be going near it again until a fix is known, far too many hours spent messing around trying to get it installed! Edit: Been running Win 8 Pro since RTM. Never had any problem until this update.
I think is better for you if you don't install this update.I have this update installed in my machine,beside others and I did no see major bugg fixes,improvements or this kind off stuff.So don't install it if buggy.My opinion.
Every update installed on all 5 of my Installs... UAC is not a problem, all metro works, all Activated, some with legit KMS others with FAKE KMS, others done a different way. I do truly wonder what else you have that is NOT PROPER ... I am using MSDN RTM - WZOR Leaked, Enterprise and Pro, x64 and x86.. I see very little difference.. but wonder "what else you have that is NOT PROPER".
Nothing friend - nothing! 'Legit RTM ISO - hash checked, and legit activation... So, a perfectly clean install, no software installed' If you have looked back through the last few pages and other forums, it's blatantly obvious that lot's of ppl have problems with this update. As previously mentioned the 98% failure mark also seems quite common. You can read of other ppl having done clean installs and the update still fails. Because it worked on 5 installs for you doesn't mean that all those who it fails for have something NOT PROPER! Perhaps all of these and many more all have something that is NOT PROPER! It's a non issue for me now anyway, won't be touching it again until I have something more positive tempting me to try it again.
I keep getting the following errors: Code: Update for Windows 8 for x64-based Systems (KB2768703) Installation date: 10/12/2012 6:06 PM Installation status: Failed Error details: Code 800F081F Update type: Important Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer. and this Code: Update for Windows 8 for x64-based Systems (KB2756872) Installation date: 10/12/2012 6:07 PM Installation status: Failed Error details: Code 800F081F Update type: Important Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
Does not mean the cert problem wont occur during KB2756872 install, because the fix is not applied until after reboot (by then its too late) Its just a guess...BTW it can be tested by installing KB2749655 before you install KB2756872 see if you get the same error
The advisory states that problems arise when specific certificates expire. It also says that the earliest date those certs expire is Nov 2012, so the update shouldn't have any effect until then.
On the microsoft answer thread of the problem.. someone managed to successfully install KB2756872 by uninstalling the audio driver first, then apply the update give it a try
I have installed KB2756872 successfully on Windows 8 Professional x64. The installation is configured with manual tweaks. Group policies, Services and SRP are adjusted according to my needs. Some features have been added/removed. I wasn't expecting a successful update due to these customizations, but it get installed successfully. The only thing I don't have used is third party drivers. Except Nvidia GeForceM 306.297 Winx64 driver, all other drivers are MS default drivers. This may be the reason of successful update of my installation.
Tried it. Now the "Installed Updates" shows 2756872 as installed. Windows Update still wants to install it but now it's 7MB and it fails. Too weird.