New set of 9 Microsoft Updates Crash Windows 7 64 Bit Desktop

Page 2 of 2 FirstFirst 12

  1. Posts : 2,171
    Windows 7 Ultimate x64
       #11

    CO Senior said:
    So, basically, we can't update Win 7 64 in the manner normally presented by Windows Update (letting Windows Update run and just hitting the install button to install Critical and Important Updates), but must override the automatic selection and choose to install Updates one at a time? That's fine, but Microsoft should (a) design the Windows Updates application to work that way, and (b) if Microsoft can't manage to do that, at least warn users to ignore the default and install updates one at a time. I've just wasted over 6 hours trying to get to the bottom of "failed" updates.
    It is designed to work that way, although not the default. I always set it for manual installs on my main machines. Even during all of the XP years. If you keep up with what's going on with security issues I think it's perfectly fine to do the updates yourself. Every once in a while there will be an update that causes some sort of problem. But update problems go back to early XP days, too. An update might break some feature that you use with a particular app, or it might have caused a problem with the OS itself that wasn't forseen, etc. There've even been updates that MS has pulled from distribution right after pushing them out. I think the problem is much more rare than it used to be (even throughout the years of XP). I have never used auto updates because of the potential, but rare, problems. I just keep up as best I can with the security world and update when I'm good and ready (when I know there are no mass reported issues). I'm not the typical update guinea pig. There's really no real reason for me to be that way anymore though. Since around 2005, I've been making images at least once a month, and always between the first of the month and patch Tuesday, so it really would be easy enough just to roll it back.

    That said, when I repair other folks' machines I usually set it to full auto. That's because it's much easier to correct any rare issue resulting from updates rather than fixing a machine that's been totally crippled because it hasn't been updated in the last year.
    CO Senior said:
    Additionally, applications keep closing with pop-ups to the effect that "Microsoft needs more information to try to solve X problems", followed by assorted variations on "Microsoft can not solve X because of Y".
    If you get that a lot you've got some kind of conflict occuring, an install problem, something's going on. But, I think you're right, it's not yet a very well refined all-around "troubleshooter". When it does have a legitimate answer it always seems to be something that would've been easy to find anyway just by doing a little poking around the system yourself.
    CO Senior said:
    I've used XP Pro, which was stable and allowed me to customize much of it to fit the way in which I use my computers, since it first came out. XP Pro was a stable and fairly easily customizable OS. Win 7 pro seems to be unduly rigid and not at all flexible to meet individual users needs/preferences. This does not make sense to me. It feels like 20 steps backwards to ME land (which appeared to have grown out of the incompetent 95 & 98 chain of OS’, rather than out of the NT chain).
    Stick with w7 for a while. I think after a while you may find that it's much more stable, secure and customizable than XP. I think I can agree on WinME being considered a disaster, but I've always thought the 95/98 versions were revolutionary, considering how bad I thought 3.1 was. I think developers had a rough time developing to the new standards imposed by 95. But it seemed to me to be just as revolutionary as the ME to XP leap. I had such a good time with 95/98, that if XP hadn't been built on the NT model, I probably would've held on to the 95/98 machines much longer than I did. I used NT4 client and server at home on a few machines for a number of years, and used them at work. And while I loved it, I think MS had a lot of work to do before introducing NT into the consumer world.
    CO Senior said:
    Sorry to go on, but I'm very disappointed with Win 7. After Win 7 turned out to be such a mess, I bought XP Pro 64 bit to install on my new x64 build in lieu of Win 7, but am reticent to install it because I understand support for XP Pro is being phased out in less than 2 years.
    Is there realistic hope that Win 7 will be brought up to the stability, functionality and customizability levels of XP Pro? Or, should I just install the 64 bit XP Pro for now and hope whatever Microsoft comes out with next (after Win 8, which I understand is an even greater disaster than Win 7) will actually be a workable OS? Or, should I just give up on Microsoft and learn all about Linux and/or Ubuntu?
    Well, most of the Linux flavors are free to try (I think most are). But I don't consider w7 a disaster at all, quite the opposite actually. I'd stick with it for awhile (of course I've no idea how long you've already stuck with it). And even though XP will be updated until April 2014, you've got to think about how patched up it is. It'll never be as secure as w7.

    Also realize that because of security issues that MS, as well as many other software firms, are trying to push more and more towards auto updates. If I remember correctly w8 was originally going to be designed as auto only. Don't know if it made that way by the time of the preview; I haven't tried it yet but I think it's now an option.
    Last edited by F5ing; 10 May 2012 at 23:50.
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #12

    sparkyuiop said:
    I'm not going to ask Microsoft; the company that keeps trying to update my Nvidia video card with their naff modified version of the latest Nvidia........
    MS do not write drivers. Drivers on WU are upplied by the manifacturer concerned, and may be cut-down versions.

    If you are getting a driver from WU, then it must be because there's an element of the installed drivers that's older than the one available at WU (which is usually at least one version behind that available at the manufacturer's site).
    I'd check out your nVidia suite and see what's there that's causing it.
      My Computer


  3. Posts : 2
    Windows 7 Pro 64 bit
       #13

    Win 7 "Troubleshooter"


    Quote: Originally Posted by sibble
    If you get that a lot you've got some kind of conflict occuring, an install problem, something's going on. But, I think you're right, it's not yet a very well refined all-around "troubleshooter". When it does have a legitimate answer it always seems to be something that would've been easy to find anyway just by doing a little poking around the system yourself.

    {sorry for the incorrect quotation style - for some reason I can't get it to work this morning....}
    Is there a way to turn the troubleshooter off? I'm used to doing my own trouble shooting and the info provided in the application is not useful, so the troubleshooter's more of a distraction than anything else.

    I'm with you on NT 4.0 - used NT 4.0 Server for quite a while, with both NT based 2000 Pro and NT based XP Pro, as those OS came on line. I've always had more faith in an OS which comes out of the NT line.

    Thank you for all of your time, thought and expertise in responding to my many questions and issues. I'll take your advice and persevere with win 7 Pro a bit longer.
      My Computer


  4. Posts : 2,171
    Windows 7 Ultimate x64
       #14

    CO Senior said:
    Is there a way to turn the troubleshooter off? I'm used to doing my own trouble shooting and the info provided in the application is not useful, so the troubleshooter's more of a distraction than anything else.
    I really don't know. I so rarely see it that I've not been bothered by it. It's probably been two or three months since it last popped up. On top of that, I never thought to disable it as I'd like to see if its performance improves over time to determine if I can ever truly recommend it as a worthwhile tool for the typical user.

    There was a two week or so period of time where I was getting it quite often. It was always with the 32bit version of either IE8 or IE9 (can't remember which), but oddly enough, only when I was viewing a list of search results from MS's own Bing. And almost never occuring on the first search, it was typically when I would navigate forward or back to the webpage that contained an existing Bing search listing, or after attempting a new Bing search on top of the last search. Never happened with other search engines.

    So obviously I was getting it often enough to be able to recognize exactly how it was occuring, but it was really the problem itself that was bothering me, rather than the troubleshooter never knowing how to fix it. But in the end I never figured out what the true cause was either; the issue had just gone away. I know there were IE updates applied, but I really couldn't say for sure that updates solved the problem. For all I know it could've been that IE was simply having problems rendering faulty Bing pages that were subsequently fixed.

    I'll look around to see if there's a way to turn off the troubleshooter and post here if I find it. In the meantime I'm sure others will see this thread too, and if there is a way to do it, I'm pretty sure you'll see a post soon with the answer.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:03.
Find Us