Windows Repair Toolbox

[AlexCa]

Hello everyone, and a happy new year.

Just a heads up, if anyone is having trouble running ADWCleaner and JRT in a computer that has the latest version of Malwarebytes installed, please do this:

before running any of those programs, right-click in MBAM icon in the notification area and select "Quit Malwarebytes".

Thank you.

 

[AlexCa]

Hello everyone,

I've just released version 1.8.0.0 of Windows Repair Toolbox:

- The “Disk” label now has a tooltip that shows additional information about the system drive, as shown bellow:

- The “Disk” label will also let you know if the drive is SSD:

- A SMART warning will be displayed if the system drive fails a basic health check (this is the same check that is performed by GsmartControl and it’s also based on smartmontools). Very important: the absence of the warning doesn’t mean that the hard drive is ok, it is just a basic test.

- Besides the Windows install date, WRT will now also present the system boot time.

- Added to “Branding” settings: password protection; hide the “About” tab option.

- Under “Backup and Recovery”: replaced TestDisk with DMDE; replaced Puran File Recovery with LicenseCrawler.

- Portable version: In the initial license window, you no longer need to hover and mouse-click the "Accept" and "Decline" buttons. Now you can just press the “Enter” key to accept and continue or “Esc” to decline and exit.

-Rkill would terminate Windows Repair Toolbox process if you renamed “Windows_Repair_Toolbox.exe” executable to something else (e.g., “My_ Repairs.exe”). That will no longer happen. This makes it easier for you to rename “Windows_Repair_Toolbox.exe” executable, and change its icon, if you want to do so.

- Added a tooltip to the “Refresh” button in the Notes tab.

- Several other minor fixes and improvements.

As usual, any questions, suggestions or bug reports, please let me know.

Thank you!

 

[HankArnold]

When I try try the link above with Chrome, I get:

"www.windows-repair-toolbox.blogspot.com normally uses encryption to protect your information. When Google Chrome tried to connect to www.windows-repair-toolbox.blogspot.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be www.windows-repair-toolbox.blogspot.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit www.windows-repair-toolbox.blogspot.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later. Learn more."

 

[AlexCa]

When I try try the link above with Chrome, I get:

"www.windows-repair-toolbox.blogspot.com normally uses encryption to protect your information. When Google Chrome tried to connect to www.windows-repair-toolbox.blogspot.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be www.windows-repair-toolbox.blogspot.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit www.windows-repair-toolbox.blogspot.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later. Learn more."

Sorry, my signature was still pointing to the old website. Please try it again now. Thank you.

 

[HankArnold]

Working now. Thanks.

 

[AlexCa]

Hi all,

I've just updated Windows Repair Toolbox to version 1.8.0.1:

- Fixed an error (“For security reasons DTD is prohibited…”) that would occur at WRT startup under special circumstances (e.g., when WRT starts the computer is connected to an open wifi that requires authentication in a webpage before allowing access to the internet, and that authentication has still not been made).

- Removed some outdated instructions from the “Custom Tools” tab (the new portable version no longer requires you to import your custom.xml file at each time you want to use it)

- Updated the link to WRT homepage in the “About” tab;

- Some other minor improvements.

Thank you!

 

[AlexCa]

Hi, I've updated Windows Repair Toolbox to version 1.8.0.2:

- Replaced Snappy Driver Installer with DriversCloud.
- Now the portable version will only display the initial licence window the first time it runs.

Thank you.

 

[GTP]

Just tried going to you website for the 1.8.0.2 update and get errors.

 

[AlexCa]

Just tried going to you website for the 1.8.0.2 update and get errors.

Hi, the website is now: https://windows-repair-toolbox.com/

I've just noticed that the first post of this thread was still pointing to the old website. It's corrected now, sorry.

 

[wavey]

Bullguard sending WRT to quarantine today.

 

[cypress]

Never heard of DriversCloud before.

 

[AlexCa]

Bullguard sending WRT to quarantine today.

Thank you @wavey, i've reported the false positive.

 

[AlexCa]

Never heard of DriversCloud before.

Hi @cypress,

it was previously known as Ma-Config, and it's been around for quite a long time.

From all the options I looked into to replace SDI, it seemed to me the most (honestly, the only) trustworthy option (the requirements i looked were: free, portable, reliable, and not install crapware - or at bare minimum give a clear option to opt-out. It could be a non-portable program, as long as the other requirements were met).

However DriversCloud nowhere as straightforward as SDI. It will provide the download links for the drivers, but those have to be downloaded one by one :/ On the plus side, it will also provide detailed information about hardware, and about BSOD.

Do you guys recommend some other software? If yes, please let me know!

I guess that another thing i can do is to keep SDI, but not giving the option to use a previously downloaded version. This way WRT would always download a fresh version from SourceForge (that, from what I understood, is compiled by @glennd), and, in theory, this would prevent the use of the built-in auto updater that brings the problematic version mentioned in the other thread.

What do you guys think?

Thank you.

 

[cypress]

As of right now maybe SDI would be good if it is still coming from Sourceforge while @glennd is maintaining it.

 

[glennd]

As of right now maybe SDI would be good if it is still coming from Sourceforge while @glennd is maintaining it.

Alex must do what he thinks is best. r539 from SourceForge is ok so long as you don't use the built in updates to update the application. Including it with WRT would be problematic for those WRT users who are not aware of the issue. I think removing SDI from his app, at least for the time being, is a fair call.

Alex may care to revisit SDI when I get the forked project sorted out in a week or so.

 

[AlexCa]

Alex must do what he thinks is best. r539 from SourceForge is ok so long as you don't use the built in updates to update the application. Including it with WRT would be problematic for those WRT users who are not aware of the issue. I think removing SDI from his app, at least for the time being, is a fair call.

Alex may care to revisit SDI when I get the forked project sorted out in a week or so.

I will, for sure!

 

[cypress]

Alex must do what he thinks is best. r539 from SourceForge is ok so long as you don't use the built in updates to update the application. Including it with WRT would be problematic for those WRT users who are not aware of the issue. I think removing SDI from his app, at least for the time being, is a fair call.

Alex may care to revisit SDI when I get the forked project sorted out in a week or so.

You're right and that sounds like the best idea for now.

 

[AlexCa]

Hello guys / gals, I've just released a new version of WRT (1.8.0.3). Here's what's changed:

- Replaced DriversCloud with Snappy Driver Installer Origin;

- Replaced Minitool Partition Wizard with Macrorit Disk Partition Expert (this second one is a portable program);

- If the system drive is identified as an SSD, and the user clicks the "Disk Defrag" button the message below will be shown:

- If the system drive is identified as an SSD, the user can no longer select "Disk Defrag" as part of the Unattended Fix (because the system drive is the one that is defragmented during the process). The message below will be displayed:

As always, your feedback is useful and appreciated.

Thank you.

 

[GTP]

The message "bellow" will be displayed:

Sorry to "nitpick" but just a small thing. I noticed you spelled "below" incorrectly and also on your website as well.

 

[glennd]

Sorry to "nitpick" but just a small thing. I noticed you spelled "below" incorrectly and also on your website as well.

He meant to say: "The message "BELLOW!!!" will be displayed"