Login to Account Create an Account
Some integrated updates still being offered
Posted 04 January 2013 - 09:38 AM
Anyone else find this behaviour?
Posted 04 January 2013 - 10:03 AM
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?
Posted 04 January 2013 - 11:56 AM
Posted 04 January 2013 - 01:30 PM
Posted 04 January 2013 - 01:37 PM
Posted 07 January 2013 - 09:40 AM
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.
Posted 07 January 2013 - 10:11 AM
Posted 08 January 2013 - 09:45 AM
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?
Posted 08 January 2013 - 02:20 PM
Posted 08 January 2013 - 03:46 PM
Posted 08 January 2013 - 10:59 PM
Posted 09 January 2013 - 09:05 AM
See the attached excerpt. I believe I got everything relevent from the Technician Computer's DISM.log.
Posted 09 January 2013 - 01:32 PM
Posted 09 January 2013 - 02:16 PM
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.
Posted 09 January 2013 - 02:22 PM
2013-01-04 07:03:39, Info CBS Appl: detect Parent, Package: Package_for_KB2727528_rp~31bf3856ad364e35~amd64~~220.127.116.11, 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~~18.104.22.168, 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~~22.214.171.124, 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~~126.96.36.199, 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
Posted 09 January 2013 - 05:14 PM
Posted 10 January 2013 - 09:00 AM
Posted 10 January 2013 - 11:05 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users