[BUG] Rainmeter 4.5.12.3616 crash with UsageMonitor Plugin skins

[Brian]

No problem and thanks for all the testing!

-Brian

[visormail]

Hi, I have the same problem but on Windows Server 2022 (and with the previous 2019), it has built in .Net Framework 4.8

Currently installed "classic" .NET Versions in the system:
2.0.50727.4927 Service Pack 2
3.0.30729.4926 Service Pack 2
3.5.30729.4926 Service Pack 1
4.0.0.0
4.8.04161

With the Rainmeter 4.5.13 and with some previous versions too.

In the C:\Program Files\Rainmeter\Rainmeter.exe.config file, there is no SKU= part.
The content of it:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" />
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>

And the issue. I set this to the ini file:

[MeasureTop]
Measure=Plugin
Plugin=UsageMonitor
Alias=CPU
Index=1

or this:

[MeasureHighestUsedRAM]
Measure=Plugin
Plugin=UsageMonitor
Alias=RAM
Index=1

When I refresh the skin, the plugin is working, it shows the values. But if I close rainmeter it never starts again, until I comment out the Plugin=UsageMonitor row, rainmeter is crashing.

[SilverAzide]

Hi, I have the same problem but on Windows Server 2022 (and with the previous 2019), it has built in .Net Framework 4.8
...
When I refresh the skin, the plugin is working, it shows the values. But if I close rainmeter it never starts again, until I comment out the Plugin=UsageMonitor row, rainmeter is crashing.

Have you seen this post? Perhaps it might help, or at least rule out a possibility...

[visormail]

I have tried it earlier, that doesn't help. Now tried again and nothing.

C:\WINDOWS\system32>cd c:\windows\system32
C:\WINDOWS\system32>lodctr /R
Info: Successfully rebuilt performance counter setting from system backup store
C:\WINDOWS\system32>cd c:\windows\sysWOW64
c:\Windows\SysWOW64>lodctr /R
Info: Successfully rebuilt performance counter setting from system backup store

Then the problem is the same, it's working until I close it, then doesn't start again. And this problem is way older than April 2022.