"Just run dism and sfc /scannow. It will surely fix your problem. Kindly mark my response as the answer."
"Hi, I'm Greg and I've been a Microsoft MVP for 10 years. I'm happy to help you out."
<insert robotic answer that totally does not answer the question at all>
I think it shouldn't be done for dev tools of course, because devs are the ones that need to see the errors.
I have a broken installer. I get some random error. Googling suggests I need to reinstall the software... whose installer I am trying to debug. Gee whiz never could have thought of that!
The ones where you search how to resize an image, and the very helpful guide on coolmagictech.com tells you somewhere around the 2nd step to download and run the CoolMagic® MagicResizer™ tool?
I haven’t seen one of those in like 5 years… But then again, I also haven’t used nor troubleshot Windows in those 5 years. Might be a correlation there?
Time was at a premium and the one option seemed to be one of those sketchy Windows app at an equally sketchy website where you could buy the software via cc. I explained the risks to my friend who decided to give it a shot (on a clean Windows install which was later wiped, of course).
It worked, just as advertised. We got all the data in a usable enough format. Surprisingly enough.
Recently I have this issue with my energy supplier, every time I try to change tariff in the app(like they tell you to) I just get "uh oh something went wrong". Like......that's condescending to the maximum.