Home > Uncategorized, Windows Forms > Windows 10 – KB3147458 – Windows update failure – 0x80070003 – ERROR_PATH_NOT_FOUND – FIXED!!

Windows 10 – KB3147458 – Windows update failure – 0x80070003 – ERROR_PATH_NOT_FOUND – FIXED!!

The Problem

I have numerous windows 10 machines and my desktop PC has started failing to apply the windows updates.

These two windows updates failed to install

  • Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3140743)
  • Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3147458)

Note: because of these issues I have set my windows update to notify and let me choose when to download and install

Setup Windows Update via Group Policy

The Symptoms

  • You are told there is a new update and you let it download and install.
  • Once completed you are asked if you wish to restart, so click restart
  • You are told that it is getting ready to install updates
  • In my case it gets to 3% and then reboots
  • Next it gives a message, “Cannot complete install. Undoing changes”
  • The computer reboots again
  • On login, you are told some udpates were unsuccessful

The Issue

In my particular instance this fixed the issue.

I first went and viewed the log file: C:\Windows\Logs\CBS\CBS.log
Depending on how long it has been since the error occured you may need to look for a file called “CbsPersist_20160425131704.log” where the number is the date/time of when the log file was created.

Open the file and search for “0x80070003 – ERROR_PATH_NOT_FOUND”

I found mine is a section as follows:

The issue is that one or more of the 16 drivers it is attempting to update has failed to be installed with a Path Not found error, but which one/s?

To find the details of the erroring driver update go to this file: c:\windows\Inf\setupapi.dev.log

Open this file and search for “Exit status: FAILURE”

I found the following, item of interest:

As you can see it is saying path not found in the FileRepository folder.
So I went looking and its right, I had no “capimg.inf_amd64_5a4379f63bea786c” folder!

The fix

In my case I have many other healthy windows 10 machines so I went and looked and sure enough they had the missing folder.

So I firstly copied the folder onto a usb key from the healthy machine.

There is a security issue with the FileRepository folder in that you will have no permissions on this folder.
To copy the “capimg.inf_amd64_5a4379f63bea786c” folder into the FileRepository directory you will need to go into the Advanced security and take ownership first. I am an admin on my PC, so I changed ownership to the Administrators group and then gave administrators full persmissions.

Once that is done you should be able to copy the missing folder into the FileRepository directory.

Next try to apply the update again and in my case it worked.

Windows10Update Success

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
Windows 10 - KB3147458 - Windows update failure - 0x80070003 - ERROR_PATH_NOT_FOUND - FIXED!!, 10.0 out of 10 based on 1 rating

Categories: Uncategorized, Windows Forms Tags:
  1. gl
    May 16th, 2016 at 02:13 | #1

    Thanks for the pointers, I’ve been battling the same issue (but with usbser.inf) for months, even spoke to MS about it but that went nowhere. setupapi.dev.log was the missing link for me, it shows that the version of usbser it thinks is current also does not exist in the FileRepository folder (but another version does).

    I fixed the last MS update that failed for the same reason by just nuking some suspicious usbser folders in WinSXS – that worked that time but failed again with today’s update. I never really knew what exactly the cause was.

    Looking in the registry, the ‘Active’ usbser driver (HKLM\SYSTEM\DriverDatabase\usbser.inf) is indeed a version that does not exist in FileRepository. As the update wants to update this driver, I won’t bother finding the missing version but will just change the registry entry to point at the one I have, and let it the update upgrade it. If it fails I’ll report back…

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  2. gl
    May 16th, 2016 at 02:24 | #2

    .. yep, it worked. My only FileRepository usbser.inf_… folder was usbser.inf_amd64_756afc9aa127e768, but the registry entry (corrected: HKLM\SYSTEM\DriverDatabase\DriverInfFiles\usbser.inf) was pointing at another.

    I simply changed the different parts in the (Default) and Active keys to my existing ‘756afc9aa127e768’, then the latest update installed fine.

    After the update I know have two usbser.inf Folders in FileRepository (I guess it keeps the old version around in case the update is uninstalled) and the registry keys point to the new one.

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  1. No trackbacks yet.