[Aplikace] Windows Repair Toolbox v.3.0.1.6

Téměř vše, co potřebujete k opravě problémů s Windows v jednom malém šikovném nástroji.


# Changelog
-All notable changes to the current version are documented in this file.

## 3.0.1.6 - 2019-01-06
### Added
- Added the command line argument '/minimal', that starts the program in minimal mode.
- Added the MacAddress information to the tooltip of the "OS" label at the bottom of the first tab.
- If the OS is Windows 10, when hovering the mouse over the label that gives that information, a tooltip will be shown displaying the specific version (e.g.: 1809).
   
### Changed
- In the "Useful Tools" section, replaced "Ninite" with "Firefox Portable".
- In the "Repairs" section, replaced "Zoek" with "SFCFix".
- In the "Repairs" section, replaced "Easy Fix" with "Office Uninstaller".
- Increased the countdown time in the Welcome Form.
- In "Notes" tab, the default format to insert a picture is now the .PNG format.
- Updated the 7-Zip components to version 18.06.

### Fixed
- Several things wouldn't work if Windows Repair Toolbox was located in a path containing any empty spaces (e.g.: C:\Users\User\Some Folder\Windows_Repair_Toolbox.exe):
 . The Microphone test (in the "Final Tests" tab) wouldn't work.
 . The Nirsoft password recovery tools (in the "Notes" tab) wouldn't work and will cause Windows Repair Toolbox to keep running in the background after its main window being closed.
 . The "Run Unattended" functionality (in the "Malware Removal" tab) would break if RKill, TDSSKiller or KVRT were selected to run.
- RKill whitelisting functionality doesn't support paths containing empty spaces. So, if Windows Repair Toolbox was located in a path containing empty spaces, RKill would terminate it (heuristic detection).
 Until that is fixed, the possible workaround was to prevent RKill from running when it's located in a path containing empty spaces (and informing the user about the reason why).
- The program "Crucial System Scanner" takes some time to close itself after doing its work (it continues to run in the background for awhile).
 So if the user tried to execute it again before allowing it to close the program wouldn't work. In order to avoid this, WRT will now check if the
 program is already closed before allowing to run it again (otherwise it will ask the user to wait and try again in one minute).