windows component store running for 20 hours and still... !!!!! [ SOLVED ]

[-vv-]

Hi,

I ran windows component store repair and after 20 hours still running. When do you think would be a good time to declare this thing is not working?

Yes, cpu is working and sometimes read and write drive work too, but how about if it is trying to install something that fails to install and it starts over and over again in an evil loop?

The advice says that we can't stop it or the computer would be destroyed, so here is the paradox: to repair the computer I lost the computer in an eternal repair.

Please advice, I'm loosing my mind here...

Thank you,



ps. the version of the computer is windows 8

1- Dism /Online /Cleanup-Image /StartComponentCleanup took about 2 hours to complete

2- Dism /Online /Cleanup-Image /RestoreHealth... still running

 the event viewer doesn't show any errors or anything

[-vv-]

24 hs so far... I think I'm breaking all records

[-vv-]

Shane answered me in private and I am posting here what might help someone else with similar issue:

----------------
First thing I was going to ask you is to see if dism is running in the task manager. If it is but isnt using any cpu what so ever then you might be safe to kill it. If it is using cpu and looks like it is still working then it would be a good idea to close out of everything else you can.

The dism will download any files it needs from windows updates, so if you have a slow connection or something blocking it that might explain the slow down.

Shane

-------------

I appreciate your response. CPU is working but no information is coming or sending by internet from the computer. I am working in other computer and the connection is strong.

I have avast antivirus, I disconnected for a while but nothing changed so I activated it again.

Any other idea?

Thank you,

-vv-

----------------------

is dism itself using any cpu?

Shane

------------------------

Oh sorry, dism itself... nop
I looked at it (both dism host and dism image) for a minute didn't change and just 0%

-vv-

---------------------------

Then looks like MS's own tool has just stopped. That is the only tool they give that can help fix sfc and the files on the system, to bad it is buggy as crap lol. But I dont know in 8.1 it is a little better.

I would say if NO cpu has moved from them in a while then they are not doing anything that you should be able to kill it. Since dism gives NO progress or information on what it is doing there is no way to tell. But if it hasnt moved then there is no other option.
--
Take care.
Shane

----------------

well all this start when I tried to update to 8.1 and the app store didn't work, and then when I manage to fix it to open then didn't install it or any update... all a mess

Still one more repair to perform after this one... is there any way to kill only this process or skip it and continue with the next one? Or just click on stop repairs button and that is...

-vv-

----------------------
Should just be able to kill dism from the task manager, the cmd window is simply waiting for it to close. So once you kill it the repairs should move on.

Shane
----------------------


I did it and the next repair ran ok and logs came up ok and normal. After a bumpy reboot (I freaked out a little) everything started normally and apps and updates working fine...

Thank you so much Shane!

[Shane]

Happy to help, sorry I didnt respond to the post faster, been awake for 40 hours programming the windows repair toolbox lol

Shane