Jump to content
CCleaner Community Forums

Recommended Posts

There is a bug in the current CCleaner version:

A DetectOS according to the scheme "DetectOS=from|to" (e.g. "DetectOS=6.2|6.3") does not work anymore and CCleaner therefore sorts out the entry.

The other combinations with a pipe symbol still seem to work (e.g. "DetectOS=|10.0" or "DetectOS=10.0|").

The bug was found by @dvdbane and reported here:
https://community.ccleaner.com/topic/32310-winapp2ini-additions/page/331/?tab=comments#comment-318930

Link to post
Share on other sites

I had a little more time to check the bug and have to correct parts of my previous post. (I use Windows 10 for my following examples.)

The following DetectOS strings no longer work:

DetectOS=|10.0 (= for Windows 10 and older)
DetectOS=10.0|10.0 (= only for Windows 10)

The problem seems to be that the version number after the pipe symbol now also needs the build number, because the following strings work:

DetectOS=|10.0.18363.778
DetectOS=10.0|10.0.18363.778

Please make sure that CCleaner, if no build number is included in the string, behaves like the previous versions and accepts a simple "|10.0" again. Thanks!

@hazelnut: Thanks for the flagging.

Link to post
Share on other sites

Just a reminder: the bug is not yet fixed in version 5.66.7716. Probably the bug report came too short before the release of the current version.

Link to post
Share on other sites
  • 4 weeks later...

Still not fixed in version 5.67.7763! Very disappointing! 👎

You have broken a function that has worked for years, please fix it as soon as possible.

Link to post
Share on other sites
  • 4 weeks later...
  • Admin

@APMichael: FYI, this has been in the development backlog for a couple of months, so it has been on the devs' radar. It was mentioned in passing in a meeting I was at earlier this week that it's now actively under investigation in the current development sprint, so depending on whatever code complexities and inter-dependencies may be involved that probably means that it will bubble out at some point over the next couple of releases.

Link to post
Share on other sites
  • 4 weeks later...

@Dave CCleaner: Thanks for the information. Unfortunately the bug is not completely fixed!

The following DetectOS string is now working again: DetectOS=10.0|10.0 (= only for Windows 10)

But this DetectOS string is now completely broken: DetectOS=|10.0 (= for Windows 10 and older)
Because now it does not even work with an attached build number: DetectOS=|10.0.18363.959 (= for Windows 10.0.18363.959 and older)

Link to post
Share on other sites
  • Moderators
45 minutes ago, APMichael said:

@Dave CCleaner: Thanks for the information. Unfortunately the bug is not completely fixed!

The following DetectOS string is now working again: DetectOS=10.0|10.0 (= only for Windows 10)

But this DetectOS string is now completely broken: DetectOS=|10.0 (= for Windows 10 and older)
Because now it does not even work with an attached build number: DetectOS=|10.0.18363.959 (= for Windows 10.0.18363.959 and older)

 

Good find !!!

Link to post
Share on other sites
  • 3 weeks later...
On 07/08/2020 at 04:12, Dave CCleaner said:

Hoping for good news from @dvdbane - we're all on a bit of a bug-busting crusade at the moment. 

sorry for late reply

Working as usual, great job 👍

Hopefully it won't happen in the future as it can goes unnoticed unless you're making and testing winapp2.ini entries

 

Untitled.png

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...