Hi @Peanut99 What you describe, with only sometimes getting the 'Browser Cleaned' notification and other times not, sounds as if it's being caused by a known bug.
You can check for this yourself, see below.
Some users have noticed that for an as yet unknown reason Smart Cleaning will sometimes turn off following an automatic clean.
That is - Smart Cleaning it will do an automatic clean once (giving you the notification) and then stop running (so no more notifications).
As you rightly say, that shouldn't be happening and is a bug. But it's not yet clear if the bug is in CCleaner or in Windows itself.
So if one automatic clean has been run, and Smart Cleaning has wrongly got turned off, then Smart Cleaning won't restart again until you either open and close CCleaner, or restart your computer.
You yourself are doing that by manually opening CCleaner when you don't get a Notification that the browser has been cleaned on closing it.
Once you have closed CCleaner again then Smart Cleaning will be running again.
You can check if this is what is happening for you fairly simply:
Check 1:
Look in the System Tray (the right hand end of the taskbar), don't forget to click on the 'up-arrow' as well.
If there is not a CCleaner icon showing then Smart Cleaning is not running for you, (although it may have run once and then closed).
ie. In this screenshot there no CCleaner icon in the Tray so Smart Cleaner is not running, you can restart it by simply opening/closing CCleaner and the icon will then come back.
![image.png]()
For contrast here is one where Smart Cleaning is running:
![image.png]()
Check 2:
If the ccleaner icon is there for you then open Edge Chrome, browse a couple of pages and close it again to get the Smart Cleaning notification, wait a minute
THEN check the system tray again to see if Smart Cleaning has closed itself after cleaning and the icon removed - if it has then you are being affected by this bug.
Why this is only being reported by some users, and just what is causing it, is under investigation.
It seems to have started with Windows 2004, although has also been reported with 1909.
It also seems to be tied into the Windows Task Scheduler, the affected users most probably have some different setting in Windows 2004/20H2 than others do - it's tracking down what particular setting(s) this may be that takes time.