They need a GUI way to fix things whenever something doesn't work.
No they don't. They just want a GUI way to fix things as they don't understand/consider other ways of interfacing with a computer. I'm always reminded of Scotty in Star Trek IV when he asks to borrow the computer to give the formula for transparent alumin[i]um when I hear this argument - his usual method of interface is spoken words, and when the computer doesn't respond Dr McCoy gives him the mouse for which his first instinct is that it is a microphone. [He's then offered the keyboard, says "How quaint" and then proceeds to use it faster than most people these days.] Scotty didn't give up in a huff because the computer didn't understand his spoken commands, he adapted to the situation.
If you have an automatic car (GUI) and someone tell you to put it into first (CLI manual car solution which is available in all automatic vehicles I've driven) to start off up a steep hill do you go off in a huff and moan that you've got an automatic (GUI) not a manual (CLI) and not bother trying the solution? Similarly going down a steep hill when being told to put it into a low gear (CLI solution) to provide engine braking when you've got an automatic car (GUI, but still has the ability for user gear selection)?
Read: CLI solutions are not quicker nor simpler, unless you already know how!
Exactly the same argument holds for GUI solutions - GUI solutions are not quicker or simpler, unless you already know how.
I'm much balder due to trying to find a GUI solution to problems I could solve with a CLI solution much quicker and simpler.
Why the difference? Simple: I took to computing then the GUI was not much more than an experiment at Xerox and so learnt the use of a keyboard instead of a mouse; when I have to deal with a GUI interface, I struggle going through menus/options to find what I want much more than finding the correct command in a CLI interface
Neither is whipping up a vim or an emacs session to edit some file in /etc/ anybody's idea of fun
Neither is whipping up a registry editor to edit the binary blob of the registry anybody's idea of fun.
It's interesting to consider that Windows 3 used INI files which were text files that cold be edited using a straight forward text editor. The result was that if the configuration was messed up, you could boot a CLI (oh, no, not that idea), either DOS or any other OS that could read the partition, run any old text editor and have a fairly good go at fixing the configuration.
Then came along Win 95 (and repeated with all windows versions) with its registry (a binary blob of a database that held all configurations) that now needs a special program to be able to edit it - GUI based. Which meant if that configuration in the registry is messed up so that the GUI can't run, you couldn't run the registry editor to fix the configuration. Really clever. Solution: take a copy of the registry, but on restoration, it'll destroy all the configuration changes for all programs made since the copy was made; solution: backup regularly and hope main configuration doesn't get messed up...