ROCKNROLL

I noticed it when running lots of tabs. No more memory restrictions and slightly better performance. Also, 64-bit has better exploit protection, but that's more under the hood type stuff.

I fixed that already in the second URL I posted above.

Thank you for going through Winapp2 and finding issues like this. I have done a big overhaul of Winapp2 not too long ago, but I must have missed issues like these. And yes, I keep all the entries in ABC order, so I would appreciate if you can keep them like that as that was one goal of the overhaul. I have been passing along suggestions to Andrew (owner of BleachBit) to improve his error checking tool for Winapp2 which he uses for his program. It is very similar to Winappdebug, but checks for more errors and more throughly. I have talked to Shane (owner of System Ninja, as well as all Winapp2debug, Winappparser and CCDump) about updating Winappdebug with some of the suggestions you have have mentioned before as well as combining with Andrews tool, but unfortunetly, Winappdebug does not analyze each line of Winapp2, but rather checks the whole entry, so it is very limited and would require a rewrite to change it, for which he does not have the time to do. It is OK as Andrew tool works, but it is a Python script that I do not really know how to use but when I send a update copy to him once a month for BleachBit, he uses the tool for us and sends the errors to Winapp2 Github page.

Updates: https://github.com/MoscaDotTo/Winapp2/commit/8d0256ac6e6d6a4887ca1eabea4cb835c83f9d7d https://github.com/MoscaDotTo/Winapp2/commit/b762e17bcdf19be4e33e9a7ae7eabd40516df3e1

MS dropped support for Windows Live quite a long time ago. Hardly anything ever used it. I do know some games that did, however servers don't work through it anymore, so deleting it wouldn't have any issues.

Updated: https://github.com/MoscaDotTo/Winapp2/commit/237280dca025c23c9943ed13ab884ade6b4a6e68

Updates: https://github.com/MoscaDotTo/Winapp2/commit/d5a8f38ca0669842f9a2ee2318cdf945d3c72069

I made the fixes: https://github.com/MoscaDotTo/Winapp2/commit/a891a4b26f8e82901103ade3ebd5c42010db3776

Do people still use this? Also, your FK10 makes no sense, please fix it.

Updates: https://github.com/MoscaDotTo/Winapp2/commit/fc54e3b72fd840e829849dd8efe023416c507801 I won't add the temp entries within other entries like that because some people don't want to remove temp files, or maybe only wants to remove it after sometime and mixing them up with other entries would not be good.

Updates so far: https://github.com/MoscaDotTo/Winapp2/commit/ad1d5f32575ebafce9f5bbe414ee797c127d5c7d https://github.com/MoscaDotTo/Winapp2/commit/f677f2d249d72f092dfcfeec7ffedc8faa46dac4

So what does everyone think about the upcoming Windows Core OS, aka Andromeda OS? I guess it is going to be able to run everywhere, PCs, Mobile, embedded systems, servers, etc. I think it is something MS should have done with Windows Vista, to be honest. I believe this will also use the new file system from MS, Resilient File System, aka ReFS. Can read about some of it here: https://www.windowscentral.com/windows-core-os

Updates: https://github.com/MoscaDotTo/Winapp2/commit/b416c527297db1f3d0b6efd0d9dc5d63af496eb4

Does everyone else agree with removing the old AVG 2013-2015 entries as well as removing AVG safeguard? I mean the new AVG is free so people shouldn't have a issue with using that. Also, AVG 2017 does work on old XP system, too.

Feel free to make this yourself. We don't usually take suggestions for cleaning rules, unless someone has made one and tested it out.

The AVG antivirus more is for 2013-2015, while the other one is for newer ones. We had discussed this in the past and everyone seemed to agree to keep them. They are old and I am not sure if these versions still receive updates. Updated the rest: https://github.com/MoscaDotTo/Winapp2/commit/075e0ed23c5aa5dd253012573f23d70efc91fcab https://github.com/MoscaDotTo/Winapp2/commit/a4069bdf325044ac12d7f3d9e118d9271e749353

The thing with backdoors and vulnerabilities is that they can come in surprises. They are made on accident and requires lots of research to determine where they are happening from. I don't think they can "guarantee" that there isn't anymore holes. No software can, not just CCleaner. 64-bit has slightly better protection and much better memory management.

Updated: https://github.com/MoscaDotTo/Winapp2/commit/7a438320e029f29d683ffb7c7ace71047d94e112

Unless you tell me which ones specifically, I don't know what they are. If you could list them, I would be willing to fix them for you. Committed your other suggestions though: https://github.com/MoscaDotTo/Winapp2/commit/c87510d69375d5367087fe0c4da7814ac06b8dd6

Updated: https://github.com/MoscaDotTo/Winapp2/commit/cc69a83ee5126add82d566e2b45939175915b876

Actually most to all features comes from the community. Mozilla mostly just does security updates. I think the screenshot feature could still be useful. I usually use snaggy because it's simple and doesn't need some account, but this might be the replacement I needed.

I just uploaded a new and improved WinappDebug: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/WinappDebug The new additions include some enhance checking and now looks for duplicate title names.

For now, I just removed the entry, unless anyone can come up with a better use for that entry: https://github.com/MoscaDotTo/Winapp2/commit/5bb86c240c126e972f3f771135940fbedd690f60

Please review this issue: https://github.com/MoscaDotTo/Winapp2/issues/105

Maybe we could make a Winapp3 topic and then write all more aggressive entries there, including language entries like these.