Re: It's the usual story.
A neighbour has a PC with a forced update to Win10. Networking was dead. Stone dead, so she called me - the "Mac guy" for help. It was trivial to plug in MacBook Pro and verify that the network was indeed alive and well. A bit of work with Mr Google released that many others were in the same sorry state because of the borked fix a month or so ago. No help from Redmond, of course.
But some suggested that reacquiring a DHCP lease might be a help but - of course - there's no way I could find to do that within any of the Control Panels. I did try for a while - total zero. Then I remembered that the command-line might help (last time I used that on Windows is longer than I care to remember) and BINGO - networking was networking again. Fortunately Redmond figured out its fiasco and applied Band-Aid#2 so I haven't been called back on this.
Then she mentioned that none of her printers had been working since the unwanted, forced update. It turns out that all the Win7 print drivers are c**p for Win10 so you have to funky-fiddle the de-install of the old ones and then manually install new ones from the vendor.
Funny, but my Apple MBP had no problem finding the printer and printing to it - although it had never seen that variety before.
So, the "usual story" is that Apple mostly gets its stuff to work, straightforward, right out of the box. If you others want to buy other stuff and then complain that *that* doesn't work - that's your problem. I choose not to spend my life doing that.