Material design is not at all flat, not even slightly. It repudiates both skeumorphism and flat design.

The mobile-UI that they force you into using in so many places in Windows X is terrible. Not to mention that it feels like you get ‘less’ options/information per screen than what you had in the good old Windows UI.

Flat and Material design are both founded on solid colors and simple geometric shapes. Yes, Google has generated voluminous documentation on Z layers and animations and calls to action and bla bla bla, but to the casual observer the actual difference between the two is hair-splitting at best. Oooh, drop shadows, totally different.

Claiming that Material is “not even slightly” like flat design just makes you sound like a crazy person. Pretty much every article on the subject acknowledges the deep similarities between the two.

The difference between a flat UI and one with drop shadows and Z depth is enormous. One is flat, the other isn’t.

I have to say that Android is pretty flat too.

Yep, I found Material design to be a major step backward from where they were before because it felt too flat. I mean, I appreciate that they took measures to keep it from going too far down that hole. . . but not nearly far enough in my book.

The default button style in Material is literally called ‘flat’. It looks like text until you mouse over it.
https://material-components-web.appspot.com/button.html

You’re wrong on this one stusser. Material is very very flat design style.

When you press it, it highlights. When you move elements around, they have Z-depth, they exist against a reference point. OBVIOUSLY material is pretty flat, but it has tons of UI hints so people don’t get confused. That’s where iOS7 really failed.

Remember back when flat was popular, people were talking about completely repudiating skeumorphism, completely clean digital interfaces, no transparencies, no depth, solid colors, no gradients, tons of white space and zero ornamentation. IOS7 was the embodiment of that, and it was really confusing to use for many people.

Windows 10 has been popping up a message for about a month asking me if I wanted to update now, tonight, or tomorrow. I kept saying tomorrow.

One day I wasn’t at the computer, apparently, and it started updating. Took a long time, then I get an error box with a red x saying it couldn’t install certain (something.) It tried to restore the previous version. Had a problem with that. After two or three reboots, I fortunately got my old version restored.

I’ve tried to avoid the update since then, but last night it did it on it’s own again, and I got the same problem.

I don’t think I can avoid the update, but has anyone seen this problem and know a fix?

Thanks

They opened the floodgates on the Creator’s Update this week.

Need more details on what’s causing your error, but for now
https://support.microsoft.com/en-us/help/10587/windows-10-get-help-with-upgrade-installation-errors

That helps - I think I was running thin on HD space on my C: drive (less than the 20G it says is required.) I’ll free it up and see if that helps. Thanks

I just wrestled with issues from the update this past week, as well. My system health apparently wasn’t top notch at the time of update, and I wound up having to do a bunch of little annoying things (including a Windows Update repair and one long-ass chkdsk /f /r - apparently a couple thousand descriptors and what not were dangling out these) until everything was peachy, again.

I thought everyone loved the Forced updates on Win10?

The Forced Update Awakens!

Linked my Windows 10 system to my MS account. Replaced hardware. Use the Activation troubleshooter to try and re-activate. It says there are no valid devices to activate. Logging into my MS account shows the old system (with motherboard details) and new system (without details).

Anyone seen this and know a fix short of actually having to call MS?

Did you replace the motherboard too? That could be an issue.

Agreed. About a year ago (so things may have changed) I was looking at doing some hardware changes, and I asked MS what their policy was. Basically, as long as I kept the motherboard I was good.

I did replace the motherboard, but that is why I specifically linked the system to my MS account. You do that to allow you to reactivate via their troubleshooter tool automatically. See https://support.microsoft.com/en-us/help/20530/windows-10-reactivating-after-hardware-change

Yeah, I see what you mean. Nice they expanded that bit, but it sounds like talking to MS is unfortunately the way to go.

tl;dr version: For some reason Windows Update just threw the Fall Creator’s Update my way again on my Win 10 Pro.

So, 3 or 4 days ago I got this “There’s an important update, you need to restart” prompt (or whatever it says). I picked “Remind me” later, but despite several manual restarts since then, nothing actually got installed. (Despite the Win Update icon being displayed on the Restart/Shutdown buttons.) After getting the prompt for a third or fourth time, I checked the Windows Update menu today, and sure enough it had the “Feature update to Windows 10, version 1709”. Choosing the restart option in the Windows Update menu did the trick and it installed the Fall Creator’s Update. After installing the Fall Creator’s Update, Win Update also listed the Metldown/Spectre patch (after manual search).

Thing is … I definitely had the Fall Creator’s Update installed months ago when it rolled out, and I had installed the Meltdown/Spectre update (KB4056892) the day it became available. I didn’t not do any system restore, and there were no weird system events (unexpected crashed etc.) that might have triggered Win going back to an earlier restore point. The Geforce Drivers I had installed a few days ago were still up-to-date.

Usually I’d shrug this off and go “Eh.”, but I’m really not fond of the idea that I may have been running an unpatched system for a few days due to whatever Win 10 glitch caused this. Any pointers?