Author Topic: Report slow repair"bug" (Read 28069 times)

Gamezertruth · « **on:** September 16, 2013, 11:52:41 am »

Problem with the new version 1.9.18 and I would like to do I report some of the repair options have more time than usual time that it needs to be 10 or 15 minutes to get some of the repair done '!

So the new version has a bug and you need to fix this following repair options! >>=)

rest file Permission. This option is now looking up to our files on our system??That is why needs time to get done. More than 20 minutes just for this option?

This repair WMI option also needs a lot of time to get done?

unhide non system files option also needs a lot of time to get done?

Willy2 · « **Reply #1 on:** September 16, 2013, 02:03:16 pm »

- Switch temporarily off your AV. Helps to speed up things.
- On my Win 7 system these repairs took 15 (reset file permissions), 6 (WMI) & 2 (Unhide files) minutes to perform. Yes, it takes time to do these repairs.

Shane · « **Reply #2 on:** September 16, 2013, 03:05:45 pm »

Quote

rest file Permission. This option is now looking up to our files on our system??That is why needs time to get done. More than 20 minutes just for this option?

This has always done that, it does each folder on the root of the drive, and that also means all sub folders. As for speed the speed of the drive and the CPU will affect the speed of the repair greatly.

And of course if the AV is running it is scanning every file it touches which slows it down as well.

Quote

This repair WMI option also needs a lot of time to get done?

Yes, this is because it now searches for the mof and mlf files to add back to the WMI by 3rd party programs. It was greatly needed and helps avoid the AV not showing up in the security center till the AV does an update. Not to mention helps when people have other programs that added themselves to WMI such as .net and others. SO again based on CPU and drive speed affects the speed.

Quote

unhide non system files option also needs a lot of time to get done?

This one shouldnt have slowed down much, I did change what API it uses to search for files so it could handle unicode files and folders. Again the AV will slow this down as well.

At the same time I also have it check for symbolic links now so it never gets stuck in a loop. That does require more cpu so i guess it would slow done a small amount base don your cpu and what else is running at the same time

Shane

Willy2 · « **Reply #3 on:** September 16, 2013, 03:30:10 pm »

But the *.mof & *.mfl files for ".Net" are, on my win 7 system, not placed in the "%windir%\system32" subfolder but in %windir%\Microsoft.net".

Type this command ("dir c:\*.mof /s /b /p" & "dir c:\*.mfl /s /b /p") and see what pops up (outside that nasty "winsxs" subfolder).

Something for the next WMI update ?

Shane · « **Reply #4 on:** September 16, 2013, 03:33:17 pm »

Perhaps, I followed the guide on the one link you gave me. For WIndows vista and newer they dont have it do that, I think because of the winsxs folder. I wonder if .net puts a copy of the files in the webam folder.

Shane

Willy2 · « **Reply #5 on:** September 16, 2013, 03:39:07 pm »

Makes sense. But now XP has a "winsxs" subfolder as well !!! (To make things easy, right ??

).

Shane · « **Reply #6 on:** September 16, 2013, 03:43:18 pm »

Windows isnt suppose to have a Winsxs folder.

On my XP it does have one, and when you check it you will see it is much smaller than a normal winsxs folder and the only files in there when installed by MS such as VC runtimes and a few others. And when I scan for symbolic links there are none pointing to it. I think it was just those MS installers put them there.

Shane

Gamezertruth · « **Reply #7 on:** September 17, 2013, 08:32:02 pm »

Thx but I have no anti-virus installed on my system for a long time so I do not think that the problem of my Windows system!
and will check it later.....
I want a temporary solution for the new version.

Willy2 · « **Reply #8 on:** September 17, 2013, 11:03:10 pm »

Don't you have the Service "WinDefend" (for Windows Defender) running ? That will slow down your system as well.

Gamezertruth · « **Reply #9 on:** September 18, 2013, 01:10:49 am »

i don’t have Windows Defender!

Willy2 · « **Reply #10 on:** September 18, 2013, 12:49:07 pm »

What's the speed of your CPU & what's your O.S. (XP, Vista, ......) ?

Gamezertruth · « **Reply #11 on:** September 18, 2013, 02:39:53 pm »

