Ole_Pete_Backup had a good suggestion…
You can create a .cmd file to stop the WDFMEService and a .cmd file to start the service when you need it.
Saves time going to the services panel every time.
Probably a good idea to set the WDFMEService to manual instead of automatic startup first.
Then…
Do the following (My example on Windows 7 64 Bit) your software location may vary.
Once you have finished with a backup…and want to recover CPU back from the WDFMEService…
Simply stop the WDFMEService via a .cmd file as per below:
Create a file with notepad (WDstop.cmd) for example with contents like this:
cd C:\Program Files\Western Digital\WD SmartWare
net stop “WDFMEService”
(Note: you need to double quote the name of the service)
Save the file where you want and create a shortcut to it.
Then, when you want to stop the WDFMEService (after a backup is finished and stopped) just double click on the shortcut.
Conversely: To start the WDFMEService prior to setting a backup going…
Create a file with notepad (WDstartup.cmd) for example with contents like this:
cd C:\Program Files\Western Digital\WD SmartWare
net start “WDFMEService”
(Note: you need to double quote the name of the service)
Save the file where you want and create a shortcut to it.
Then, when you want to start the WDFMEService just double click on the shortcut.
A real CPU resource saver. :manhappy:
Oh…BTW:
Since the WDFMEService hogs CPU anyway… You may as well _ untick _ the “run backup when computer is idle” check box in software settings.
This seems to speed up the backup even though no more CPU is consumed with this setting compared with the software performing no action anyway! (Go figure)