Merge 32 & 64 bit nodules

While the concept of a CCleaner that is individually customized for 32 bit & 64 bit sounds nice, 32 bit CCleaner will clean a 32 bit OS great.

But try the 64 bit in a 64 bit OS. Now, you have 32 & 64 bit software in a 64 bit OS!

Does this mean that only way to clean both, is to run both CCleaners?

This seems inefficient!

What's going on here?

A way to combine them please?

Clean 32 AND 64 bit in one pass?

I'm not sure what you're getting at... the advantage of the 64bit version is its ability to work in a 64bit environment.. it doesn't clean any differently (other than that) than the 32bit version AFAIK, unless it just looks towards SysWOW64 instead of System32 in some cases.

Applications from the pre-64-bit era are most unlikely to even know of SysWOW64.

32 Bit Applications never look at SysWOW64,

but every time they attempt to access System32 they never get there,

because 64 Bit Windows is a con artist and it gives them SysWOW64 because this is where the 32 bit DLL's have been evicted to,

and the System32 is now occupied solely by 64 bit DLL squatters.

64 bit stuff in sytem32, and 32 bit stuff in sysWOW64.

You aint seen nothing yet - wait for M.S. to roll out 128 bit code.

N.B. 32 bit applications CAN see 64 bit DLL's if they look at SysNative,

but this is a "magic spell" - a special re-direction that does not work for 64 bit applications,

and 32 bit applications must know the exact term - they will never know about it via searching for "Sys*"

I have learnt much from replies to my topic at

http://forum.piriform.com/index.php?showtopic=32083

I have raised my concerns about 32 bit CCleaner being deceived by Windows deception into doing damage, but not yet received response, at

http://forum.piriform.com/index.php?showtopic=32222

To all the above I will now add that I find TREESIZE is able to show that System32 is much larger than SysWOW64,

and RevoUninstaller claims to work well on 64 bit systems,

BUT TO MY SURPRISE,

I cannot find a choice of 32 bit or 64 bit downloads for either.

I assume that 64 bit applications cannot be used in 32 bit hardware,

so assume both of these are 32 bit applications with the special ability to avoid 64 bit O.S. con tricks,

and presumably see and/or zap 64 bit DLL's via SysNative.

I believe 64 bit CCleaner can see and therefore delete items in both system32 and SysWOW64,

and it needs to process SysWOW64 to deal with junk from stray 32 bit applications.

I do not know what it does in this respect.

@ WinApp2.ini - Sorry my friend, but you have a big job ahead.

I gave up after counting more than 40 FileKey24 items that zap bits out of System32, such as

FileKey24=%windir%\System32\config|SAM.jv16pt_bak.LOG2

But nowhere do I see a SysWOW64.

I have also spotted two off DetectFile=%WinDir%\System32

The first enhancement we need is to repeat all instances of System32 with SysWOW64

The second enhancement we need before release is to ensure that residues from an uninstalled 32 bit application do not damage its 64 bit upgrade (and vice versa),

and that may require extra detection capabilities.

Have a very nice day ! ! ! !

Leave it to MS to get things wrong.

This is why I wish MS left 32 bit program directory and system directory alone, instead of defaulting the 64 bit to take over the old 32 bit directories, and assigning the 32 bit to new ones.

Example:

program files directory in a 32 bit OS -> C:/Program Files

program files directory in a 64 bit OS -> C:/Program Files

Pretty normal seeming, till you realize that now, 64 bit are C:/Program Files & 32 bit are C:/Program Files (86).

What MS should have done, is just let C:/Program Files stay as 32 bit directory, then add a C:/Program Files (64) for 64 bit programs.

That would solve everything!

Although, I still would like to have a 32 + 64 bit cleaner!

Example:

Windows 7 64 bit comes with Internet Explorer 32 & 64 bit.

Users can use either.

But using both creates trash under the 32, and also the 64 bit IE.

32 bit only cleans 32 bit apps, while 64 bit cleans only 64 bit apps.

Why leave 32 bit trash on 64 bit systems?

Why can't CCleaner clean 32 + 64 bits on a 64 bit system to get ALL the trash?

I'm not sure how you're all managing to run the 32bit on a 64bit OS, every time I try to open it, it opens the 64bit anyway.

Sometimes applications are 32 bit only so 64 bit Windows gets 32 bit junk.

I do not know whether or not 64 bit CCleaner attempts to purge SysWOW64 etc.

It would be nice if it does.

Ditto Program Files (x86)

The same desires apply to WinApp2.ini (the file not the person)

This means zapping both SysWOW64 and System32

Ditto Program Files (x86)

It also means any Detect File that considers Program Files must also consider Program Files (x86).

Candles burning till Midnight for some one ! ! !

CCleaner actually looks through both when you put in %ProgramFiles% from what I've been able to tell.

As for SysWOW64 and System32, those would need double entries.

If you want to give it a try to confirm, try this:

Make a file in \Program Files(x86)\ named Test

put in a file, any file, but just one, doesn't matter.

[*Test*]
LangSecRef=3021
DetectFile=%ProgramFiles%\Test
Default=False
FileKey1=%ProgramFiles%\Test|*.*
FileKey2=%ProgramFiles(x86)%\Test|*.*

Now, open CCleaner and analyze for this entry. It will pick up 2 files, despite only having one in the folder. When you clean, however, there will be only one file cleaned, because to CCleaner the two paths point to the same location.