First of all, best of luck - I do remember missing a *lot* of 2001-2009 with our 3 kids up until the youngest was 2ish.

When they are 3 and on it's a complete joy ride - lots of run watching them discover the world.

Then they become teenagers.

I now know why hard liquor was invented.

Yes, *I* use DSC quite a bit. In fact, pretty much daily. But as upi state - *** For my server builds. ***

This broke Windows 10 version 1607. I run it at home, and at work on a couple of test desktops, but i know of no instances of 1607 under our SCCM - for that matter, we only have about a 5% deploy of Windows 10.

So yes, this slipped through, but I think the actual exposure will be quite small. Lots of crowds and torches on slashdot, but this is probably a very small blip.

  In fact, by virtue of how Fast Track gets deployed I don't think I'd ever see this issue -

    Win10 install from SCCM or ISO
    Apply DSC config as part of the build or part of a configuration script
    manually enable fast track
    wait for MS to update the box to fast track
    get the new build
    finally get the bad patch

If I were MS, I'd look at creating a better patch/update exposure matrix - the Fast Track for Insider Updates includes all sorts of telemetry, and I would imagine that they could look at a patch and compare the functionality to the actual use telemetry - "This patch updates DSC. DSC has been used by 1% of all fast track users over the past 10 days. Risk of patch++"

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"SeparateProcess"=dword:00000001

FTW

Completely agree - the Ecobee is everything the Nest claims to be and better.

Wow - a thoughtful and logical comment on why Windows 10 is actually interesting.

My biggest addition to this is the boot time - Win10 boots in under 5 seconds on my SSD laptop, compared with 15-20 on my desktop with a high end Seagate hybrid 7200 (I know, bad purchase. If I could have waited another year...) My desktop boots up with a couple of active HyperV instances (Plex Server, Ubuntu, FreeBSD), so its not really usable for an other couple of minutes, but that's my own issue.

The Windows 10 interface is an interesting combination of the old and new - all your programs are immediately available like 7, but you have the live tile pane for all the new "chatty" applications - weather, news, recipes, Facebook, etc. all with their own ADHD inspired "Hey! Click me!" look. I'm running insider/fast on one of my boxes and the interface changes that are coming for the summer release are quite good. I've got tile sections for Office, Development, Admin tools and other crap - which is sort of back to the old Program Manager Groups from Win3.1 :-)

Updates, well, its windows so it will do that. I've only had issues when I clicked the "do it now" button, then realized my wife was watching something off the Plex server.

Other than a couple of minor issues, it just works.

Yes, but if the lawyers tell Intel that it's employees cannot contribute to the Kernel *as a work requirement* anymore, what does that do to the Kernel?

So I'm waiting for someone at a major corporation that does substantial open source development to file a hostile work environment suit against their company if they are required to do kernel submissions. That would *quickly* result in a change in attitude if a major contributor decided that it was potentially litigiously expensive to contribute.

And I'm talking Intel, IBM, RedHat, or even Google, all with massive presence in the US, where this type of behavior would be considered completely unacceptable.

I'm sorry, this is like working for a vulgar cousin or uncle. Fine for small business and family shops, completely unacceptable outside of that type of environment.

My understanding is that MS is working to integrate powershell based package manager tools like https://chocolatey.org/ with Powershell 5.0.

"could be" is a way for lawyers to charge more hours.