Main Forum > Tweaking.com Support & Help

New Version 2.85

(1/5) > >>

silhouett:
I have windows 8.1 64 bit, I had run windows repair tweak 2.84 with no issues except I had noticed in the event log a warning Interactive service not running error. I had started it but it was in manual so I think it should have started on it's own, I then ran 2.84 with no issues.   Now I am running 2.85 and it is still on step 1  registery permissions toggling between process count 139, 140 doing drive writes but it has literally been 51 minutes and nothing seems to have changed ?  Version 2.4 was far past this stage and done by now.


 

Shane:
140 processes is a LOT to have running in the back ground while the repairs are running. On my system I never have more than 60 to 65 processes running at any one time.

You should really see what you have running in the back ground and why so many.

Also when the repair is running, if you check the task manager you should see cmd.exe running and SetACL_64.exe running. The SetACL_64.exe is what is setting the permissions so you should see it running and using CPU.

But it is very possible one of those programs you have running is getting in the way of the repair. Also, on the next version of WR 2.8.6, which I am releasing monday, I have changed the way the program waits for a repair to finish. I had fund that on slower machines that the repair cmd.exe wouldn't open fast enough and so the program would think the repair was done and start the next repair. I now have working better and keeping that from happening.

Shane

silhouett:
Thanks for the quick replay, Yes I am a process-holic

Attached is what is running

Shane:
You have 4 or 5 different backup programs all running, you have multiple antivirus programs running (Which is a bad idea, they can conflict with each other) and a bunch of other things, that there is a good chance you dont need to have running in the background :-)

I am going to be changing the interface in WR soon to ask the user to please start the system in clean boot mode and then run the repairs. Cleanboot mode is where none of the 3rd party programs are started. I have found more than a few times, where people ran the repairs on a system with nearly 3 times the amount of normal processes running would get random and odd problems with the repairs. Some of the repairs didnt run right because multiple programs where scanning it and keeping it from working or messing with what it was trying to do. Other times the system was simply out of resources because of the number of things open and so the repairs didnt work correctly.

Not to mention that it slows the repairs down by a large amount. :wink:

Shane

silhouett:
Well they are backups for diffrent things, Google, Samsung Pictures I take with Camera, Arconis for drive image etc.. 

SO how do I exit your software ? LOL  it says Stopping, Waiting for current repair to finish... :evil:

Navigation

[0] Message Index

[#] Next page