Main Forum > General Computer Support

Windows 8.1 updates hanging

(1/2) > >>

kevinclarke:
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:
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.
--- End quote ---

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. :wink:

Shane

kevinclarke:
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:
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 :wink:

Shane

kevinclarke:
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

Navigation

[0] Message Index

[#] Next page