Update KB3000850 fails to install

Anonymous
2014-11-26T14:09:39+00:00

Hi there,

I have a problem installing update KB3000850. It downloads and appears to install OK until the computer restarts to complete the installation. It gets to about 8% of configuring windows updates and then I get the following message:

failure configuring windows

undoing changes

The computer restarts and is usable. I don't know a great deal about windows error reporting but I checked the C:\Windows\Logs\CBS\CBS log and found the following message:

CBS Failed installing driver updates [HRESULT - 0x80070003 - ERROR_PATH_NOT_FOUND]

I checked the Event Viewer and found the following message in the Windows Logs\System section:

Event ID: 7023

Source: Service Control Manager

The Windows Modules Installer service terminated with the following error:

The system cannot find the path specified.

I have no idea which path it cannot find. I have tried running the SFC and DISM commands and have tried the Windows Update Automated Troubleshooter but none of these seem to fix it. I understand there is a problem with the Avast anti-virus software but I am running Norton 360. I am using Classic Shell and am not sure if that is causing the problem but don't want to uninstall it if the error is being caused by something else.

Any help or advice would be most gratefully received.

Thanks in advance,

Richard

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

110 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-12-12T19:44:58+00:00

    All the other updates from patch Tuesday installed OK but, unfortunately for me, KB3000850 still refuses to install.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-12T19:58:40+00:00

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-13T00:06:54+00:00

    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.

    PS C:\windows> dir -Re -Fi flash* Where-Object -FilterScript {$_.VersionInfo.FileVersion} Sort LastWriteTime select -ExpandProperty VersionInfo -Property FullName ft FileVersion, FullName -AutoSize

    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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-14T17:54:53+00:00

    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

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-12-28T18:38:14+00:00

    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.

    Was this answer helpful?

    0 comments