Update KB3000850 fails to install

C:>dir/a/b/s wiaek*

Interesting.  You are missing the one (and its subdirectory) in FileRepository (assuming mine mean anything).  And I suppose we should look at the lengths too as an indication of version and state.  This looks better when copied to Notepad with Wrap off but I have tried using Format: Code Block to try to make the wrapped lines here line up better.

Looks like we could have put a leading * on the dir/a/b/s diagnostic too.  With one we get some underscore matches that don't occur otherwise.

I really wish we knew how to decompress "compressed" SxS files or at least knew how to view .manifest files.  Judging by the 12642 lengths (do a  Ctrl-f for that to hightlight them) those could be the only ones we have to work with. 

I'm thinking that if the only difference is in that FileRepository, one option might be to put it there the same as mine and see if your symptom changes.  But why would it not be there and is this something that DISM should be able to repair for us?  It's not a .dll so I suppose that could be why SFC doesn't notice it.

I do have a Kodak Hero printer but I don't think I got an installation disk (do such things still exist?) as I'm pretty sure the software was downloaded from Kodak's website. It was updated a few months ago and there was a problem, it tried to install the printer again, it thought there was two but I managed to fix that.

Aha.  Then as another possible option, consider uninstalling it and see if that changes the problem symptom?

I'd forgotten it was "patch Tuesday", I notice in the important section KB3008925 performs a security update for flash player. Anyway, I managed to install all the updates, EXCEPT KB3000850 which failed with the same wiaek002.inf problem.

Good.  Let's use the new attempt's logging as diagnostics then.  Too bad we don't have a ProcMon trace to go with it.   <eg>

I think we may be making progress.

HTH

Robert

P.S.  Since you had a Flash update has DISM changed its CheckSUR report?  I had forgotten that we had been looking at that "corruption" too.

Hi Robert,

Here are the results:

C:&gt;dir/a/b/s wiaek*

C:\Windows\Inf\wiaek002.inf

C:\Windows\System32\DriverStore\en-US\wiaek002.inf_loc

C:\Windows\WinSxS\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6\wiaek002.inf_loc

C:\Windows\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242\wiaek002.inf

C:\Windows\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca\wiaek002.inf

As for do I need...

[Strings.0409]  

Provider="Eastman Kodak Company"

Location="Install Setup Disk"

I do have a Kodak Hero printer but I don't think I got an installation disk (do such things still exist?) as I'm pretty sure the software was downloaded from Kodak's website. It was updated a few months ago and there was a problem, it tried to install the printer again, it thought there was two but I managed to fix that.

I'd forgotten it was "patch Tuesday", I notice in the important section KB3008925 performs a security update for flash player. Anyway, I managed to install all the updates, EXCEPT KB3000850 which failed with the same wiaek002.inf problem.

Regards,

Richard

2014-11-24 14:08:50, Info                  CBS    Doqe: Recording result: 0x80070003, for Inf: wiaek002.inf

2014-11-24 14:08:50, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

That's nice but it isn't telling us where it is looking for it.   E.g. do this

C:&gt;dir/a/b/s wiaek*

I have a few of them, including something called  wiaek002.inf_loc  which by its name could be adding a whole different layer of indirection to look at.

This is why I would be using ProcMon to supplement all of the vague diagnostics that we are given.  We don't have access to the source or support documentation and so cannot read between the lines of this stuff.

Oh.  Do you need this?

BTW is this "patch Tuesday"?  Perhaps you should wait to see if anything has changed before trying any further diagnosis on stuff that is older than I had realized.   ; )

Good luck

Robert

Hi Robert,

Here is the extract from the CBS log for the original update error (this happened when the computer restarted to install the update):

2014-11-24 14:08:50, Info                  CBS    Doqe: Recording result: 0x80070003, for Inf: wiaek002.inf

2014-11-24 14:08:50, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2014-11-24 14:08:50, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2014-11-24 14:08:50, Info                  CBS    Perf: Doqe: Install ended.

2014-11-24 14:08:50, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2014-11-24 14:08:50, Error                 CBS    Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2014-11-24 14:08:50, Info                  CBS    Shtd: Rolling back KTM, because drivers failed.

... and below is the information from Event Viewer/Windows Logs/System for that timestamp of 2014-11-24 14:08:50:

Log Name:      System

Source:        Service Control Manager

Date:          24/11/2014 14:08:50

Event ID:      7023

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      computer

Description:

The Windows Modules Installer service terminated with the following error: 

The system cannot find the path specified.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7023</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2014-11-24T14:08:50.530840400Z" />

    <EventRecordID>68714</EventRecordID>

    <Correlation />

    <Execution ProcessID="656" ThreadID="7264" />

    <Channel>System</Channel>

    <Computer>computer</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Windows Modules Installer</Data>

    <Data Name="param2">%%3</Data>

    <Binary>540072007500730074006500640049006E007300740061006C006C00650072000000</Binary>

  </EventData>

</Event>

I assumed "PATH_NOT_FOUND" related to "The system cannot find the path specified."

However, I think someone else might have the same problem with wiaek002.inf, check out reply #37...

http://www.msfn.org/board/topic/173051-kb3000850-big-update-windows-812/page-2

However, I understand this didn't fix that persons problem entirely and do you think I'm barking up the wrong tree because the problem is somewhere else?

Hope this helps,

Regards,

Richard

... and for PS command dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue  | Where-Object -FilterScript {$_.FullName.Contains("flash")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Length FullName

---

       C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1

2242   C:\WINDOWS\WinSxS\Manifests\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1.manifest

       C:\WINDOWS\WinSxS\Temp\InFlight\214f9309b787cf0102000000a00c280a\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

       C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

2406   C:\WINDOWS\WinSxS\Manifests\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc.manifest

So as I suspected you have .manifest files only about Flash for that build version.  So DISM is being stupid IMO and should clean this up and not complain about it.  Certainly not a good reason to hold up an update if that is what is happening.  Unfortunately I don't know enough about the WinSxS file structure to know whether you can just eliminate the orphan .manifest and thus eliminate the problem.  I think it would help if we could just browse the .manifest (the way we used to be able to).

I agree that the DISM errors could be a red herring. Looking again at the original error which I found in the Event Viewer (in the Windows Logs\System) section:

    <TimeCreated SystemTime="2014-11-24T14:08:50.530840400Z" />

That doesn't look like the right timestamp.   I think you will need to look back further in the CBS.log (or relevant archived portion) within the correct timestamp context for more clues about the update failure.

HTH

Robert