Download Windows Repair 3.8.2

Tweaking.com has released a new version of Windows Repair. This program is capable of fixing many problems, such as errors in the registry or with file permissions, or caused by a virus. The repairs are extensive, so it is recommended that you only use the program when there are few other options left. Before it starts the repairs, it offers the possibility to check the hard drive for errors, scan the system files and of course create a backup of the registry and a system restore point. The program can be used for free, even in commercial environments. You can get one for twenty dollars pro license be purchased, which provides additional options and supports the further development of the program. Since version 3.8.0, the following changes and improvements have been made:

Changes in Windows Repair version 3.8.2

• Fixes to the interface.
• Code fixes and cleanup.

Changes in Windows Repair version 3.8.1

• Updated the tree view control on the main repair window to the new controls. This control will size properly for users who have a higher DPI setting or have their fonts set about 100% on their systems.
• Added a new item to the top of the repair list, this way you can just click or unclick the check box there to select or unselect all the repairs. This allows me to get rid of the two buttons I had for that, freeing up a little more space.
• Updated all the permissions repairs and removed the “Users” group from being set to full. Only administrators, the system and such need full access, the “Users” group isn’t touch by the repair unless it is part of the default permissions that are put back.
• Added the ability for the taskbar icon to display a progress bar during the repairs, this is for systems that support it.
• Fixed a very odd bug in Windows Vista when a user ran the register system files and no other repairs. This bug would cause VSS to break and thus system restore or windows backup would stop as well. But if you ran all the repairs and ran the Repair Volume Shadow Copy it would fix it. I traced it down to the fact of the order that the files are registered in. For some reason if you register a dll with the /i command and then after registered the same file like you would any normal file is where something in vista didn’t like it. After that happened none of the vss writers would show up. BUT if you register the file normal first and then call the /i command it would work fine and not break VSS. This bug seems to only be in vista.