Tweaking.com Support Forums

Main Forum => Tweaking.com Support & Help => Topic started by: Omnivore on September 20, 2016, 07:30:48 am

Title: Length of run
Post by: Omnivore on September 20, 2016, 07:30:48 am
I have had the repair tool free version, running for 18 hours and it is still on fix 2 of 43.  It appears to be stuck and I am wondering if there is a way to stop so the client can go back to work, such as it is.

Your quick response would be appreciate4d.

Steve(Omnivore)
Title: Re: Length of run
Post by: Willy2 on September 20, 2016, 08:33:39 am
- Did you run the program in Safe Mode ?
- Abort the program and rerun the program but skip the repair(s) that are causing this kind of problem(s). Then rerun the entire program again.
- Do you have any corrupted files (Run that tool in Windows Repair) ?
- Run the SFCfix tool and post the log in your next reply.
http://www.majorgeeks.com/files/details/sfcfix.html
Title: Re: Length of run
Post by: Boggin on September 20, 2016, 03:50:26 pm
It may be worth running a chkdsk /f first to see if it reports any KBs in bad sectors and then running a chkdsk /r if it does but back up your personal files.

As for SFCFix.exe, that needs to be run immediately after a sfc /scannow as it needs a CBS log to work from.
Title: Re: Length of run
Post by: Omnivore on September 21, 2016, 01:52:02 pm
I should have asked the question better.  I needed to know if there was a way TO abort the program, but I took a chance and closed the reporting window.  It then proceeded to do more, froze and I closed that window.  After going by the first 6 or 7 tests, it completed.  I DID not run it in safe mode, and I did check the drive prior with both SFC and CHKDSK.  No errors were found.

Thanks for the response back.

Steve
Title: Re: Length of run
Post by: Boggin on September 21, 2016, 02:26:33 pm
I suppose you could stop it in Task Manager, but give it another run after using the program to boot up into Safe Mode, but you could use Option 5 to restore the registry back to where it was before the first aborted run and then see how it performs.

It's possible that your antivirus program was getting in the way in normal mode.