Main Forum > Tweaking.com Support & Help

Tweaking has not made any changes in the last two hours

(1/2) > >>

paprgypc:
Hello,

I have a Win 10 system and started the tweaking program about 5 hours ago.  It has stopped at Job 8 of 42 for the last three hours.  There is no read or write for some time.
 

This is the first time I have ran Tweaking.  Not sure what I should do now.  Any help would be appreaciated.

thanks,
Jim

Boggin:
Hi Jim,

Stop the repair program then open either a Command Prompt (Admin) or Powershell (Admin) and enter these cmds -

dism /online /cleanup-image /restorehealth

sfc /scannow

Enter exit to close the cmd window and try the repair program again.

Let me know how you get on.

It's advisable to manually create a restore point before proceeding with the repair program.

There is a bug in the program where it doesn't physically create a restore point when using that option and the Registry Backup doesn't work properly in that version of Windows Repair.

Shane is currently working on an update for the repair program which should resolve those bugs.

paprgypc:
I went to powershell as admin and ran this command: dism /online /cleanup-image /restorehealth
I received error 87. 
So not sure were to go next.
thank you for your help.
Jim

paprgypc:
I was able to get the code to run by capitalizing DISM in the code.  now starting Tweaker
Thanks,
jim

Boggin:
I'm running a dism /restorehealth cmd in Powershell run as an admin at the moment and it's running without error in lower case.

When a Windows update changed Command Prompt to Powershell in the Start menu, I changed it back so i normally just use the Command Prompt (Admin) from there.

You would only normally get an error 87 if you made a typo in the cmd line, so not sure why a correctly entered cmd should produce that error code until you capitalised dism.

Did the repair program run okay this time ?

Navigation

[0] Message Index

[#] Next page