winapp2.ini: 32-bit architecture vs. 64-bit environment variables
Bug #1301112 reported by
Andrew Ziem
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BleachBit |
Fix Released
|
Medium
|
Andrew Ziem |
Bug Description
Hi. I use PeerBlock and that was added a few months ago in winapp2. CCleaner detects PeerBlock OK on my system but BB doesn't.
[Peerblock*]
LangSecRef=3024
DetectFile=
Default=False
FileKey1=
I just contacted by winapp2 about this and apparently CCleaner isn't having this issue. The issue is that BB is not detecting it at all, meaning it is not showing up in the cleaning rules at all. I have PeerBlock installed under the Program Files (not x86) where 64-bit applications are installed under Windows 7.
ROCKNROLLKID
summary: |
- winapp2.ini: peerblock not detected as installed + winapp2.ini: peerblock not detected as installed (likely 64-bit issue) |
tags: | added: winapp2..ini |
To post a comment you must log in.
Also, Piriform mentioned this "The interesting bit is that CCleaner corrects internally for programfiles vs programfiles(x86) (as we learned 3½ years ago in this thread).. Try moving it to programfiles(x86) just to see what happens, I guess." I am not sure if BleachBit is capable of that either. x86 for windows users if 32-bit the other on is for 64-bit and my path directory is in 64-bit, so is it possible that BB doesn't detect 64-bit applications for winapp2 entries? Just another thing to look into for future entries. Otherwise, it is probably a wildcard issue and BB needs to add detection for wildcards.