i have microsoft window xp professional version 2002 service pack 2

intel{R}celeron{R}m cpu

440 @ 1.86GHz

1.86GHz, 504 mb of ram

Willy2 · « **Reply #12 on:** September 19, 2013, 01:00:25 am »

When you look at the info in the "Repair Info" pane then you'll see that the program is aware of the time consuming nature of a number of repairs. Perhaps the wording should improved.

Shane · « **Reply #13 on:** September 19, 2013, 01:50:17 am »

Quote

I want a temporary solution for the new version.

I am not changing the repairs. The repairs do more to do the job better, if it slows down so be it. On my system I barley had a difference of about 45 sec.

Again speed of the hard drive and the CPU matter most.

Your CPU is slow and you dont have a lot of memory. And if your hard drive is older and slower all 3 of those things will make the repairs take a while for you.

Your on a old computer, anything ever added to the repairs you are going to notice.

Shane

Willy2 · « **Reply #14 on:** September 19, 2013, 05:15:42 am »

Keep in mind: (like Shane said at least once) It's a repair tool and not a maintenance tool that should be run say every day or week.

Luckily I found a bug in the WMI program code and as a result some program code doesn't get executed. Otherwise that repair would have taken much more time on a XP system. (@Shane: See our conversation).

Gamezertruth · « **Reply #15 on:** September 19, 2013, 09:56:46 pm »

Quote from: Shane on September 19, 2013, 01:50:17 am

Quote
I want a temporary solution for the new version.

I am not changing the repairs. The repairs do more to do the job better, if it slows down so be it. On my system I barley had a difference of about 45 sec.

Again speed of the hard drive and the CPU matter most.

Your CPU is slow and you dont have a lot of memory. And if your hard drive is older and slower all 3 of those things will make the repairs take a while for you.

Your on a old computer, anything ever added to the repairs you are going to notice.

Shane

Good information, but in the old versions there is no problem with the repair option above since the last version came out!
This was all on the same computer I'm on it!
How do I speed up the hard drive and CPU?
And my computer is 3 years-old ..Not bad, right?

Gamezertruth · « **Reply #16 on:** September 19, 2013, 10:10:47 pm »

Quote from: Willy2 on September 19, 2013, 05:15:42 am

Keep in mind: (like Shane said at least once) It's a repair tool and not a maintenance tool that should be run say every day or week.

I know this. But I do not run anything so until I think the virus hit my system and has done change system settings'!
It is okay?

Willy2 · « **Reply #17 on:** September 20, 2013, 12:44:04 am »

- Install more memory if possible. Price of 2nd hand memory for XP systems has come down dramatically.
- Install Cleanmem.
http://www.pcwintech.com/cleanmem
The program reduces memory usage and that reduces disk I/O and leads to a better overall system performance. Helps to speed up WR as well because WR needs to process A LOT OF files on your harddisk.
- Increase overall speed of Windows by switching off A LOT OF visual gimmicks/features. (GOOGLE it).
- Install Service Pack 3 for XP.
- Run Simple System Tweaker.
http://www.tweaking.com/content/page/simple_system_tweaker.html

Could you rewrite your previous post ? I didn't quite understand what you were trying to say.

Willy2 · « **Reply #18 on:** September 20, 2013, 07:37:40 am »

I know that "Repair WMI" (for XP) executes three commands that each take a significant amount of time. And those 3 commands are executed twice. No wonder it takes "some time" to run "Repair WMI". Perhaps it's possible to speed up that repair.

Shane · « **Reply #19 on:** September 20, 2013, 01:49:18 pm »

A new hard drive would help a LOT. If your drive is dieing or has slowed down, which they do as they age, then when the repairs are trying to read and work with so many files you are at the limit of how fast the drive and get the information it is asking for.

I finally decided to buy myself a SSD drive, I got the one that can do 500mb/s read and writes vs the normal 25 to 100 mb/s of normal working drives. Boot up from turning ont he computer to the desktop should take less than 4 sec now :-D

Shane

Willy2 · « **Reply #20 on:** October 13, 2013, 11:27:09 pm »

@G-Hot: Try WR v2.0.0. Repair WMI should be a lot faster on a XP system.