Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Craig Matthews Craig_​Matthews Good News, Everyone!
  • Windows 8 is finally paying off for Microsoft!

    Is this going to be on "Signature" PCs?  Just sayin'.

     

  • Stop the madness mark 2.

    , bondsbw wrote

    @magicalclick:  No, I meant what you said by "never increment the number", which means it is the last version of Windows.  I'm thinking (just my guess) that they won't even release a 10.1, 10.2, and so on... if they do, I'll be very disappointed by the blatant copying of Apple.

    LOL. that was pretty much the correct way to version things way before OSX came out. Instead of stupid things like going from  8.1 to 8.1 Update 1.  Should have been 8.2.

     

  • Stop the madness mark 2.

    , figuerres wrote

    I wonder about this fear of updates and why updates go wrong....

    I know that for corporate networks and a small number of others there is a core need to control updates, ok they need that.

    But for the vast numbers of average users updates should be automatic. In every case that I know of the update failures are a result of something wrong with the pc that needs to be fixed, if Wu is looping, crashing, hanging etch... that means that you need to have an it pro fix something or reload the o's in the extreme case. It may be a sign of a Trojan, a corrupted filesystem or possibly a pending hardware failure. Fix the darn pc and get it updated!

    Instead of telling users to fear updates tell them to have the pc backed up and checked for malware on a regular basis.

    Ok sometimes a Wu problem can happen but I would bet that is the 1% of all the updates overall, not the common case.

    A pc is a machine with many parts, if you do not keep it up it will have failures and that is not Microsoft's fault.

    While I agree with the general sense that updates, for non-enterprise/pro SKUs, should be automatic, I have to ask where you've been with regard to update issues? Failed updates, update loops, boot loops after updates, etc. - caused by the update itself -- happen quite often to mass numbers of people at the same time. 

    The reason I believe updates should be completely automatic for non-pro/non-enterprise SKUs is mainly because:

    • It holds Microsoft's feet to the fire and forces them to make sure their QA is better with regard to update publishing. If updates are forced and suddenly no one can get their Netflix anymore, people will get upset at Microsoft and force them to do better, and maybe those same customers will think a little bit more about the fact that they let an entire industry get away with selling defective products with no recourse.
    • It prevents tech support people from using "you don't have all the latest updates" as an excuse to get off the phone because they're either lazy, unqualified, or -- usually, both. People can just tell that support guy, "sorry, bud, all the updates got forced to my computer. I *can't* be out of date. You're gonna have to actually think, buddy."

     

     

  • Stop the madness!

    , NoelCarboni wrote

    • The ability to choose when to apply updates - something important to those who run mission critical systems, as the installation process for updates, even if they subsequently work properly, can be disruptive.  At this point, it IS possible to achieve this through a Local Group Policy change (I have done it).  But I'm not convinced this won't change in a future build.  Without this key element, Windows 10 will be useless for any critical usage (thinking, for example, about that recent ball game that was delayed because the scoreboard computer chose to update itself).

    I don't see any evidence where this is changing in any way. As far as I know, SCCM Configuration Manager isn't going away, which is what enterprise environments use for patch management. Patch control is foundational to the enterprise ecosystem and a key component of Microsoft's enterprise management package. Removing the ability to control updates via group policy in Enterprise and Pro SKUs is simply not a valid hypothetical. That's just not going to happen. Additionally, there's Windows Intune for small situations, and now Windows Update for Business.

    There are too many integration scenarios where it's a non-starter to even think about automatic, uncontrollable updates. The fact is -- if the scoreboard at a sporting event or a mission critical database server reboots in the middle of the day for updates, the responsible IT organization simply isn't doing their job -- either by using the wrong SKU or not configuring updates properly. 

    And I really wish people would stop referring to Group Policy, either explicitly or implicitly, as some sort of hack, backdoor, or kludge. Group Policy is an entire subsystem of Windows who's purpose for existence is to control these types of things in an enterprise environment, and has been for over 15 years. It's the system administrator's enterprise control panel, not a hack.

    If the IT people in an enterprise environment consisting of mission critical Windows systems doesn't know how to control updates, doesn't know how to configure maintenance windows, or doesn't know how to QA patching with the tools that Microsoft has provided -- which they are not taking away -- those IT people really need to be replaced. 

     

  • Another day, another locked thread

    If he opened another thread, he would have been called a troll, the thread locked, and people would be bitching about endless threads about the same topic. He isn't the one that hijacked this thread. And for the record, this reply I'm typing is on topic.

  • Does Windows 10 fix the console and powershell?

    ConEmu pretty much blows away the console host in every version of Windows. Highly recommended.

     

  • Android Apps to run on Windows Phone

    Is this thing about Windows Phone running Android apps really true? I'm seriously running out of reasons to get a Windows phone when it comes time for replacement. First, they ripped out the hubs (pretty much the distinguishing feature). Then my bank pulls their app completely and their mobile site still doesn't work.

    As far as I can tell, sitting on the outside as a non developer and just a user of this platform, if I had to guess -- it appears that Microsoft must be making app developers slice their wrist and spill blood into a cup and pledge their soul to the service of Lucifer to get on the Windows Store with the way app developers appear to be avoiding the platform like the plague. What the hell is the problem?

    It's great that Office and OneDrive is available for all the big platforms now, but given that, plus everything I said above, the question becomes: other than this great camera, why do I have a Lumia 1520?

    In just one year, this phone went from the best smartphone I've ever owned to being a good camera. If I had to pick right now, I'd probably get an Android. Making my phone able to run Android apps instead of fixing this app store situation will probably seal the deal. If devs aren't making apps for Windows phone now, why the hell would they start now that it runs Android apps?

     

  • the next 5 years is crucial to MS.

    I read this all the time -- not just here --- can someone explain to me how a company can be "done for" or  "failing", or the like, because they don't produce a product that they haven't produced before?

    I'm no economist -- so I don't understand this at all. Why does Microsoft have to make a watch? Why does Microsoft have to get into wearables? Why does Microsoft have to produce a good [insert random product type here] or else they will fail?

    Ford has been producing cars for a century and they've never, to my knowledge, manufactured a television. They're still in business.

     

  • These Windows 10 ​adware/prel​oader patches are packaged with important security updates. JUST WTF?!

    What's the deal with that Aero-translucent title bar in Chrome and the Windows Vista taskbar in that screenshot of Windows 8?

     

  • These Windows 10 ​adware/prel​oader patches are packaged with important security updates. JUST WTF?!

    , wastingtime​withforums wrote

    Uh, it's not.

    gpedit.msc is even more a hack than regedit for most people. Most users heard about the registry, but group policy is something almost no average user comes ever in contact with. Not even "enthusiasts" touch it, because the settings there are pretty much useless for a non-domained PC.

    Hiding the option there (instead of a tickbox in the nag-screen) is... hiding.

    First thing -- regardless of who launches gpedit.msc, there is no way it's any more of a "hack" than regedit, simply because gpedit specifically is a configuration GUI which takes configuration settings set by user and applies them to the relevant registry entries. The only difference between it and a control panel applet is that it runs in an MMC window.

    GPEDIT is also pretty much the "advanced mode" that techies started screaming they wanted once they perceived that Windows was being "dumbed" down and it's been there in some form or another since Windows for Workgroups -- "enthusiasts" touch it all the time (even the ones that shouldn't), and most of the settings in there have nothing to do with whether a machine is on a domain or not. 

    Yes, they should have put a checkbox that says "stop bugging me about this." I read you loud and clear there and agree with you 100%. But, no offense to anyone on this forum, we're dealing with a company where Hanlon's Razor should be the very first plausible explanation for anything -- not nefarious imagined threats of an upgrade.