Page 1 of 2 12 LastLast
Results 1 to 15 of 28
  1. #1
    5 Star Lounger
    Join Date
    Jan 2011
    Location
    Seattle, WA
    Posts
    1,070
    Thanks
    42
    Thanked 132 Times in 86 Posts

    MS sends out a silent update to Windows Update




    PATCH WATCH


    MS sends out a silent update to Windows Update


    By Susan Bradley

    It should come as a pleasant surprise that you're unlikely to find any new patches this week in Windows Update.
    However, Windows Update is itself getting a silent update. Here are a few tips to ensure no hiccups during the process.

    The full text of this column is posted at windowssecrets.com/patch-watch/ms-sends-out-a-silent-update-to-windows-update/ (opens in a new window/tab).

    Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.
    Last edited by Tracey Capen; 2012-06-27 at 19:53.

  2. #2
    Super Moderator
    Join Date
    Jun 2011
    Location
    New England
    Posts
    4,756
    Thanks
    171
    Thanked 653 Times in 576 Posts
    Quote Originally Posted by Susan Bradley View Post
    Recently, the U.S. Federal Trade Commission announced a complaint against the Wyndham hotel chain, accusing it of failing to protect guests using its Wi-Fi network.
    The FTC complaint against Wyndham Hotels is about security of account information on corporate networks and has nothing to do with protecting guests' Wi-Fi.

    Bruce

  3. #3
    New Lounger
    Join Date
    Dec 2009
    Location
    Southern Minnesota, USA
    Posts
    19
    Thanks
    4
    Thanked 4 Times in 3 Posts
    Just yesterday, we found a new problem with our WSUS server: two newly imaged Windows 7 client machines could not get updates from our WSUS server, but can get updates from Microsoft Update. On the one client where I saw the problem, it displayed an error code of 0x800B0001; running the Windows Update Reset FixIt made no difference on the client machine. Other existing Windows machines can check for updates against this WSUS server with no problems.

    When I checked our WSUS server, I found no obvious problems, and no hint of this silent update. Until I ran Windows Update on the WSUS server itself and saw this message:

    Install new Windows Update software
    To check for updates, you must first install an update for Windows Update. Your automatic updating settings will not change.

    To install the update, Windows Update will automatically close and re-open.
    Install now

    I've asked the WSUS server administrator to allow that to install and reboot the server, to see if it fixes the problem.

    I sure wish Microsoft would give us a lot more details on this. That single KB article doesn't explain much. Sande

  4. #4
    2 Star Lounger
    Join Date
    Dec 2009
    Location
    Dallas, Texas, USA
    Posts
    113
    Thanks
    3
    Thanked 6 Times in 6 Posts
    No Joy on Windows XP, SP 3

    As soon as I skimmed the table of contents, I jumped right to Susan's article about the "silent" Windows Update, hoping to find information to help resolve it. Since I had just installed ESET, immediately before I first noticed the problem, while attempting to use Windows Update to download and install the latest update for Microsoft Security Essentials, I immediately uninstalled ESET altogether, and restarted.

    Other than eliminating a DEP warning, this had no effect. I would fullow the prompts to update the engine, but I always wound up with a stalled instance of Internet Explorer 8. After I read the article, I followed the link to MSKB article 949104. As indicated, a FixIt popped up. However, my next attempt at Windows Update froze the entire computer, possibly because I didn't close the web browser.

    Following a hard reset (power off), I made another attempt, which yielded a message box captioned "IEXPLORE.EXE - Application Error," containing the following message: The instruction at "0x05e90068" referenced memory at "0x05e90068". The memory could not be "written". I'll be visiting the ISC blog next.

    The Plot Thickens

    A careful comparison of the chart in article 949104 reveals that every file on my machine is up to date. File versions, sizes, and modification dates agree 100%.

    Alas, the article says nothing about registry keys affected by the update.
    Last edited by TXWizard; 2012-06-28 at 17:02. Reason: Additional Information
    David Gray, Chief Wizard
    WizardWrx
    Irving, Texas, USA

    WizardWrx Web - Technical Articles and Free Software
    You are more important than any technology we may employ.

  5. The Following User Says Thank You to TXWizard For This Useful Post:

    czl (2012-06-30)

  6. #5
    New Lounger
    Join Date
    Apr 2011
    Posts
    8
    Thanks
    4
    Thanked 0 Times in 0 Posts

    The silent update

    I checked for the update using the method you outlined. There is no trace of WU client version 7.6.7600.256. There is however a different
    version: WU client version 7.5.7601.17514
    This begs the question: has the update not occured, or is the version on my machine the bogus client?

  7. #6
    2 Star Lounger
    Join Date
    Dec 2009
    Location
    Dallas, Texas, USA
    Posts
    113
    Thanks
    3
    Thanked 6 Times in 6 Posts
    That's a good question. According to the historical information in the article, the immediately previous version was 7.4.7600.226. Further, every version mentioned in the hostory ias a 3 digit revision number, rather than the five digit number (17514) that you mentioned.
    David Gray, Chief Wizard
    WizardWrx
    Irving, Texas, USA

    WizardWrx Web - Technical Articles and Free Software
    You are more important than any technology we may employ.

  8. #7
    New Lounger
    Join Date
    Apr 2011
    Posts
    8
    Thanks
    4
    Thanked 0 Times in 0 Posts

    Silent Update - bogus clien

    Hello TEXWizard. Thank you for your input.
    Well, it isn't a typo, I copy/paste'd it straight from the log. So I am making the assumption that it is bogus. If so, that would imply that any updates I am getting are also bogus. Incidentally when I went to look at the article, the "Fix it" window popped up. Did you also experience this, or is that part of the charade? I don't know how to fix this, as there is no freestanding KB to manually install the patch, nor any means to remove the old one.

  9. #8
    2 Star Lounger
    Join Date
    Dec 2009
    Location
    Dallas, Texas, USA
    Posts
    113
    Thanks
    3
    Thanked 6 Times in 6 Posts
    According to Susan's article, the "fixit" is supposed to pop up, as it did in my case, although this is the first time that I've had one do that. Anyway, it's possible that the historical information in the article is incomplete. Also, I found another "fixit" KB article yesterday, also related to WU, that popped open the wizard on its own. The absence of manual instructions bothers me, too. If a solution isn't forthcoming soon, I'm going to see whether I can pull the fixit apart; I found what appears to be its code in my %SystemRoot%\Temp directory, and it's a series of PowerShell scripts. (It's easy enough for Microsoft to discover for themselves that PowerShell is installed on my machine.)

    Meanwhile, it appears that my MSE installation may also be broken; I couldn't update the signatures this morning.
    David Gray, Chief Wizard
    WizardWrx
    Irving, Texas, USA

    WizardWrx Web - Technical Articles and Free Software
    You are more important than any technology we may employ.

  10. #9
    New Lounger
    Join Date
    Apr 2011
    Posts
    8
    Thanks
    4
    Thanked 0 Times in 0 Posts
    The MSE update failure happened to me from time to time, but usually it completes if I try again later. By the way this morning's update
    was created at 4:04AM, Version 1.129.718.0 Of course if it is being updated by a rogue location, that is also of dubious value. Clicking on the Fix-It pop-up in the MS article resulted in a download that fixed nothing. The article itself does not deal with any cures to the problem itself, only the patch fixes. I complained about it on their feedback form, but without much hope.

  11. #10
    New Lounger
    Join Date
    Dec 2009
    Location
    Southern Minnesota, USA
    Posts
    19
    Thanks
    4
    Thanked 4 Times in 3 Posts

    Re: error 0x800B0001

    For any of you who read my posting above, here's an update:

    On our WSUS server, installing the offered Windows Update update, then restart, did not fix the problems.

    And now we've found another way to trigger the problem on a client machine that is currently working correctly with our WSUS server: go to Microsoft Update and check for updates, When it tells you it has an update for Windows Update, accept it. Now this client will get the same 0x800B0001 error from our WSUS server, but can still get updates from Microsoft Update.

    I've opened an incident with Microsoft on this. We'll see what they have to say. Sande

  12. The Following User Says Thank You to snissen0 For This Useful Post:

    TXWizard (2012-06-29)

  13. #11
    2 Star Lounger
    Join Date
    Dec 2009
    Location
    Dallas, Texas, USA
    Posts
    113
    Thanks
    3
    Thanked 6 Times in 6 Posts
    MSE Update

    Before replying to your message, I made another attempt to update, and succeeded. MSE reports my version number as 1.129.718.0 (same as yours), and says that it was created at 06/29/2012 @ 06:04 (+2:00 from the time you cited). However, if these times are adjusted from a UTC base, as is almost certainly the case, and you are in the Pacific Daylight time zone, my time would be later than yours by two hours.

    Do-Nothing FixIt

    Your experience mirrors mine almost exactly.

    The absence of detail in the article is unusual, unless this reflects a recent change. Until recently, when I've visited a page that had a FixIt link, the article also contained manual instructions to do the same things that the FixIt did, along with instructions for rolling back the change.

    IMO, barring the need for an out of cycle update, Microsoft has until 10 July 2012 to fix this. That should be plenty of time.
    David Gray, Chief Wizard
    WizardWrx
    Irving, Texas, USA

    WizardWrx Web - Technical Articles and Free Software
    You are more important than any technology we may employ.

  14. The Following User Says Thank You to TXWizard For This Useful Post:

    czl (2012-06-30)

  15. #12
    Lounger
    Join Date
    Apr 2011
    Posts
    41
    Thanks
    2
    Thanked 3 Times in 3 Posts
    A couple of questions re the .NET Framework updates for my XP home-user system:

    1. Is it really necessary to update my video driver (NVIDIA GeForce 5200) before installing the .NET updates OK'd in this Patch Watch? I haven't had any problem with the previous .NET updates that Susan has cleared to install.

    2. Are KB 2604092, KB 2604010, and KB 2604111 OK to install? They are 05/08, MS12-035 updates. They were offerred at the same time and were discussed and put on wait in the same Patch Watch column item as KB 2656407 (MS12-034) that the current Patch Chart has as now OK to install.

    3. What about the .NET updates from MS11-100, offerred in December 2011? These are old skips that were dropped from the Patch Chart. I have three of these still being offered in my MS Updates: KB's 2656352, 2656353, and 2657424. They are updates to .NET 1.1 SP 1, .NET 2.0 SP 2, and .NET 3.5 SP 1, respectively.

    Thanks for any guidance on these items.
    MarciaG

  16. #13
    Lounger
    Join Date
    Apr 2011
    Posts
    41
    Thanks
    2
    Thanked 3 Times in 3 Posts
    Can I install KB 2686509, if my XP was not an upgrade from Windows 98 or ME?
    Thanks,
    MarciaG

  17. #14
    2 Star Lounger
    Join Date
    Dec 2009
    Location
    Dallas, Texas, USA
    Posts
    113
    Thanks
    3
    Thanked 6 Times in 6 Posts
    Marcia,

    I think what Susan intended to suggest is that you may need to update the video drivers if they are very old and you are having problems with .NET Framework updates.

    Several years ago, up to about the time that version 4.0 shipped, I had some difficulties with .NET updates on Windows XP. Since then, they have all slid right into place. I'd say make an extra restore point, mark it "before updates," and proceed.
    David Gray, Chief Wizard
    WizardWrx
    Irving, Texas, USA

    WizardWrx Web - Technical Articles and Free Software
    You are more important than any technology we may employ.

  18. #15
    Super Moderator
    Join Date
    Jun 2011
    Location
    New England
    Posts
    4,756
    Thanks
    171
    Thanked 653 Times in 576 Posts
    Quote Originally Posted by czl View Post
    The silent update

    I checked for the update using the method you outlined. There is no trace of WU client version 7.6.7600.256. There is however a different
    version: WU client version 7.5.7601.17514
    This begs the question: has the update not occured, or is the version on my machine the bogus client?
    Quote Originally Posted by czl View Post
    Silent Update - bogus client

    Well, it isn't a typo, I copy/paste'd it straight from the log. So I am making the assumption that it is bogus. If so, that would imply that any updates I am getting are also bogus.
    That version number is genuine but at least a year old. I don't think you're getting bogus updates, which is an extremely theoretical possibility (just a mechanism used by Flamer to spread; I don't believe there's any evidence that any bogus windows updates have actually been received by anyone). You just don't appear to have got the new version yet.

    Bruce
    Last edited by BruceR; 2012-06-29 at 22:08.

  19. The Following User Says Thank You to BruceR For This Useful Post:

    czl (2012-06-30)

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •