Soozy

The issue happened immediately after the 5.37 CCleaner update the other day.

I am very well aware what Insider testing is about and using Insider builds. My point was to make CCleaner aware that there is an issue SINCE Avast took over Piriform. If a software company is not interested in input about their product, that's fine. As stated I and others had no issues with a GSOD until the newest CCleaner update. And other software developers ARE interested in issues that arise with their programs and Windows 10 builds. These developers willingly work with MS to clear up a problem or find the cause.

That's fine, I don't have a problem with that. I have used CC have 3 years while testing Insider builds and never had an issue until Avast took over. I just felt that the Avast people should be made aware of the issue as Microsoft was made aware.

Sorry, but as a Windows 10 Insider I don't want to take the chance of this happening with every new build we get (once a week). I'm not the only Windows Insider seeing this. Several posted to the Windows 10 Feedback and not just involving CCleaner. I believe the Avast AV is also causing an issue. Thank you for trying to help.

I have used CCleaner for years and NEVER had an issue with Windows 10 and CCleaner until Avast took over. Today for the 1st time in ages, I had a GSOD and had to rollback my Win 10 build. This happened immediately after getting the latest CCleaner update this AM. So I guess CCleaner is going bye bye for me after all these years.