Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About crizal

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Florida, U.S.A.

Recent Profile Visitors

569 profile views
  1. @nukecad -- kind of figured that.
  2. Microsoft's new Edge Chromium is officially out. Current CCleaner 5.63.7540 ignores it as expected but it can be cleaned from within the browser. Time for a new version of CCleaner.
  3. I reported CCleaner's problems with Edge pre-loading in October 2018 and a fix was supposed to come in the next release. That never happened. https://forum.piriform.com/topic/52706-547-partially-brokenwin-10-1809/
  4. I don't do anything in the registry unless I'm really sure of what needs to be done. The HKeys shown above need to be created and I haven't bothered with the pre-loading issue at all. We'll see how the new Edge will work out in a couple of weeks. Another thought -- with Windows 10 changing as frequently as it does between feature and cumulative updates, there are times when previous registry tweaks no longer work.
  5. No matter where you are, a happy and safe holiday season to all.
  6. crizal

    Windows 10 1909

    It wouldn't surprise me. Some of the feature as well as cumulative updates change user settings and MS likes their stuff as the default. Luckily, we're still able to change things to our liking -- for now. An entire other story if that ever changes.
  7. crizal

    Windows 10 1909

    Hi @hazelnut -- the link in your post above pretty much echoes what was posted on TenForums today. In the following thread, I posted a question to @Stephen CCleaner regarding the Edge pre-loading registry fix (for the current browser) as to whether it'll be needed in the new chromium Edge. Link is in this thread: https://forum.piriform.com/topic/56335-solution-ccleaner-cannot-fully-clean-microsoft-edge-due-to-pre-loading/?tab=comments#comment-313516 BTW -- runtime error is gone and has not returned, so long as 'category' view is not used for Control Panel. Let's hope MS doesn't mess the new Edge install or the next feature update.
  8. Hello @Stephen CCleaner -- quick question. According to this thread from TenForums, the final, stable channel public release for the new chrome Edge will be out on or shortly after January 15th. If the registry fix described above is implemented for the existing Edge, will it need to be changed for the new Edge? Microsoft plans on hiding the old Edge very deeply in the system. https://www.tenforums.com/windows-10-news/146645-microsoft-details-migration-plan-new-microsoft-edge-windows-10-a.html Thanks for any information.
  9. crizal

    Windows 10 1909

    After every Win 10 reinstall or repair install, Control Panel was always in category view by default on my system and I never gave it a second thought. At least now that the cause and workarounds are known, hopefully others who have this issue can solve it easily. Happy holidays to all and Santa is in icon view.
  10. crizal

    Windows 10 1909

    Now this is really embarrassingly simple -- especially after troubleshooting for three weeks. The entire issue, at least on my machine, was caused by Control Panel being in category view. @Andavari you gave me an idea. All I had to do was change the CP view from category to either small or large icons. Don't even need to pin anything to start menu. Just go to CP in the usual way through search and be greeted by icon view and not category view -- no errors. For me, finally, case closed!
  11. crizal

    Windows 10 1909

    @hazelnut, @Andavari, @nukecad, @Nergal -- informative update regarding the Runtime error. It's hitting a small number of machines on Win 10 1909. The cause has something to do with 1909, Control Panel and Cortana. It's actually the Control Panel setting the error when Reliability History is checked. The error also appears if you go to a different category in the CP. There are two workarounds. The first has a 100% success rate -- the second may or may not work. 1. Go to Control Panel and change the view from category to icons. Right click the icon topics you want to open and pin each one to the start menu. Close Control Panel. Run CCleaner to remove the errors from Reliability History. Open the appropriate icon from the start menu. It will directly go to that section in Control Panel and no errors will be generated. To properly check Reliability History, the Security and Maintenance icon must be pinned to the start menu and opened from there. 2. At least one user found a solution by uninstalling, reinstalling and re-registering Cortana using Powershell. That may be beyond the ability of a typical user. The following link from TenForums explains it all and it's good reading. If this link is against this forum's policy, I apologize and please remove it. https://www.tenforums.com/general-support/145996-runtime-errors.html Next up is to get Microsoft involved.
  12. crizal

    Windows 10 1909

    @nukecad -- 2003 aka 20H1 aka the next Feature Update. I do like your angle better.
  13. crizal

    Windows 10 1909

    Sure have. There've been a few suggestions and ideas but nothing that's worked. Seems to be a very obscure issue. Including myself, I know of only five people experiencing this and I did report it to MS on the Feedback Hub -- no responses. MS support has been pretty lame on many levels. BTW -- computer will be 4 years old in March. Came with Win 10 1511 and has never had any major issue through 1903 which worked flawlessly. 1909 is essentially 1903 on steroids -- they both get the same updates. That's the puzzle -- what changed in 1909 to trigger this error ……….
  14. crizal

    Windows 10 1909

    @Andavari, @nukecad -- Sorry for delayed response. I just finished doing another experiment. I did another clean install of Win 10 1909 (getting very good at this) and something did change very recently and it could've been something Microsoft did (perhaps getting ready for 2003?) ….. 1. The first update to 1909 was from 1903 via Windows Update. Everything worked for 4 days, then the Runtime error started. 2. Did clean install of 1909. Runtime error started exactly 2 weeks later. 3. Just completed another clean install of 1909 and Runtime error started immediately. There is obviously something in 1909 that doesn't like my computer or it could be something in my computer doesn't agree with 1909. Why there was a delay in it showing up and now it's immediate tells me something is different "under the hood". I'm going to let it go and see if Cumulative Updates remedy the situation, or, wait for 2003 to come out. In any event, computer's working fine so while there's a mystery -- it's not hurting anything.
  15. crizal

    Windows 10 1909

    This is precisely what makes this issue so frustrating -- is it really a problem when everything works? I suppose time will tell.
  • Create New...