I hear your frustrations - the crux of my question, are you still running 240 TH1 or 1511 TH2? The issues you are experiencing sound like the bugs in TH1, and were remediated in TH2.Yes, as I said in my post I performed multiple resets, and would run update multiple times after the reset. The first update would install the major windows updates, and the subsequent ones would appear to be installing a series of smaller updates. This series of smaller updates would pop up again after each restart, appear to install, but continually reappear, thus apparently never getting installed. Now I had a problem on my desktop with a VC++ run-time update that would not reinstall, and found the KB that addressed this and fixed it.
The larger point of my post, and particularly as a former QA Manager and Program Manager AT Microsoft, is that here I was with a brand new device that I purchased at 3 in the afternoon. At 11:30 that night I was still up mucking with it just to get two frigging built in Apps to work.
I also understand the steps that Aldec mentioned in his post, having gone through them on my desktop to get (almost) everything working right on Win10. I also understand the importance of updating, particularly since I myself participated in working on and shipping many many patches and hot-fixes for various Microsoft products. Additionally, since updates are so important, why o why doesn't the SP4 Pro immediately force you into an update cycle when a new unit is started up?
I completely get that I could have installed Chrome, added Gmail there, and never experienced a problem. At least not until I needed to update an App through the App store. I don't have an answer as to why these problems manifested themselves on my unit, and that others claim to have one that works perfect with no glitches right out of the box. Peruse YouTube and you will see lots of issues with both Surface Pro and Book.
The whole point of my post is that I expected more out of Microsoft, particularly on a flagship product. We are just about 6 months post release and these types of problems should not be happening at this point. As I said, I will probably wait another two or three months for the problems to get ironed out and try again, and physically go into a Microsoft Store and make them find one with the latest manufacturing date possible.