[Tripredacus]

Yesterday I integrated around a dozen MSU packages from Windows Update into a Windows 8 Pro x64 image. Of those that were integrated (confirmed via DISM) these updates still show up as being offered after checking for updates:

KB2727528
KB2771431
KB2772501

Anyone else find this behaviour?

[ner]

Tripredacus, on 04 January 2013 - 09:38 AM, said:

Yesterday I integrated around a dozen MSU packages from Windows Update into a Windows 8 Pro x64 image. Of those that were integrated (confirmed via DISM) these updates still show up as being offered after checking for updates:

KB2727528 - yes can be injected
KB2771431 - no cannot be injected
KB2772501 - no cannot be injected


Anyone else find this behaviour?

[gotenks98]

One is an executable type update and the other is just online only because its an update to the service stack, kind of how SP1 was to Windows 7. I really wish microsoft would post something to let us know what updates are integrateable or not. I spent 2 days trying to figure this out.

[cluberti]

Are the files that shipped with the updates still older versions on disk after you've installed Windows 8? For example, 2727528 updates synceng.dll to either .16432 (GDR) or .20533 (LDR) - what version is on disk after you install Windows 8 at that point? If it's older, you might want to check the cbs.log to see why those updates didn't apply during staging.

[MagicAndre1981]

Update KB2772501 is an exe, so you can't integrate it. KB2771431 is a servicing stackupdate which can't be integrated.

[Tripredacus]

cluberti, on 04 January 2013 - 01:30 PM, said:

Are the files that shipped with the updates still older versions on disk after you've installed Windows 8? For example, 2727528 updates synceng.dll to either .16432 (GDR) or .20533 (LDR) - what version is on disk after you install Windows 8 at that point? If it's older, you might want to check the cbs.log to see why those updates didn't apply during staging.

Both the synceng.dll files (Syswow64/system32) show as having a file version of .16384.

@Andre there must have been some error along the lines in our documentation process and we didn't even download 2771431.

[MagicAndre1981]

if the file version is 16384, the update was never integrated correctly. Look into the DISM and CBS.log for errors.

[Tripredacus]

MagicAndre1981, on 07 January 2013 - 10:11 AM, said:

if the file version is 16384, the update was never integrated correctly. Look into the DISM and CBS.log for errors.

The logs on the deployed OS, or on the system I used to integrate the update?

[MagicAndre1981]

the logs from the PC where you integrated the Updates.

[cluberti]

Actually, both - I've seen updates that will stage correctly offline, but won't install online due to many issues. So yes, please check where they were integrated, but also check the cbs.log file on the deployed PC as well to see if anything happened there of interest as well.

[MagicAndre1981]

interesting, I've never seen this.

[Tripredacus]

I looked in all the first boot logs (on the client machine) and only one of the various "setupact.log" files actually has the KBs listed in it... KB2727528 was not anywhere in the log file.

See the attached excerpt. I believe I got everything relevent from the Technician Computer's DISM.log.

[MagicAndre1981]

you've uploaded a Win7 log. I can see that you're using a winpe. What has this to do with Win8 updates?

[Tripredacus]

MagicAndre1981, on 09 January 2013 - 01:32 PM, said:

you've uploaded a Win7 log. I can see that you're using a winpe. What has this to do with Win8 updates?

My mount point is in a folder called winpe_x86. I should have noticed the time stamp in the logs I found. See this new attachment for the Windows 8 logs.

Attached File(s)

•  DISM_KB2727528.txt (17.68K)
  Number of downloads: 3

[MagicAndre1981]

you are trying to integrate an Update which is for the release Preview into a RTM Image:

Quote

2013-01-04 07:03:39, Info CBS Appl: detect Parent, Package: Package_for_KB2727528_rp~31bf3856ad364e35~amd64~~6.2.1.1, Parent: Microsoft-Windows-Client-Features-Package-shell~31bf3856ad364e35~amd64~~6.2.8400.0, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2013-01-04 07:03:39, Info CBS Appl: detectParent: package: Package_for_KB2727528_rp~31bf3856ad364e35~amd64~~6.2.1.1, related parent found: Microsoft-Windows-Client-Features-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384, which is not real parent

2013-01-04 07:03:39, Info CBS Appl: detect Parent, Package: Package_for_KB2727528_rp~31bf3856ad364e35~amd64~~6.2.1.1, disposition state from detectParent: Absent
2013-01-04 07:03:39, Info CBS Appl: Evaluating package applicability for package Package_for_KB2727528_rp~31bf3856ad364e35~amd64~~6.2.1.1, applicable state: Absent
2013-01-04 07:03:39, Info DISM DISM Package Manager: PID=3892 TID=3100 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error

and this fails

[cluberti]

Heheheheh - good catch.

[Tripredacus]

Ahhhh that explains why KB2785605 didn't go in either. I'll have to keep watch for those little "-rp" in the file name.

[MagicAndre1981]

yes. But because the RP expires next week, there will be no more RP updates. So you don't have the issue again.