7 replies to this topic

[metalj]

I've been using CCleaner for quite a while...

Now I notice that the registry cleaner checks my floppy drive when checking for registry errors...

Any ideas?

[Andavari]

If you have secure deletion enabled that I know for some reason will query my floppy drive when just using the Cleaner, not the registry cleaner.

I haven't had that issue with the registry cleaner doing it though.

I wouldn't necessarily deem it a bug though, as many programs query the floppy drive, for what reason I don't know.

[Augeas]

There's some option in the BIOS which I have long since forgotten (no flop any more) which stops this annoying rattling of the flop drive. I'll try to dig it out if you're interested.

[Alan_B]

When Registry Cleaner is run from my daughter's profile, it offers to delete entries for Applications which are removed.

It ALSO does this for an application which, in their stupid folly, M.$ installed in my user profile, which was therefore invisible to Registry Cleaner when run in a different profile.

It seems to me very possible that at some time a floppy drive executable was run, and Windows automatically added relevant entries to the registry, and the Registry Cleaner will automatically look at Drive A to see if the executable is still there - hence it rattles and bangs.

I suggest you :-
1. Format a floppy so it is readable, but has no files which might correspond to what the Registry has recorded;
2. Remove the floppy and reboot to ensure Windows knows nothing about the floppy;
3. Start Registry Cleaner and then insert the floppy disc.

If Registry Cleaner then offers to remove entries corresponding to executables absent / un-installed from Drive A:\ you will know exactly what it was looking for, and you can then clean those references so it will not rattle and bang any more.

NB If you never ran / installed the "missing" executable, you might like to challenge everyone else who had access to the computer - if you tell them what they ran, they may confess to other miss-deeds !!!

Regards
Alan

[metalj]

FIXED IT!!!

Sorry Piriform guys, but this is not a bug.
It seemed more like a weird problem with my registry.

All I did was to run the COMODO REGISTRY CLEANER and reboot.

Thanks to everyone who replied.

[metalj]

Nah, I didn't fix a thing.
It came back again.

But I noticed that it has something to do with the "MUI Cache".
Every time the registry cleaner checks for "MUI Cache" errors (but doesn't find any) the floppy drive turns on (like checking for a floppy).

I repeat: this is not a bug; it’s some sort of weird problem with my PC.
Any suggestions will be appreciated.

[Alan_B]

MUI Cache was one of my suspects - it still is.

Did you do the tests I suggested ?
What were the results ?

Perhaps a Floppy disc file has been read/written in the past, resulting in registry entries/pointers/etc.
When CC cleans the registry it tests such registry entries/pointers/etc for current validity,
so anything that was on Drive A:\ will still need to be on drive A:\.

If you run CC with no floppy disc loaded, the drive will click and bang,
and the O.S. will report to CC that the removable drive is absent, and CC will abort that test.

If instead you run CC whilst an empty floppy (formatted but no files) is present,
then the O.S. reports that the relevant file is absent,
and THEN you may expect CC to tell you what file it wanted to find.

Regards
Alan.

[metalj]

I FIXED IT!!! and this time for real!!!

Thanks Alan for your reply.
I did exactly what you told me, but nothing.
Still, you were right!
I did was using a floppy some days ago.
But it seems that CCleaner is not cleaning removable drive's MUI Cache.
I was googling around and I found this:

HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\MUICache

There I found the value that was disturbing me.
But I also found some values from my thumb drive too.

CCleaner is definitely not cleaning removable drive's MUI Cache.
(I had the same problem on another computer)
That can be a bug! or maybe this feature is not included.

Thanks again Alan for your reply.