Windows update problem makes giant CBS.log probably languagepacks involved

From the explosive growth of my CBS.log file it turned out that something goes wrong with finding or installing (window) updates

The cbslog grows above 1 GB, sometimes within some hours, even if a new one is made (and the old one stored as CBSpersist_date). It seems to be caused bij some specific language modules.

My computer is a desktop, W8 on SSD (64GB), factory installed, HDD 2TB, memory 8 GB, core i7.

If i run SFC, than a set of files of 6 languages (packages in various KBupdates) is repaired. After that, the problems is away for some hours or a day, with only small additions to CBS.log. But then it explodes again, and grows within short time by 100's of MB. It seems to be related to new updates, which seem to be installed succesfully. Maybe the cbs explosion starts just by some routine check by the system (CBS?). The pc also seems to adjust windows during restart more than usual, not only after an update or SFC. But not always, so at some moments all seems to be ok.

It looks as if SFC must repair some language-specific components, i think even always the same languages (hu, fr, da, es , fi, nb). (SFC finishes all these repairs succesfully) .

You see these languages also appear frequently in the CBS.log -lines of before the SFC-run.

I don't know the exact procedures, but it seems that a number (or all) of the language-specific components or files for a task are checked one by one, to see if there's something new about them and if packages or maps to copy them from are present.

For the 6 languages that later sfc must repair, you often see a line parent found for (name file or map), State: absent.

For the other languages (if checked) the corresponding line is "no parent found, go absent".

Updatenames are also mentioned during one and the same CSB.log explosion several KBnumber are mentioned, although it seems KB2756872 is always involved, also when the event starts again some time after an SFC run. This KB2756872 is -according to update history, already installed since october 2012, so in the factory.

My question is: does someone recognize this (kind of) problem, and what is the solution?

Because as long as this is not solved, i can not make a basic image to restore to, as the underlying problem will be inhereted forever then...

I did not install any personal software yet, only the programs originally installed by the factory (as is W8, OEM, with recovery partition on hard disk).

Underneath I add some lines from the CBS.log. First the repairmessage of SFC (for 1 language, for the other 5 languages it is similar patron).

Then an axample of the 2 lines from CBS.log before running SFC, for one of the problem-languages. For comparition, also the same line for a correct' language.

In the end some lines about an invalid package, that are quite in the beginning of an "explosive" cbs-run.

(HResult= 0x800f0805 - CBS_E_INVALID_PACKAGE). Could this have to do with the problem, or can i neglect it?

SFC in CBS.log:

CSI 000006e9 [sR] Repairing corrupted file [ml:60{30},l:58{29}]"??C:windowsSysWOW64hu-HU"[l:46{23}]"windows.ui.xaml.dll.mui" from store

Earlier in the CBS.log, first 2 lines of a check for package 15 (fat is where the 2nd lines is different from the other ("good") languages):

(...) CBS Appl: detect Parent, Package: Package_15_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1, Parent: Microsoft-Windows-CoreSystem-Base-Package~31bf3856ad364e35~amd64~hu-HU~6.2.9200.16384, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present

(... ) CBS Appl: detectParent: package: Package_15_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1,parent found: Microsoft-Windows-CoreSystem-Base-Package~31bf3856ad364e35~amd64~hu-HU~6.2.9200.16384,state: Absent

For the correctly working languages (obviously...) e.g. package 14) the first line is similar, but the 2nd says:

(...) CBS Appl: detectParent: package: Package_14_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1,no parent found, go absent

The 3rd, fth and 5th lines per package are the same for fault and correct tested languages / packages:

(...) CBS Appl: detect Parent, Package: Package_15_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1, disposition state from detectParent: Absent

(...) CBS Appl: Evaluating package applicability for package Package_15_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1, applicable state: Absent

(...) CBS EvaluateApplicability, package: Package_15_for_KB2779562~31bf3856ad364e35~amd64~~6.2.1.1, Package applicability: Absent.

To finish my post, the lines about the ïnvalid package:

CBS Session: 30279046_1308985532 initialized by client WindowsUpdateAgent.

CBS Failed to internally open package. [hrESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

CBS Failed to OpenPackage using worker session [hrESULT = 0x800f0805]

I hope someone knows a bit more about the CBS processes and can lead me to some solution to the problem, or can tell me how to find out more myself....

View this thread