Update KB3000850 fails to install

Hi Robert,

Sorry it's taken me a while to respond, been a bit busy.

Anyway, there has also been a separate Adobe Flash update today which I installed OK. I did try DISM again but, unfortunately, the same error still occurs (0x800f0906). I've checked my update history and it seems I do have KB2889543 installed.

Here are the results of PS C:\windows> dir -Re -Fi "*wiaek*" -Fo  -ErrorAction:SilentlyContinue  | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Length FullName
------ --------
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6
244    C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6.manifest
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242
383    C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242.manifest
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca
384    C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca.manifest
271    C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf-languagepack_31bf3856ad364e35_6.3.9600.16384_en-gb_267c72cf1ecb42a0.manifest
12642  C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242\wiaek002.inf
12642  C:\WINDOWS\Inf\wiaek002.inf
12642  C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca\wiaek002.inf
2020   C:\WINDOWS\WinSxS\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6\wiaek002.inf_loc
2020   C:\WINDOWS\System32\DriverStore\en-US\wiaek002.inf_loc

It does appear that I am missing the one in FileRepository (and it's associated subdirectory). Should I create this directory and copy in wiaek002.inf and try the update again?

Regards,

Richard

a separate Adobe Flash update today which I installed OK. I did try DISM again but, unfortunately, the same error still occurs (0x800f0906). I've checked my update history and it seems I do have KB2889543 installed.

KB2889543.  Flash modules at version level  11.8.800.174?  Was that a problem?...  Oh.  We haven't looked at that yet because we were ignoring FileVersion (because IMO it is being unreliably maintained).  And that update is very old so probably its modules have been compressed or archived so we can't use the Length as an identifier.  And I still don't know how to derive a package name from these "FullName" things that we are finding.  Wonderful.

Also, I don't know how this was distributed but apparently it represents an alternate source (somehow)?

http://helpx.adobe.com/flash-player/release-note/fp_118_air_38_release_notes.html

Still, the good news is that you can keep on going, ignoring DISM's concerns about Flash.   ; }

Try this pipeline for some clues about FileVersion.  FWIW I don't have anything anywhere near version 11.

In my case the ordering sort of makes sense, anything for version 15 came before version 16 and those are the only ones I have

. 

Here are the results of PS C:\windows> dir -Re -Fi "*wiaek*" -Fo  -ErrorAction:SilentlyContinue  | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Oops.  I have given you the sort keys we were using for the Flash problem.  It should probably only be  LastWriteTime.   Using Name for the Flash stuff was just an attempt to group the different module names usefully.  But with the new pattern including a leading asterisk that may be putting results in a less useful order.

It does appear that I am missing the one in FileRepository (and it's associated subdirectory). Should I create this directory and copy in wiaek002.inf and try the update again?

Is that the only discrepancy?  I imagine it would be a benign change but it would be nicer if we knew of an actual repair technique for this.  How did it get corrupted?

Have you considered uninstalling the Kodak thing to see if that would change your symptom?  Being absurdly optimistic it's possible that the uninstall would actually repair the damage.  However, I was only hoping that if the update had less reason to notice the damage that the update might go on and then you could hopefully redo whatever it was to install it before.   <eg>

HTH

Robert
---

Hi again Robert,

OK, here's the results of dir -Re -Fi flash* | Where-Object -FilterScript {$_.VersionInfo.FileVersion} | Sort LastWriteTime | select -ExpandProperty VersionInfo -Property FullName | ft FileVersion, FullName -AutoSize:

dir : Access to the path 'C:\WINDOWS\System32\LogFiles\WMI\RtBackup' is denied.
At line:1 char:1
+ dir -Re -Fi flash* | Where-Object -FilterScript {$_.VersionInfo.FileVersion} | S ...
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (C:\WINDOWS\Syst...es\WMI\RtBackup:String) [Get-ChildItem], UnauthorizedAccessException
    + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand


FileVersion FullName
----------- --------
7,0,19,0    C:\WINDOWS\SysWOW64\Flash.OCX
1.0.1.0     C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9\FlashUSB.sys
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\Flash.ocx
16,0,0,235  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_2705599f71aa2b43\Flash.ocx
16,0,0,235  C:\WINDOWS\SysWOW64\FlashPlayerApp.exe
16,0,0,235  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_2705599f71aa2b43\FlashPlayerApp.exe
16,0,0,235  C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl
16,0,0,235  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_2705599f71aa2b43\FlashPlayerCPLApp.cpl
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil_ActiveX.dll
16,0,0,235  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_2705599f71aa2b43\FlashUtil_ActiveX.dll
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil_ActiveX.exe
16,0,0,235  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_2705599f71aa2b43\FlashUtil_ActiveX.exe
16,0,0,235  C:\WINDOWS\System32\Macromed\Flash\Flash.ocx
16,0,0,235  C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_1cb0af4d3d496948\Flash.ocx
16,0,0,235  C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_1cb0af4d3d496948\FlashUtil_ActiveX.dll
16,0,0,235  C:\WINDOWS\System32\Macromed\Flash\FlashUtil_ActiveX.dll
16,0,0,235  C:\WINDOWS\System32\Macromed\Flash\FlashUtil_ActiveX.exe
16,0,0,235  C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17500_none_1cb0af4d3d496948\FlashUtil_ActiveX.exe
16,0,0,235  C:\WINDOWS\System32\Macromed\Flash\FlashUtil64_16_0_0_235_Plugin.exe
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_235_Plugin.exe
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerPlugin_16_0_0_235.exe
16,0,0,235  C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

I did uninstall my Kodak printer and tried again to install KB3000850 but still get the problem with wiaek002.inf, here is the extract from the CBS log:

2014-12-14 17:17:14, Info                  CBS            INSTALL index: 37, phase: 1, result 3, inf: wiaek002.inf
2014-12-14 17:17:14, Info                  CBS    Doqe: Recording result: 0x80070003, for Inf: wiaek002.inf
2014-12-14 17:17:14, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2014-12-14 17:17:14, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2014-12-14 17:17:14, Info                  CBS    Perf: Doqe: Install ended.
2014-12-14 17:17:14, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2014-12-14 17:17:14, Error                 CBS    Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2014-12-14 17:17:14, Info                  CBS    Shtd: Rolling back KTM, because drivers failed.

I also run dir -Re -Fi "*wiaek*" -Fo  -ErrorAction:SilentlyContinue  | Sort-Object LastWriteTime | ft Length, FullName -AutoSize (after uninstalling my Kodak printer), and here's the results:

Length FullName
------ --------
 12642 C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242\wiaek002.inf
   383 C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242.manifest
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242
 12642 C:\WINDOWS\Inf\wiaek002.inf
   271 C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf-languagepack_31bf3856ad364e35_6.3.9600.16384_en-gb_267c72cf1ecb42a0.manifest
   244 C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6.manifest
  2020 C:\WINDOWS\WinSxS\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6\wiaek002.inf_loc
  2020 C:\WINDOWS\System32\DriverStore\en-US\wiaek002.inf_loc
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_3295fc9bcf7ff3a6
 12642 C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca\wiaek002.inf
  2835 C:\WINDOWS\SoftwareDistribution\Download\c81c3f7fc84ac954c4736bb1c59de0fa\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca.manifest
   384 C:\WINDOWS\WinSxS\Manifests\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca.manifest
       C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca

Any other ideas?

Regards,

Richard

Hi,

I've scanned this thread real quick since I have the same problem.  All this troubleshooting you guys are doing looks very technical.  I think you could get a job as a programmer for figuring this out yourself if you do.

Unfortunately, it looks like this issue is common.  I see a lot of other threads in other forums about it.  Is there any chance that Microsoft is gonna take care of this and fix the update for us so we don't all have to dig through all those files?

I know it's only an optional update, but it's pretty substantial in size, and it seems to address some issues that I'm experiencing on my pc.  I would be a much happier user if I could just get it to work and know that I've done everything I can to make my computer work better.

 have the same problem

Which one?  The one that DISM thinks is a problem or the one that Richard wants solved?  Also, did you have a Kodak printer installed too?   <eg>

Probably best to start your own thread with your own details if you are looking for help.

Otherwise just keep waiting.  There will be another patch Tuesday to look forward to and perhaps it will change the symptoms again.

HTH

Robert
---

Well I must have missed something.  I thought the DISM problem was a part of the Richard's first issue in his original post.  I am getting the same failed installation of the same update.  It rolls the update back after the initial update restart, in the same way. 

I do have a Kodak printer installed but if there's any evidence removing it will work I missed that as well.  I don't want to get into a whole undoing/redoing of my computer until I see that it worked for somebody else. 

Hi Matt,

Well, a long time ago I WAS a programmer (but not on a PC) so I suppose it helps. I haven't run DOS commands since the early '90s with the introduction of Windows.

I also have a Kodak (Hero 7.1) printer and even uninstalled this and tried the update again, but it still failed with the same problem which is according to my CBS log file is to do with driver wiaek002.inf. I have made a bit of progress though. I created directory C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b and copied wiaek002.inf from c:\Windows\Inf into it. It got a bit further but now fails on file prnekcl2.inf. I found this out from this link msfn.org check out post #37, user youravinalarrrf seems to be having the same problem as us but it appears to be unresolved.

I will probe a little further and let you know of any further progress I make.

Regards,

Richard

 now fails on file prnekcl2.inf.

Does this help?  <eg>

Good luck

Robert
---

Hello again Robert,

I have good news. KB3000850 has successfully installed.

Firstly, here's my results of ls -Re -Fi "*prnekcl*" | sort LastWriteTime | ft Length, FullName -AutoSize :

Length FullName

------ --------
177291 C:\WINDOWS\System32\spool\drivers\x64\PCC\prnekcl2.inf_amd64_2ff0d71af23904e1.cab
  4544 C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6\prnekcl2.inf
  9857 C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6\prnekcl2.cat
   798 C:\WINDOWS\WinSxS\Manifests\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6.manifest
       C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6
  4544 C:\WINDOWS\Inf\prnekcl2.inf
   271 C:\WINDOWS\WinSxS\Manifests\amd64_prnekcl2.inf-languagepack_31bf3856ad364e35_6.3.9600.16384_en-gb_0719e7d08cb153be.manifest
   245 C:\WINDOWS\WinSxS\Manifests\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454.manifest
   222 C:\WINDOWS\WinSxS\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454\prnekcl2.inf_loc
   222 C:\WINDOWS\System32\DriverStore\en-US\prnekcl2.inf_loc
       C:\WINDOWS\WinSxS\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454
183409 C:\WINDOWS\System32\spool\drivers\x64\PCC\prnekcl2.inf_amd64_59438dc7ce792b20.cab
  9476 C:\WINDOWS\Inf\prnekcl2.PNF
  4544 C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e\prnekcl2.inf
  9841 C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e\prnekcl2.cat
  7968 C:\WINDOWS\SoftwareDistribution\Download\c81c3f7fc84ac954c4736bb1c59de0fa\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e.manifest
   797 C:\WINDOWS\WinSxS\Manifests\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e.manifest
       C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e

I checked my c:\windows\inf\setupapi log and found out that folder/directory prnekcl2.inf_amd64_59438dc7ce792b20 didn't exist. I created it and copied prnekcl2.inf from c:\Windows\Inf into it. I ran the update again and it spent ages on 30%, I feared the worst in that it was stuck in a loop. It eventually restarted and then completed to 100%. It then spent a while on the Seattle welcome screen with the small yellow exclamation mark but let me in eventually. Everything seems OK so far.

Thanks ever so much for your continued help.

Regards,

Richard