Jump to content

ROCKNROLL

Experienced Members
  • Posts

    515
  • Joined

  • Last visited

Posts posted by ROCKNROLL

  1. [Malwarebytes Anti-Exploit*]LangSecRef=3024DetectFile=%CommonAppData%\Malwarebytes\Malwarebytes Anti-ExploitDefault=FalseFileKey1=%CommonAppData%\Malwarebytes\Malwarebytes Anti-Exploit|*.logFileKey2=%LocalAppData%\VirtualStore\ProgramData\Malwarebytes\Malwarebytes Anti-Exploit|*.log

    FileKey1 doesn't exist on my system. Also, I think we can just combine this entry with this one:

    [Malwarebytes Anti-Exploit Logs*]LangSecRef=3024Detect=HKLM\SYSTEM\CurrentControlSet\Services\MbaeSvcDefault=FalseFileKey1=%CommonAppData%\Malwarebytes Anti-Exploit\|*.LogFileKey2=%ProgramFiles%\Malwarebytes Anti-Exploit\|mbae-uninstall.log;changelog.txt
  2. Speaking of duplicates, these entries are all duplicated:

    [Polarity Cache*]LangSecRef=3022DetectFile=%ProgramFiles%\PolarityDefault=FalseFileKey1=%AppData%\Stanley Lim\Polarity\Cache|*.*|RECURSE[Polarity Cache*]Section=BrowsersDetectFile=%ProgramFiles%\PolarityDefault=FalseFileKey1=%AppData%\Stanley Lim\Polarity\Cache|*.*|RECURSE[Polarity Favicon*]Section=BrowsersDetectFile=%ProgramFiles%\PolarityDefault=False[Polarity Favicon*]LangSecRef=3022DetectFile=%ProgramFiles%\PolarityDefault=False[Polarity History*]LangSecRef=3022DetectFile=%ProgramFiles%\PolarityDefault=FalseFileKey1=%UserProfile%\Polarity_Config|history_times.ini;savedTabs.ini;history.ini;history_names.ini;history_times.ini;downloads_urls.ini;downloads_times.ini;downloads_names.ini;[Polarity History*]Section=BrowsersDetectFile=%ProgramFiles%\PolarityDefault=FalseFileKey1=%UserProfile%\Polarity_Config|history_times.ini;savedTabs.ini;history.ini;history_names.ini;history_times.ini;downloads_urls.ini;downloads_times.ini;downloads_names.ini;

    I just don't know which section is the proper one to use.

     

    EDIT: I just realised the "Polarity Favicon*" don't even have FileKeys to them. Weird...

  3. Can you add support of Eraser 6 ?

     

    [Eraser 6*]

    LangSecRef=3024

    Detect=HKCU\Software\Eraser\Eraser 6

    Default=False

    FileKey1=%ProgramFiles%\Eraser|schedlog.txt

    FileKey2=%LocalAppData%\Eraser 6\Logs|*.log

     

    I think we can just combine this with this entry:

     

    [Eraser*]

    LangSecRef=3024

    Detect=HKCU\Software\Heidi Computers Ltd\Eraser\5.5

    Default=False

    FileKey1=%ProgramFiles%\Eraser|schedlog.txt

    FileKey2=%LocalAppData%\VirtualStore\Program Files*\Eraser|schedlog.txt

  4. Besides which, I thought it was recently decided that more* entries should be reserved for entries that double winapp1.ini entries not doubling winapp2 entries (but maybe I made that up idk spoiler alert: it was literally less than a month ago).

     

    Would "Store Extras*" be acceptable?

     

    Anyways, what I meant by what I was saying was that, since I am not usually logged in, it isn't a problem for my system. That's why I recommended moving to a different entry and add a warning. I mean this is kind of the samething with removing passwords in FireFox/Chrome/Edge/IE/etc (yes I know you said unlike websites).

  5. If you dont use the app the way a normal user would, how can you be sure if the entry is good/bad?

     

    I never said I don't use the store, I only said I a, just usually not signed into it. I use the store often, and you don't have to be signed in to use it, either.

  6. I have done enough testing before I recommend these changes. Looks like Windows 10 build 1607 is affected.

     

    What if we moved them to a separate entry called Store More* and put a warning that it will sign you out of Store and such? Store cache and temp files build up quickly if you use the Store often. I am usually never signed into Store to begin with, so I don't see this happening.

  7. Removed:

    Deleting files from these locations signs out of the Windows Store and messages start to pop up in Action Center.

    %LocalAppData%\Packages\Microsoft.WindowsStore_*\AC\INetCookies|*.*|RECURSE

    %LocalAppData%\Packages\Microsoft.WindowsStore_*\AC\TokenBroker\Cache|*.*|RECURSE

    %LocalAppData%\Packages\Microsoft.WindowsStore_*\TempState|*.*|RECURSE

     

    Are you sure? I am not seeing this happening on my Windows 10.

  8. Ah i think i misunderstood again. I have the items checked (the ones i want to keep on winapp2). As I've always ran trim every time it gets updated i have always kept it that way.

     

    Anyway... I managed to get a screenshot of the error i'm getting before trim.bat closes. It gives those errors every time i try to run it.

     

    http://imgur.com/a/GgjGo

     

    Try putting quotes around the file, like "Winapp2", as it says for step 2 on the site. If that doesn't work, try putting the trim.bat in the exact same place where Winapp2 is (looks like you have it in a folder called TRIMMER now?).

  9. Still the same.

     

    Also it's saying that 'MORE' is not recognized as an internal or external command upon starting the trim.bat.

     

    Try what dvdbane said. If none of those work, make sure you are not running CCleaner (even in background, check task manager to make sure) and make sure to run trim.bat as admin rights. If none of those work, try running it under safe mode. That has sometimes helped for me.

  10. I wonder if Smalik will return once it's up on GitHub. I know he didn't seem to like it here at Piriform anymore, but I would hate to have to lose someone who was so dedicated to this project.

  11. Also, I think it would be best if we waited on suggesting entries until he has it up and running on GitHub. That way we can make them as pull requests without having to have him go through all these pages and re-add them himself.

  12. Wonder what would happen if the graphics card went kaput, install a brand new one, and that old installer won't install due to incompatibilities with the new card.

     

    I don't know about Nvidia, but I do know that AMD drivers are universal. The drivers should be able to run on any card. I assume the same should be for Nvidia.

  13. Hi folks!

     

    Sorry I've been away without contact. And doubly sorry that I really can't discuss why.

     

    I haven't had time to read what I've missed here just yet but I should like to restructure how this operates, such that it can at least continue to function well should I lose access to my machines again

     

    As such, I'd like to migrate to Github! I'll get around to this in the coming weeks when more things have settled. I hope to have this going in time for the next CCleaner update, but if not certainly it'll follow shortly after. I'm not too experienced with Git, so I may need a little guidance from some of you experts in the crowd :)

     

    Again, sorry for the communications embargo the last few months. Wasn't much of a choice on my part.

     

    Hope to resume in full swing shortly, I appreciate the patience and commitment to the project you've all shown in my absence. Be well, I shall return soon :)

     

    I assume you got my email then, right.

     

    GitHub is actually pretty simple. Everything is pretty straightforward and I have a lot of experience with it. I might recommend you add some admins with it, so when you are away, there is someone else to take over for awhile.

     

    I talked about this in the email I sent, but I will say it here. Consider making 2 Winapp2 files, one for CCleaner and 1 for all other cleaners. That way, when you remove entries for CCleaner, people can download the one for CCleaner, while the other cleaners don't lose their cleaning abilities. Sorry, I know we are not aloud to talk about other cleaners, but it is a good idea to do.

     

    Anyways, no need to apologize for anything. You don't owe us anything and it's not like you are getting paid for it, you know other then donations.

  14. Hi... trim.bat has stopped working for me. I realize the version of winapp2.ini is a little behind the times but, I've installed some softwares and uninstalled others since the latest iteration and was just trying to re-customized the winapp2 file to more accurately reflect my current setup. Upon re-downloading the latest winapp2 file from the website, I am encountering an impasse when trying to accomplish my mission. http://i64.tinypic.com/4raqzr.jpg

     

    Make sure you are running trim as administrator. Also, make sure you are clicking "Analyze" and not "Run Cleaner" during this operation.

  15. Fully agree and understand.  I just wanted to re-enforce that they should not be removed by presenting a real-time example from my systems.   ;)

     

    Maybe you can find a way to have those log/old files to be removed while leaving the ExcludeKeys intact.

  16. everything else ccleaner does is plaintext and not behind codewall.

     

    Maybe I just misunderstand what you meant by this, but CCleaner is not open-source, so thus everything CCleaner does is behind a "codewall". Maybe you meant winapp/winapp2 that is not behind a "codewall" and are written in plain text.

  17. CustomLocation only affect entries without *

    so currently cc only clean entries without *

    winapp2.ini = entries with *

     

    Wow, and here I was thinking CCleaner was ahead of the game. Looks like that isn't the case.

  18. I would suggest just leaving the situation as it is.  I only speak for myself, not the Piriform people. 

    When Winapp has time to make changes, he will, and we will be grateful for the update. 

     

    The pressure of school endeavors is enough, there should be no additional pressure on Winapp.

     

    Talk of ownership, and what could be done if push came to shove, is an unpleasant direction to take.  It could have negative consequences for Winapp himself, and for the winapp2.ini project which has been so helpful to so many for so long.  And no, I am NOT going to outline the many possible negative consequences.  

     

    There are however a few issues related to plain old good manners, such as:

    If I was an artist, I would not want my work shown publicly by anyone except me. 

    If I was an author, I would not want each draft of my work exposed unless I decided it was ready. 

    If I was a software developer, I would want to be the one who decides if or when it gets released, or posted, or whatever. 

     

    But the bigger issue, imho, is that the work (the .ini file) is already publicly available, for free, here on this forum and other places. 

    It is built for use with an application called CCleaner, also free. 

    If CCleaner users decide to use the winapp2.ini file, they can get it here.  I bet 99.99 percent already know that. 

     

    So just leave it alone.  Winapp2.ini himself has already decided where it belongs. 

     

    Edit:  Winapp may come along and blow my philosophical maundering completely out of the water by saying "Sure, post it wherever you like", but that should be his choice.  :)

     

    But that is the thing. If he did throw it on GitHub, it would take a lot of the pressure off for him. What he has to do now is add all the entries in manually, but if he put it on GitHub, all he would have to do is click a button and it is done already.

     

    What you should also realize is that Winapp2 is not just for CCleaner anymore. There are 3 other cleaners that use Winapp2. I always see entries get removed because they were added to CCleaner, which isn't fair for the other cleaners as they lose some cleaning ability then.

     

    Smalik is also right that it isn't just Winapp himself that makes this all happen. We all have been contributing entries to Winapp2 for years now. 1 person wouldn't have made all this happen by himself. A little appreciation towards people who have been contributing their time to make entries wouldn't hurt once in a while.

  19. I don't know about him, but some of the admins here will get upset on this suggestion. I know they have insulted you previously when you asked when this file would be updated. The exact same thing happened to me a while ago. Some of the admins here are like dictators.You remember when he said that Winapp2.ini will be updated twice a month. Now, it isn't even updated ONCE a month.

     

    Well, since Piriform doesn't own Winapp2, they can't really do anything about it if someone did. Why do you think they would be against this, though?

     

    Trust me, it's not only the admins that get fed up with people getting pi**y about the file not being updated. It's something that is done by winapp, on a voluntary basis, fitted around school and real life commitments, nothing to do with Piriform and with nothing in return for his time and effort. So when people start whining at the lack of an update it's a pretty crappy way of showing your 'gratitude' for said time and effort. ESPECIALLY as all the entries are HERE, if you're that desperate for any of them, copy them from here to your winapp2 file yourself :rolleyes:

     

    That is kind of why I offered to put it on GitHub for him. So he has some help with all this and show our appreciation to him.

     

    Of course if I were to do such a thing, I will still give full credit to Winapp2 for his years of dedication.

  20. @Winapp2.ini, I have spent lots of time to make/correct the entries that I provided here since you updated the file last time. Can I send all of them in a .txt file so you won't miss them in the next update?

     

    Do you think he would be mad if one of us put Winapp2 on Github for him? That way, all the entries would be there and be much less chance of him missing future entries.

  21. Edit entry:

     

    [Log Files More*]
    LangSecRef=3025
    Detect=HKCU\Software\Microsoft\Windows
    Default=False
    FileKey1=%WinDir%\inf|*.log*
    FileKey2=%WinDir%\Panther|cbs.log;DDACLSys.log;miglog.xml;Migrep.html;PostGatherPnPList.log;PreGatherPnPList.log
    FileKey3=%WinDir%\debug\WIA|*.log
    FileKey4=%WinDir%|SIGVERIF.TXT
    FileKey5=%WinDir%\System32\sysprep\Panther\IE|diagerr.xml;diagwrn.xml
    FileKey6=%WinDir%\Panther\UnattendGC|diagerr.xml;diagwrn.xml
    FileKey7=%WinDir%\Panther\FastCleanup|*.log
     

    Removed FileKey 3 because it is a file that cannot be removed anyways and only generates a permission denied error in BleachBit.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.