Author Topic: Windows 8.1 updates hanging (Read 17730 times)

kevinclarke · « **on:** May 17, 2015, 06:43:32 am »

Dear forum,

I wonder if you can help. My windows 8.1 updates started to fail last Thursday, the updates fail but after doing the recommended fix that windows suggests (using the dism tool restorehealth, fails after 80%) the updates just hang and never complete. Note the Dism tool when ran manually, fails with an error 1726 "The remote procedure call failed".

I checked the RPC was started ok.

I since ran the Tweaking.com windows repair tool (pro version) and this also fails dism, I noticed on test 29. here is the output below. Note I ran the Tweaking repair tool in both Safe mode and booted up in normal mode. The results are the same regardless.
Note I ran the SFC within the tool this also fails.

"Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Error: 161

The specified path is invalid.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Error: 1726

The remote procedure call failed.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log"

I have also tried a tool I saw in this forum the SFCfix, but this tool said there were no error reported. Lastly I tried recovering to the earliest check point available, but the results are the same.

Any help or advise would be greatly appreciated, I have attached the dism log in case it helps.

Many thanks for your help

Regards
Kevin

Shane · « **Reply #1 on:** May 18, 2015, 03:00:18 pm »

Go to services and check to see if the service "Remote Procedure Call (RPC)" is set to automatic and is running. If that sint running then that will cause the error.

I also found others who had the same error and it turned out a system file was locked and caused it as well

Quote

You can use Process Explorer to help find the cause of your issue here. In this thread, a user having the same issue used it successfully to narrow down the responsible programs, which turned out to be locking the dxgi.dll file. Upon exiting those programs, the user was able to successfully run the DISM command.

So first lets check the service and then if that isnt the problem we will need to dig in and find what file is causing it.

Shane

kevinclarke · « **Reply #2 on:** May 19, 2015, 01:36:24 am »

Hi Shane,

Many thanks for your reply.

I checked the RPC status and they are as follows:

Remote Procedure Call (RPC) is running and in automatic
Remote Procedure Call (RPC) Locator is in Manual

I assume this is correct? As you mentioned also about the dxgi.dll file locking a thread. I did see some hits about this and I have installed Process Explorer tool, but I cannot see this file listed. i.e. I did a "Find Handle or DLL" and searched for it but I cannot see it. Maybe I doing something wrong or not using this tool correctly?

Many thank for your help

Regards
Kevin

Shane · « **Reply #3 on:** May 19, 2015, 12:17:43 pm »

The trick with process monitor (Not the explorer one) is to have it look at the dsim process and see what it is hitting, and at the bottom of the list should be the last files it hits.

So with process monitor from sysinternals you start it up and then start the dsim, then wait till dsim is finished, then find dism in the list of process monitor and then right click on dsim.exe and hit include, this will make it to where it only shows results for it, clearing up that list a ton and making it easier to read

Shane

kevinclarke · « **Reply #4 on:** May 20, 2015, 05:34:52 am »

Hi Shane,

I ran the dism command waited until it failed. I've attached what I found, this is the end of the dism list I captured in the attachment "Capture.png". I also attached the Stack and process screen shots after the failure. Not sure if any of these help?
The ntdll.dll seems consistent in each of these screen shots, is this relevant?

Thanks for all your help
Regards
Kevin

Shane · « **Reply #5 on:** May 20, 2015, 12:45:45 pm »

So it looks like it is crashing when it calls the ntdll.dll file to do a command, which when that happens it is because it is having trouble with something else. Its like a painful game to play lol

Can you compress and attach the cbs.log file after the scan, that should hold more information.

Shane

kevinclarke · « **Reply #6 on:** May 21, 2015, 02:28:13 am »

Hi Shane,

I did another run of the dism restore command and have attached both the cbs.log and also the dism.log in case it helps. I notice at the bottom of the cbs log a failure

Error CSI 000000fd (F) Failed on regenerating file [l:30{15}]"wuaueng.dll.mui"[gle=0x80004005]

This same failure has been pretty consistent I think for previous dism attempts.

Thanks for all your help

Regards
kevin

Shane · « **Reply #7 on:** May 21, 2015, 11:30:48 am »

wuaueng.dll is part of windows updates, the wuaueng.dll.mui is used by the system on how to work with the file AND dism uses windows updates to download missing files or updates it needs.

So if it is crashing on a windows update file then that might be the file we are looking for that needs replaced

If you cant find a replacement for the file I do have 8.1 installed in vmware and I can grab the file off of it for you.

Shane

kevinclarke · « **Reply #8 on:** May 22, 2015, 06:58:05 am »

Hi Shane,

Once again many thanks for all your help.

I managed to get copies of both wuaueng.dll and wuaueng.dll.mui from an 8.1 system, but unfortunately this did not solve the problem. I did a reboot after putting these files in place and re-ran dism it fails as before.

This is really very strange eh..

Let me know if you have any other ideas otherwise I'm guessing it will be a reload.

Regards
kevin

Shane · « **Reply #9 on:** May 26, 2015, 02:14:55 pm »

Not being able to trace exactly what is causing the problem is what is a pain. You could see how a repair install does though instead of a full reinstall.

http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html

Shane