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
    2014-12-29T23:52:56+00:00

     now fails on file prnekcl2.inf.

    Does this help?  <eg>

    PS C:\windows> ls -Re -Fi "*prnekcl*" sort LastWriteTime ft Length, FullName -AutoSize <br><br>ls : Access to the path 'C:\windows\CSC' is denied. <br><br>At line:1 char:1 <br><br>+ ls -Re -Fi "*prnekcl*" sort LastWriteTime ft Length, FullName -AutoSize <br><br>+ ~~~~~~~~~~~~~~~~~~~~~~ <br><br>    + CategoryInfo          : PermissionDenied: (C:\windows\CSC:String) [Get-ChildItem], UnauthorizedAccessException <br><br>    + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand<br><br><br> <br><br>Length FullName <br><br>------ -------- <br><br>   798 C:\windows\WinSxS\Manifests\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6.manifest <br><br>   277 C:\windows\WinSxS\Manifests\amd64_prnekcl2.inf-languagepack_31bf3856ad364e35_6.3.9600.16384_en-us_0ea2a2ee87da0783.manifest <br><br>   245 C:\windows\WinSxS\Manifests\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454.manifest <br><br>   222 C:\windows\WinSxS\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454\prnekcl2.inf_loc <br><br>   222 C:\windows\System32\DriverStore\en-US\prnekcl2.inf_loc <br><br>       C:\windows\WinSxS\amd64_prnekcl2.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_717bbf74093ca454 <br><br>  4544 C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e\prnekcl2.inf <br><br>  4544 C:\windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_5d5f2ed31b4e4a9b\prnekcl2.inf <br><br>  9841 C:\windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_5d5f2ed31b4e4a9b\prnekcl2.cat <br><br>  9841 C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e\prnekcl2.cat <br><br>   797 C:\windows\WinSxS\Manifests\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e.manifest <br><br>       C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e <br><br>  4544 C:\windows\Inf\prnekcl2.inf <br><br>  9476 C:\windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_5d5f2ed31b4e4a9b\prnekcl2.PNF <br><br>       C:\windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_5d5f2ed31b4e4a9b <br><br>  2140 C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6\prnekcl2.cat <br><br>    47 C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6\prnekcl2.inf <br><br>       C:\windows\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6<br><br><br> <br><br>PS C:\windows>

    Good luck

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-29T19:57:39+00:00

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-28T23:01:35+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-28T19:01:34+00:00

     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

    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