There is no need to fill an issue (or any bug report) with "Me too" messages, unless some "new" information about the issue is found. We (the Rainmeter team) are aware of ALL reported issues posted on GIthub and here on the forums.Everyone who' struggling with this, please chime in on the Github issue to hopefully get the developer's attention: https://github.com/rainmeter/rainmeter/issues/377
We usually do not respond to issues or bug reports until we have something meaningful to add to the conversation. A lack of response does not mean we do not care, or we aren't paying attention. In most cases, if we haven't responded, it usually means we haven't had the time to investigate the issue.
In this particular case (#377), based on the reports so far, the issue is obviously on Windows INSIDER editions (aka, a beta release). Microsoft might fix this issue before any "official" Windows release is made. Or, they might not even know about it...since the purpose of Insider builds is to report any potential issues with them. We aren't going to prematurely attempt to fix something that might be just a temporary issue from the OS. Also, it's possible that some other app is not processing some window message correctly causing the message to not be passed to Rainmeter, but this seems unlikely.
-Brian
Statistics: Posted by Brian — Today, 5:23 pm