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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-03-17T19:00:06+00:00

    Same problem & fix here too. I also used to have a Kodak printer on this installation of Windows. A Hero 5.1.

    Thanks to all who contributed to this thread.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-16T12:49:09+00:00

    Thx a lot guys, creating following folders

    C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b

    C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

    and coping following files from C:\Windows\Inf to these folder worked like a charm :D

    wiaek002.inf

    prnekcl2.inf

    PS:

    I also have a Kodak printer seems like Kodak is to blame for this.

    Thank you all for finding this fix. It was really beginning to annoy the ever living spit out of me that this update just kept failing. I used to have a Kodak Printer but I thought I'd un-installed everything from it... apparently this issue is a remnant.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-07T14:27:13+00:00

    Thx a lot guys, creating following folders

    C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b

    C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

    and coping following files from C:\Windows\Inf to these folder worked like a charm :D

    wiaek002.inf

    prnekcl2.inf

    PS:

    I also have a Kodak printer seems like Kodak is to blame for this.

    Also have a Kodak Printer. Fix above works great. Thanks

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-02-01T00:13:53+00:00

    Thx a lot guys, creating following folders

    C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b

    C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

    and coping following files from C:\Windows\Inf to these folder worked like a charm :D

    wiaek002.inf

    prnekcl2.inf

    PS:

    I also have a Kodak printer seems like Kodak is to blame for this.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-12-30T20:32:22+00:00

    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

    Was this answer helpful?

    0 comments