Ok, then only the corrected hash value (which has nothing to do with VirusTotal Results) ... it should be ......
The displayed hash value for .NET 8.0 is wrong (the linked is correct): It should be ~ Removed VirusTotal Results as per Policy ~ see the...
All right! Then I will remove those unmaintained. Thank you for clarification!
Oops, I should slow down sometimes ;-) But I see different included translation files where are NOT up-to-date - maybe from older v6.9.7.0 or so,...
JFI for translating Changed from v6.9.7.0 to v6.9.8.0: Changed string: 414 Deleted string: 421
@alexandrud Thank you for new version! Yes that makes really sense! Greetings
@alexandrud Sounds GREAT! Thank you!
@alexandrud I will see, what I can do about this (.NET v7.x) ... Greetings PS: Ok, I could now install the .NET Desktop Runtime 7.0.13 and this...
It's the latest, which is installed from MS AUTOMATICALLY (through Windows Update) on my system here! I saw the recommendation, yes, thanks.
With "official" I meant, not official automatically installed on all Windows 10 machines. HERE in my Windows 10 Pro version (Microsoft Windows 10...
No, please not - please stay with "official" MS .NET versions. I still have .NET 4.8.x on my Windows 10 Pro system and don't want to install the...
Hmm ... that sounds not good with that experimental function (UPPERCASE expeptions). Alexandru, have you news about that? Greetings
Ahh, yes - of course. I had forgot the sense and mechanism of secure rules, sorry.
At least I haven't this problem WITHOUT Secure Rules activated till now (tested few times only) not tested with Secure Rules activated. So that...
@AmigaBoy Yes, here too!
There is a "." after winstore ... so the right name would be "WINSTORE.APP.EXE". Greetings
Ty ty :thumb::thumb::thumb:
@alexandrud The Malwarebytes logo is missing, see here: [ATTACH] Greetings.
Then I was wrong here, sorry! Ahh, ok - I understand. Not a big deal, it's also the first time I noticed it :) Thank you! Thank you for...
@alexandrud [WFC v6.9.4.0] - The rules with @ (MS Store rules) are now editable (at least the APPLY button is no more greyed out)? Is that...
@alexandrud Thank you very much for new version! There is another updated language string: from ... 934 = This field must be a numeric value...
@alexandrud Sounds perfect!
@alexandrud In the test version v6.9.3.0 (maybe in older versions too? I can't remember *g*) we have a column Edge traversal for outbound rules...
@yeL Here it works correct. So at least it seems no generally bug.
@alexandrud In the test version 6.9.3.0 I noticed that the Extended Properties column no longer works (empty). Additionally it's also editable...
Separate names with a comma.
