When rainmeter crashes because of a skin using this plugin, I've found a workaround to fix it until the next time it crashes.
Run this batch AS ADMIN creating a shortcut in your start menu:
Once BITS has run, Rainmeter will be able to start again after 1 or 2 minute. Run the batch again after 2 minutes if Rainmeter can seem to work.
Code: Select all
@echo off cls title Restart Background Intelligent Transfer Service Net stop BITS Net start BITS @ping localhost -n 30 >nul exit
Actually, it will report that the Background Intelligent Transfer Service is not running and that's the issue it will fix.
It seems that BITS keeps stopping for unknown reasons. There is no warning or error in windows log, just saying that it stopped correctly but with a delay of 28458.187 seconds or so but it's not accurate because it actually auto stop after about 120 seconds after I run it with the batch.
I enabled more logging (event viewer/app & services log/Microsoft/windows/bits-client/analytic) to understand what trigger its end so often and it is normal. I couldn't find something weird. It stops a 1 or 2 minute after I run it. Rainmeter keeps working for a while (≈10 min) after that and ends up crashing.
I'll see if I have to end up creating a schedule task to run Net start BITS command every 5 minutes to prevent rainmeter from crashing.
Please, report here if bits is running on your computer and if you see warning about its end in event viewer/app & services log/Microsoft/windows/bits-client.
If you have idea about why running BITS fix TopProcesses plugin and possible solution to fix it, you're welcome.