Hi,
I'm currently considering to suppress the use of VBScript engine in Windows 10 due to security reasons.
I found that HDS creates three VBS Scripts in %APPDATA% directory and at least one in the TEMP directory. I wonder what is the purpose of these scripts and what do I lose if I prevent running the scripts.
And is there a way to prevent the scripts to be created at all?
I would just like to understand what they are used for and their importance in HDS functionality.
Purpose of VB Script files hds_control_*.vbs etc
- hdsentinel
- Site Admin
- Posts: 3115
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Purpose of VB Script files hds_control_*.vbs etc
These scripts designed to communicate with Windows Scheduler: to create, check existence and delete the scheduled task (which launches Hard Disk Sentinel when the current user logs in).
When the software is configured to start automatically and there is no change in this setting (no change of Configuration -> Preferences -> Load with Windows option) then I can confirm these are not required at all.
Hard Disk Sentinel saves these to %APPDATA% folder (as you wrote), it uses the temp folder only in the case if the %APPDATA% folder can't be determined somehow.
Apart from controlling the automatic startup, they have no importance/use at all.
If you prefer, you may completely disable the "Load with Windows" option and create a scheduled task manually
(as described at viewtopic.php?f=6&t=10694 )
so then even the files may be there, they will be not used and things will work if VBScript engine is completely disabled.
When the software is configured to start automatically and there is no change in this setting (no change of Configuration -> Preferences -> Load with Windows option) then I can confirm these are not required at all.
Hard Disk Sentinel saves these to %APPDATA% folder (as you wrote), it uses the temp folder only in the case if the %APPDATA% folder can't be determined somehow.
Apart from controlling the automatic startup, they have no importance/use at all.
If you prefer, you may completely disable the "Load with Windows" option and create a scheduled task manually
(as described at viewtopic.php?f=6&t=10694 )
so then even the files may be there, they will be not used and things will work if VBScript engine is completely disabled.