Jump to content
CCleaner Community Forums

JMR

Experienced Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JMR

  • Rank
    Member
  1. Months later, version 5.40 still doesn't work.
  2. Okay, thanks. Obviously a terrible design by Microsoft.
  3. Well, I just replicated it on the Piriform forum. All I did was close the IE browser, go into CCleaner and right-click the "Saved Passwords" option under "Microsoft Edge" and selected "Clean Saved Passwords".
  4. It turns-out that the "Saved Passwords" option under "Microsoft Edge" is wiping-out the usernames/password in Internet Explorer. This is obviously not supposed to be happening.
  5. In Internet Explorer 11 under Windows 10 (and possibly other versions of Windows), CCleaner v.5.30.6065 removes SOME usernames and passwords... even though the "Autocomplete Form History" and "Saved Passwords" options are NOT selected under the "Internet Explorer" section. In addition, the websites in question are listed in the "Cookies to Keep" section in Options/Cookies.
  6. I'm just wondering why there has been no one at Piriform is addressing this issue. Seems odd there is no official response after nearly two months. Even a simplistic response such as "we are looking into this" or "this change is by design" would be helpful. Let's be clear about this issue. Using the Menu Order Cache option of CCleaner now removes any custom ordering of the IE Favorites Bar. This has not always been the case. This is undesirable as there is now no way to reorder the Start Menu without also alphabetizing the IE Favorites Bar.
  7. No, it has NOT always done this. As I mentioned, I already disabled that checkbox as a temporary workaround, but that is not a solution.
  8. Internet Explorer 11 running on Windows 7 Professional SP1.
  9. CCleaner v5.29 now removes custom ordering of the IE Favorites Bar with the use of the Menu Order Cache option, which is undesired. It is now unchecked, but this alphabetization result for the IE Favorites Bar did not occur in the most recently installed previous versions.
  10. v5.26 does not exhibit this issue... rolled it back and works fine. IMHO it makes no sense to roll-out v5.28 without addressing a show-stopper.
×
×
  • Create New...