If your Windows system breaks, and that means anything beyond "oh I'm missing a driver", you have no recourse, you have to reformat. You end up googling and doing the exact same procedures you would under Linux, except because the OS internals are obscured and proprietary, you don't have whole stack detailed analysis on whatever problem you have, you have a black box and you have to hope the tools MS gives you are good enough.
It doesn't change that for 99% of users, regardless of OS, when you encounter a problem you don't try to fix it yourself. Most people aren't going to even try, they are either going to take the system to an expert who would use a terminal no problem or just get another one.
I think the primary difference with Linux is that developers are fairly content mucking about with things, so breakage that would be a showstopper for someone who is not intimately familiar with computers goes somewhat unnoticed. It's hard to step back and say "what would I do if I didn't know about <x,y,z>?" in daily life.
The point is, yeah, you shouldn't have to go to a terminal, but that requires the development of guis to overlay the complexity. I use my relatives as test beds for whatever breaks that requires a "control panel entry" to fix.
- Windows XP - Power went out at a critical stage of updates. Completely hosed the system, and wasted hours of my life having to rebuild (including rebooting multiple times to get updates installed again after the recovery).
- Windows 7 - Cable giving my router IP addresses. Called ISP tech support... they had me manually plug the cable in and type cryptic commands at a DOS prompt. Is that unacceptible too?
Also, I'm really baffled as to how the network going down could kill a Fedora update. The downloads happen before any significant filesystem modification in every version that I have ever used (certainly any recent one). I guess maybe some third party package does something weird during a POSTINSTALL script? I dunno.