Hi all, I've just released version 1.5.0.5: - Emailing the unattended fix log is now much easier (there's no longer the need to configure a Gmail account). Thanks!
[FONT="]Hi all, I've just released version 1.7.0.0:[/FONT] [FONT="] [/FONT] [FONT="]- The portable version of Windows Repair Toolbox is now distributed as a .zip file. It runs directly from an external media (e.g., a pendrive) and the downloads will also run and be stored in the external media.[/FONT] [FONT="] [/FONT] [FONT="]- Branding: you can now change the program icon and title bar text.[/FONT] [FONT="] [/FONT] [FONT="]- Updated the 7-Zip components to version 16.04.[/FONT] [FONT="] [/FONT] [FONT="]- In the "Final Tests" tab, the "Drivers" button will now also give the chance to disable Windows automatic drivers updates (Windows 7 and higher).[/FONT] [FONT="] [/FONT] [FONT="]- In the "Malware Removal" tab, replaced Hitman Pro with Zemana Antimalware portable.[/FONT] [FONT="] [/FONT] [FONT="]- Added a "refresh" button in the custom tools tab.[/FONT] [FONT="] [/FONT] [FONT="]- Windows Repair Toolbox used to always require a fresh download regarding any of the malware removal tools, ignoring any previously downloaded file. That no longer happens, and the behavior is now the same as in the other tools (give the option to download a new copy, or run the previously downloaded file).[/FONT] [FONT="] [/FONT] [FONT="]- Several minor improvements and fixes.[/FONT] [FONT="] [/FONT] [FONT="]Any questions, suggestions or bug reports, please let me know. [/FONT] [FONT="] [/FONT] [FONT="]Thank you![/FONT]
In the old days of XP, there was a Microsoft tool called “Fixit” that was highly user friendly and effective at repairing a wide range of problems, without requiring user expertise. No clearing of malware, but most users have their AVs to do that. Its current version seems to be a lot limited in what it can do. It would be nice if the present tool can do what Fixit used to do.
I have portable Microsoft FixIt on a flash drive I use, and a copy on my PC. It indeed is a handy tool.
[FONT="]Hi all, [/FONT] [FONT="] [/FONT] [FONT="]I've just updated Windows Repair Toolbox to version 1.8.0.1:[/FONT] [FONT="] [/FONT] [FONT="]- 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). [/FONT] [FONT="] [/FONT] [FONT="]- 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)[/FONT] [FONT="] [/FONT] [FONT="]- Updated the link to WRT homepage in the “About” tab;[/FONT] [FONT="] [/FONT] [FONT="]- Some other minor improvements.[/FONT] [FONT="] [/FONT] [FONT="]Thank you![/FONT]
[FONT="]Hi, I've updated Windows Repair Toolbox to version 1.8.0.2:[/FONT] [FONT="] [/FONT] [FONT="]- Replaced Snappy Driver Installer with DriversCloud.[/FONT] [FONT="]- Now the portable version will only display the initial licence window the first time it runs.[/FONT] [FONT="] [/FONT] [FONT="]Thank you.[/FONT]
Hi @Jari, thank you for your feedback! The extra information about the system drive is are provided by smartmontools (the same tool that powers GSmartControl). Probably that model is still not fully supported by the program (at least by the stable version, that's the one WRT is using). I'll keep up integrating the new stable versions, as they become available, in WRT. Regarding the boot environment information (BIOS/UEFI), it's still present 1.8.0.5. But it won't be displayed in a system that where the setupact.log file is missing (this will happen for instance in a computer where Ccleaner was executed with the advanced options checked, and that was the case of the computer I used for the screenshots).
From what i've tested, Windows built-in disk cleanup does not delete that file (not even if executed as admin and with all checkboxes checked).
OK, but I have setupact.log file in Windows folder, created 25th March 2017. It is an install date of Windows 15063 (15063.11 now).