crizal

@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.

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

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 ……….

@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.

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

@nukecad --Thanks for checking. I'm also using a local account and only a few of the store apps that came with Win 10 and they are working properly. So far, the only common denominator I can even remotely suspect has nothing to do with store apps -- Intel Rapid Storage Technology. My computer came with it but when I did the clean install to 1909, it was removed by Windows. And, one of the people I know who got the problem today still has RST in program files but Device Manager is now showing Windows is using the Microsoft driver (it's under Storage Controllers) and not Intel's. This is certainly elusive.

@Andavari -- HP uses customized drivers and the support page for my unit is grossly outdated. In fact, the latest integrated graphics driver HP shows is 2 years old and the driver for my dedicated graphics card has never been updated by HP and it's 4 years old. Can't get the customized drivers from Intel or AMD but when I did the clean install to 1909, Windows Update put in the last Intel drivers available before they started with the DCH graphics drivers. As a matter of fact, the Runtimebroker error deals with Microsoft Store apps and they are working and updating properly. The wording on the errors is so ambiguous I'm starting to think troubleshooting is not worth the time and effort. Since everything's working, just ignore it and see what the next Feature Update does.

This is really getting strange. Some people have it, others don't. Doesn't matter what brand computer or configuration. Thanks for checking. I will press on with my investigation.

It's back! "Runtimebroker.exe has stopped working" error reappeared in Reliability History as of this morning -- exact same issue I reported a few weeks back. Only this time, four other people I know who are on Win10 1909 also started getting it this morning as well. What's bizarre is everyone's computer is working fine. Programs and apps open and work properly and there's no problem restarting -- but everything done sets the error. Obviously something changed in Windows behind-the-scenes for some people and the fix that worked for me earlier no longer resolves it. Anyone running Win10 1909 -- please check Reliability History and see if you're getting the error as of today. If your computer's been off for any length of time, it might have to run for a bit to see if this eventually catches you.

Good point. Regardless of Google's decision, I know a lot of people who are not happy about Cloud Print's pending demise.

The apps are kind of iffy. Some people have good luck with them -- others can't get them to work -- even if they're using one of the newer Chromebooks. And, I believe, there are some very new CBs that will work directly with a wireless printer if connected to the same network. My main computer is Windows but I do have a CB for quick access if away and I don't bother with printing anything from that unit. CBs are limiting but if it's all you need, they suffice.

I love how the article says users will have to find an alternative. Not too many of those if all you have is a Chromebook.

As the following article explains, Google Cloud Print will be history the end of next year. https://9to5google.com/2019/11/21/google-cloud-print-dead-2020/

@hazelnut, @nukecad, @Andavari -- problem officially solved. Final solution was to clean install 1909, uninstall the Intel Graphics Command Center and then reinstall it. I don't really need it but it's there and working if I do Yes, an early holiday present! Thanks again to all for your valuable insight.

Many thanks to @hazelnut, @nukecad and @Andavari for a lot of good ideas, suggestions and information. I may have stumbled on something which I'm testing out now. Doing the upgrade from 1903 to 1909 via Windows Update yet again, I took a very close look at the error in Reliability History. As we know, it says "Runtime Broker has stopped working". Delving into the details, it mentions that the faulting module is something called settingsenvironment.desktop.dll. Runtime Broker is most often associated with apps and by the name of the faulting module, I immediately started thinking graphics -- can't explain why but I did. My computer has been updated from the Intel legacy graphics driver to the new DCH driver. Installation of the DCH driver also installs the new Intel Graphics Command Center app from the MS Store. That also uninstalled the old Intel Graphics Control Center which doesn't work with DCH. On a hunch, I uninstalled the Command Center. So far, no errors. Could simply be that app and I have read in the past that some people have been having issues with it. If this holds up for a few days, that's the answer. I won't miss the Command Center as there's nothing in there I need. I'll be posting back later in the week and hopefully this detective game will have been solved.

Very good point. If I decide to try another clean install of 1909, I'll make sure other partitions are deleted. I may just take a break from this for a few days to clear the cobwebs. Thanks for your suggestions.

There's a forum that specifically deals with Windows 10 which I also post on. Don't know if I can mention it here. The possible release of 20H1 to OEM's in December to coincide with Azure releases has been mentioned. Not known is whether it'll be released to the general public at the same time changing the release schedule or if we, the user, will still get updates in the Spring and Fall. Another possibility mentioned on several forums is that there will only be one large Feature Update each year, with a minor upgrade like 1909 six months later. Guess we all will find out soon enough.

I agree with you entirely. I believe @hazelnut is on the right track -- some type of configuration issue. Finding it is another matter. No doubt there will be some cumulative updates coming for 1909 and 1903 gets the same ones. I could easily test them out by going from 1903 to 1909 via Windows Update and quickly get back to 1903 by uninstalling the Enablement Package if 1909 is still problematic.

Yes -- just the Runtime Broker stopped working error. Not to confuse the issue, I have backup images (Macrium Reflect) for 1809 and 1903. I used the 1903 image to get that back on my machine. And even earlier, I put 1809 in and updated to 1909 using the Windows Update Assistant. No solution found yet. 1903 is working just fine.

@hazelnut -- I do not have any other machines. AV is Windows Defender. @nukecad -- Yes, 1909 is a 1903 fixer and you are right, the Reliability History errors aren't stopping the computer from working. It's really an annoyance at this point. The registry tweak to stop Runtime Broker was done and reversed back when I was on 1909. That was for high CPU and memory usage which has never been my issue. MS was grasping at straws. I'm back on 1903 and no errors.

@hazelnut -- Tried with tips and background apps turned off. I have MS and local accounts, tried them. Even tried a new user. With past upgrades, there were Runtime Broker errors but they dealt with RB causing high CPU and memory usage and the workaround was a registry tweak to turn off RB. I tried that -- no joy. I also had Cortana disabled and enabled that to see if it made a difference -- nope. And yes, I did a clean install and the issue persists. I have a backed-up image of 1903 so I reverted back. I'm really out of ideas at this point.

Win10 1909 does not like my computer which has the latest drivers and isn't even 4 years old. I updated 1903 to 1909 via Windows Update and while the computer works just fine, every single thing I do sets an error in Reliability History -- "Runtime Broker has stopped working". Happens when I turn the machine on, restart or when I open any browser, app or program. I uninstalled the Enablement Package to revert back to 1903 and the errors are gone. I've posted about this on several forums as well as Microsoft's Feedback Hub. No one can explain it or even come up with a guess as to why it's happening. I did chat with Microsoft and they advised me to stay on 1903 until 2003 comes out. And, if 2003 has the same issue, I should revert back to 1903 until it's no longer supported and then consider getting a new computer. Not what I wanted to hear. What's frustrating is that the computer works great. I'm still doing research on this issue but it's so obscure I don't think there'll be an easy fix.

Thank you very much for the information. Good to know.

It is my understanding -- and apologies if I'm wrong -- that the version of Edge which can be currently installed on Windows 7 is the Beta version of Chromium-based Edge which is still under development. As such, existing versions of CCleaner will not work with it. However, Piriform is working on a Beta version of CCleaner to remedy that. Please see the following thread ... https://forum.piriform.com/topic/54563-ccleaner-beta-edge-chromium-v561006/ Eventually, regular releases of CCleaner will work with the new browser. Again, apologies if I'm wrong. Perhaps someone from Piriform will stop by and offer additional comments.

As of this writing, my neighbor and I have had 5.58 installed for 18 hours. So far, so good. I will report back if there are any issues.