Repair Windows App repair job 38 now at 29 hours?

[pme1410]

Hello there,
been running the windows repair app for 29 hours now, is this expected?
The CPU level is fluctuating, obviously the time is increasing and the laptop hasn't crashed, it's at repair jobs 38/43 with a cmd window showing Deployment operation progress.
I've already had to cancel and shut down once, am I kidding myself thinking it's still working?
Done all the tests etc on the way to this repair tab...
Regards
pme1410

[Boggin]

I've passed this onto Shane, but would suggest that you stop it for now.

What problems are you having that prompted you to run the program ?

[pme1410]

Thank you Boggin,
is there a safe/safer way to stop progress?
I ran the program after I updated to W10 anniversary, I had impossibly slow start up and shut down issues, which I thought I had solved some months previously, before W10 Anni, by updating my graphics card drivers.

[Boggin]

I think you have to stop it the way you have done.

Some have reported slow boot up times after upgrading with the Anni. Update but as it has also been producing other problems for some, I would suggest that you roll back to the previous version.

Quite a few still haven't received this through Windows Update and the thinking is that MS have put this on hold until they sort out the bugs.

[Boggin]

Can you run the program again and see which repair in the list 38/43 relates to.

Shane needs to know this so as find what is sticking.

[pme1410]

Does it not show the stalled repair in the photo of the screen I posted?
I'll run the repair again anyway tomorrow...

[Boggin]

Yes it does - I'd assumed Shane had looked at your thread that I'd included a shortcut to.

It appears to be 28.01 - I'll let him know.

[pme1410]

Got to the same repair today, after 2 hours, and further - Command 5 of 6...!

[Boggin]

Reply from Shane -

Command 4 is this command
 powershell.exe -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\ImmersiveControlPanel\AppxManifest.xml

 command 5 is
 Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register $($_.InstallLocation)\AppXManifest.xml

 So again command 5 is powershell doing all the installs of the apps. If it is hanging up then something is wrong with them, or bad sectors on the drive.

Me -

Did you run a chkdsk /r before running the repairs - if not, then stop WR and run that command to eliminate the hard drive - it should show if there are any KBs in bad sectors.

If there are, then you should back up your personal stuff.

The bad sectors will remain but they will be roped off so nothing else can be written to them and depending upon how many whether you should get a new HDD straight away.

[pme1410]

Hi Shane,
yes I ran each and every step test option to this point, from power down battery tab step 1, through to this point step 5 repairs, no errors what so ever were reported at any stage, including the check disc step.
Do you wish me to run checkdisc, chkdsk /r under a separate cmd, not within WR?
If there is a log I can upload if you wish.
Do you think this is corrupt windows files?

[Boggin]

Shane isn't on the forum at the moment but when you run chkdsk from within the program, it only runs it in read-only mode and may not be accurate.

Run a chkdsk /r on its own and there's only a need to post its log if it shows anything substantial.

I assume you know where to find its log in Event Viewer and how to Copy/Copy details as text to paste into the reply box ?

[pme1410]

Yes, Thanks Boggin, I have a go tomorrow, bed time now!

[Boggin]

Okay - I won't belong in going to bed myself as it's just turned the witching hour.

[pme1410]

Humm, Check disc (admin - cmd chkdsk /r) in (windows not safe mode) got to 17% and now I just have the whurlie wheel and pointer, no windows writing on the screen as before, although the hard drive light is flashing as if somethings happening, leaving it on for the time being...

[Boggin]

The slow start up that you were experiencing could have been a sign that the drive was starting to fail but also masked because the Anniversary Update (AU) has also been causing that for some.

What are you using to post with ?

If you have another machine with a disk drive then you can download and create a SeaTools for DOS disk which will check the integrity of the hard drive but will not repair the files as a chkdsk /r could do.

http://www.seagate.com/gb/en/support/downloads/seatools/seatools-dos-master/

I was getting that black screen and busy when trying to manually upgrade to the AU and power shutting down and a restart would give me Windows is attempting to recover the installation.

Sometimes it would and then I'd just get rolling back to previous OS.

I'm not sure if Windows will be able to recover in your case as I don't know what corruption will have occurred when it was trying to reinstall the apps or the condition of your hard drive, but with the SeaTools for DOS disk, at least you will be able to tell if it's OS corruption or a failing hard drive.