Author Topic: Tweaking stoppped anytime (Read 17514 times)

elicha · « **on:** August 07, 2019, 01:21:02 pm »

Hello,
When running Tweaking, I've never reach teh end. It stop many times even after 20 minutes. I shut the window and it go on to an another stop. I don't remimber it finished right one time. What happen?
thank's

Boggin · « **Reply #1 on:** August 07, 2019, 02:01:42 pm »

Can you open a Command Prompt(Admin) and enter chkdsk /f

You will be prompted to type y for it to perform after the next reboot.

Then enter shutdown /r /t 00 which will effect an immediate restart to allow it to continue.

The machine will restart after its completion where you should then open Event Viewer and when it has read the data, expand Windows Logs - click on Application/Action/Find and type chkdsk into the Find box and press enter.

Cancel the Find box to read the chkdsk report in the scrollable window below and check to see if it reports any KBs in bad sectors.

If it does, close off Event Viewer and open a Command Prompt(Admin) and enter chkdsk /r

This will transfer what data it can to safer parts of the HDD and then you should immediately create a system image onto something like an external HDD, although DVDs can be used.

You will also need to create a System Repair disk to boot up to restore a new HDD when that one eventually fails.

If the chkdsk report does not report any KBs in bad sectors then open a Command Prompt(Admin) and enter sfc /scannow and let me know what that reports and which version of Windows you are using.

elicha · « **Reply #2 on:** August 08, 2019, 03:38:54 am »

Thank's so much for your answer. I've already make sfc . I'm going to test chkdsk.

Boggin · « **Reply #3 on:** August 08, 2019, 04:18:29 am »

Which version of Windows are you using ?

elicha · « **Reply #4 on:** August 08, 2019, 04:50:51 am »

I'm using W7 family 64 .
The command CHKDSK did not find any bad sector. and same scf /scannow

Boggin · « **Reply #5 on:** August 08, 2019, 04:57:06 am »

I assume you are running the repair program in Safe Mode with Networking ?

Try the repair program again and when it stops, go Start - type reliability and press enter when View reliability history comes up.

That may have something or Event Viewer may have recorded something.

elicha · « **Reply #6 on:** August 08, 2019, 07:11:06 am »

I've runed in safe mode with network; I'll try again now

Boggin · « **Reply #7 on:** August 08, 2019, 07:35:39 am »

What exactly happens when the program stops - does it crash or just freeze ?

elicha · « **Reply #8 on:** August 08, 2019, 08:12:21 am »

I was just coming to you; I tried again. Now it stopped only one time : it freeze on the second repair. On restore File Permission / Propagating inheritable ACEs; item done 96%: 627/649.
After 15 minutes, I've shutted that windows and the software run until the end and return to normal windows.
I'll try again to-morrow, but I think it's already a good result. I'll come back again after
Regards

Boggin · « **Reply #9 on:** August 08, 2019, 08:15:09 am »

It's possible that the chkdsk may have righted something, but it sounds promising.

elicha · « **Reply #10 on:** August 08, 2019, 11:56:53 am »

Good evening
I think that the permission who stopped is not so important. if it stop again I'll let it like that. and I will not ask the second option. i'll try to morrow

Boggin · « **Reply #11 on:** August 08, 2019, 02:46:42 pm »

It is supposed to do the permissions first.

elicha · « **Reply #12 on:** August 09, 2019, 02:50:50 am »

Good morning
I tried again and I thinked maybe by running as administrator will be well. But it's same and it stoped in the same place. I believe i 'll stop searching more and exclude the n°2, nor but il some genious idea can solve the problem
Thank's for all

Boggin · « **Reply #13 on:** August 09, 2019, 02:54:43 am »

It's strange that it keeps stopping on the second Permissions repair.

I'll have to pass this onto Shane to see if he has any ideas as to why this is happening.

EDIT - Are you connected to the Internet in that mode ?

elicha · « **Reply #14 on:** August 09, 2019, 06:49:41 am »

I'm happy you can speak about my problem with an another helper; perhaps two heads will find the solution.
Connected at 2:....AM? no! I don't sleep too much but not writing at that time !

elicha · « **Reply #15 on:** August 09, 2019, 06:53:22 am »

I'm living in France and at that time it is 15:53

Boggin · « **Reply #16 on:** August 09, 2019, 06:57:03 am »

Shane is the author of the repair program, so if anyone will know why this is happening, then he should.

elicha · « **Reply #17 on:** August 10, 2019, 03:34:55 am »

Have a good day,
So, as you say, i'm sure that the solution will be promptly find!
Thank's for all

Boggin · « **Reply #18 on:** August 10, 2019, 07:10:54 am »

I wouldn't count on the "prompt" - I don't always get a reply.

elicha · « **Reply #19 on:** August 11, 2019, 01:12:37 am »

Helle,
We get time; we can wait some time to have an answer.

Boggin · « **Reply #20 on:** August 11, 2019, 01:27:30 am »

I copied & pasted the line with the 96% bit into my email to him where it was stopping so Shane will have something to work on, but if no one else complains of this, then it will be something that is specific to your machine which could make it more difficult to diagnose.

I had test run 4.5.3 when it was first released and it went through the repairs just fine.

It isn't convenient for me to run the repair program again just yet, but will try it later today to see how it performs.

elicha · « **Reply #21 on:** August 11, 2019, 02:35:24 am »

Thank's for all the trouble I make to you. µI'm waiting...

Boggin · « **Reply #22 on:** August 12, 2019, 02:36:45 am »

I ran the first four repairs and they ran fine so it looks like whatever it is, it's specific to your machine.

elicha · « **Reply #23 on:** August 12, 2019, 05:42:45 am »

Re,
The conclusion is to let the program run without le n°2. maybe my computer is not fine? I don't believe it's so important. Thank's again and maybe one another time

Boggin · « **Reply #24 on:** August 12, 2019, 08:30:25 am »

What was the reason why you ran the repair program ?