Windows 10: [SOLVED] Windows update issues - DISM reporting 0x8E5E0147

I've been having trouble installing updates for a while. Tonight I tried installing .NET 3.5 and it gave me 0x8E5E0147.

I tried downloading a new Win ISO and running:

Dism /online /enable-feature /featurename:NetFX3 /All /Source:[USB with ISO]:\sources\sxs /LimitAccess


It fails, and in dism.log I've spotted:


2020-04-01 01:34:49, Info CSI 00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.710_none_5f52d84058d0677f\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND


There is no amd64*-folder in Windows\Servicing. I'm guessing it's at least part of the problem, but my Google-fu isn't strong enough for this one.

Here is a Pastebin of dism.log. Anyone familiar with this issue? If so I'd be thankful for any pointers.


Thank you.


Edit: Also generally curious about what "shimming" means in this case. What's it considering? I'm only familiar with mechanical shims :



Robin


UPDATE\SOLUTION


Somehow my component store WinSxS must have become corrupted. I ended up unpacking a Wim file from install.esd and using that to repair my component store, after which .Net 3.5 installed withouth a hitch.


Copied install.esd from the ISO onto the root of C: first so commands below were run from there.


dism /Get-WimInfo /WimFile:install.esd

dism /export-image /SourceImageFile:install.esd /SourceIndex:6 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity

dism /Online /Cleanup-Image /StartComponentCleanup

dism /Online /Cleanup-Image /AnalyzeComponentStore

dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess


I'm hoping this will have killed my other Win Update woes, but I'll report back if not.

:)

 

Windows 10 fails to update


Thanks,

The Users list compared to the Profile list you posted earlier tell me there is not an issue with Users (a known issue where there is a profile in the list, but not actual User folder).

The error code suggests corruption in the CBS manifest:
Try these steps one at time until the issue is resolved or you run out of steps.

Is Windows activated?
No? Activate Windows 10

Launch Command Prompt (Admin)
enter the following line
reg query HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate /s
If DisableWindowsUpdateAccess REG_DWORD 0x1

launch regedit
navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
change the value of DisableWindowsUpdateAccess to 0
exit regedit
exit Command Prompt

Launch Windows Update

Try the next suggestion if the issue is not resolved.

Restore health to the component store
DISM - Repair Windows 10 Image
Step 6. To Use DISM /RestoreHealth /Source:wim Command
- OR -
Step 7. To Use DISM /RestoreHealth /Source:esd Command
Check System Files
SFC Command - Run in Windows 10
Read the front material, then
follow >> OPTION THREE <<
To Run SFC /SCANNOW Command in Windows 10

If there are integrity issues reported on screen,
Follow the instructions in >> OPTION FIVE <<
To View Only the "SFC" Scan Results from the CBS.LOG

If there are no integrity errors, Launch Windows Update

Try the next suggestion if the issue is not resolved.

Paste the following line into the address bar of File Explorer
Control Panel\All Control Panel Items\TroubleshootingLaunch System and Security > Fix problems with Windows Update
Press Advanced
Select Run as administrator
Press Next

Launch Windows Update

Try the next suggestion if the issue is not resolved.

Automatically reset Windows Update components
Download and run MS Windows Update diagnostic cab (direct download)

Launch Windows Update

Try the next suggestion if the issue is not resolved.

Manually reset Windows Updates via batch file

Windows Update - Reset in Windows 10

Launch Windows Update

 

New install Windows 10 (issue solved)

It's good that you're not experiencing any issues. Unfortunately many folks are, a quick Google search will show the same info im offering the OP.

Heres a couple examples:

Here

Here

It's basically what I mentioned above, small issues here and there ,but nothing to end your day.. for the most part.

I know it's anecdotal, but for my experience 95% of the time it's perfectly fine. The issues I've run into wouldn't be enough for me to roll back , but they would be enough (had I not installed it yet) ,to avoid it for another couple weeks which is why I'm suggesting it to the OP

Windows 10 Fall Creators Update problems and complaints

• Installation problems with the Fall Creators Update
• Microsoft Edge problems with the Fall Creators Update
• Drivers problems with the Fall Creators Update
• Experience problems with the Fall Creators Update

keep in mind, as of recently, the FCU is installed on 5% of devices roughly.....

 

Windows insider program update issue

well , in the off chance that anyone was curious as to this issue, i fixed it without the above steps....i retried it today, but remembered that i have My RAM overclocked from 1333mhz, to 1866mhz.

I dropped it back down to its stock speeds, and it breezed right though the update with no issues what so ever. problem solved.