1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Automatic updates will not install

Discussion in 'Windows XP' started by Smckinn, 2008/03/08.

  1. 2008/03/08
    Smckinn

    Smckinn Inactive Thread Starter

    Joined:
    2008/03/08
    Messages:
    9
    Likes Received:
    0
    Hello. I am having the same problems installing updates. I have tried several of your intrsuctions here and it temporarily will fix the problem. The update the comes right back because my system will not let it install. I ran the insatll log for KB927779, that is the update I am stuck on. I am attaching it because there are errors all through it. can someone look at this and try and give me an idea of what I need to do?



    [KB927779.log]
    0.891: ================================================================================
    0.891: 2007/10/29 18:34:11.953 (local)
    0.891: C:\WINDOWS\SoftwareDistribution\Download\6b5f9b6e24a379bdb34ad3589556de3e\update\update.exe (version 6.2.29.0)
    0.891: Hotfix started with following command line: /si /ParentInfo:93f08dae10a5f04fa102a752539a7715
    1.141: DoInstallation: CleanPFR failed: 0x2
    1.141: SetProductTypes: InfProductBuildType=BuildType.IC
    1.141: SetAltOsLoaderPath: No section uses DirId 65701; done.
    1.172: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB927779$
    1.188: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
    1.219: ref tag c:\windows\system32\sp4.cab does not exist
    1.219: ref tag c:\windows\system32\sp3.cab does not exist
    1.219: ref tag c:\windows\system32\sp2.cab does not exist
    1.219: ref tag c:\windows\system32\sp1.cab does not exist
    1.219: ref tag c:\windows\system32\driver.cab does not exist
    1.219: ref tag c:\windows\system32\fp40ext.cab does not exist
    1.219: ref tag c:\windows\system32\fp40ext1.cab does not exist
    1.219: ref tag c:\windows\system32\wms4.cab does not exist
    1.219: ref tag c:\windows\system32\wms41.cab does not exist
    1.219: ref tag c:\windows\system32\ims.cab does not exist
    1.219: ref tag c:\windows\system32\ims1.cab does not exist
    1.219: ref tag c:\windows\system32\ins.cab does not exist
    1.235: ref tag c:\windows\system32\ins1.cab does not exist
    1.235: Starting AnalyzeComponents
    1.235: AnalyzePhaseZero used 0 ticks
    1.235: No c:\windows\INF\updtblk.inf file.
    1.235: OEM file scan used 0 ticks
    1.500: AnalyzePhaseOne: used 265 ticks
    1.500: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    1.500: AnalyzeComponents: Hotpatching is disabled.
    1.500: FindFirstFile c:\windows\$hf_mig$\*.*
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.500: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.516: KB927779 Setup encountered an error: The update.ver file is not correct.
    1.594: AnalyzeForBranching used 78 ticks.
    1.610: AnalyzePhaseTwo used 16 ticks
    1.610: AnalyzePhaseThree used 0 ticks
    1.625: AnalyzePhaseFive used 15 ticks
    1.625: AnalyzePhaseSix used 0 ticks
    1.625: AnalyzeComponents used 390 ticks
    1.625: Downloading 8 files
    1.625: bPatchMode = TRUE
    1.625: Inventory complete: ReturnStatus=0, 453 ticks
    1.625: Num Ticks for invent : 453
    1.656: [dumpDownloadTask] Update.exe posting request file to download a total of 456516 bytes (95818 bytes in patches and 360698 bytes in fallbacks)
    1.656: dumpDownloadTask returned 0xf200 (more files to download)
    1.735: KB927779 installation did not complete.
    1.735: Update.exe extended error code = 0xf200
    0.844: ================================================================================
    0.844: 2007/10/29 18:44:18.500 (local)
    0.844: C:\WINDOWS\SoftwareDistribution\Download\6b5f9b6e24a379bdb34ad3589556de3e\update\update.exe (version 6.2.29.0)
    0.844: Hotfix started with following command line: /si /ParentInfo:c4402ca53b076f4abaca48496f76f7fa
    1.078: DoInstallation: CleanPFR failed: 0x2
    1.078: SetProductTypes: InfProductBuildType=BuildType.IC
    1.078: SetAltOsLoaderPath: No section uses DirId 65701; done.
    1.125: Express: 456,516 bytes were downloaded.
    1.266: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
    1.312: KB927779 installation did not complete.
    1.312: Update.exe extended error code = 0xf201
    1.250: ================================================================================
     
    Smckinn,
    #1
  2. 2008/03/10
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Hi, Welcome to WindowsBBS.

    Try this:

    1. Open a command prompt: go to Start > Run and type cmd in the Open box, click OK
    2. Stop Automatic Update Service; type Net stop wuauserv (press Enter) .
    3. Type rd /S %Windir%\SoftwareDistribution. This will delete the %Windir%\SoftwareDistribution folder. Type Y to confirm.
    4. Type Net start wuauserv (hit Enter) to start the Automatic Update Service. Close the command prompt.
    5. Force a Windows Update detection and see if that works.
     
    Arie,
    #2


  3. to hide this advert.

  4. 2008/03/10
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Also:

    You may want to start a free Windows Update support incident
    request: https://support.microsoft.com/oas/default.aspx?gprid=6527


    =============================
    Support for Windows Update:
    http://support.microsoft.com/gp/wusupport

    For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and in Canada or by contacting your local Microsoft subsidiary. There is no-charge for support calls that are associated with security updates. When you call, clearly state that your problem is related to a Security Update and cite the update's KB number (e.g., KB123456).

    For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the International Support Web site: http://support.microsoft.com/common/international.aspx

    For enterprise customers, support for security updates is available through your usual support contacts.
     
    Arie,
    #3
  5. 2008/03/10
    Robin20152

    Robin20152 Inactive

    Joined:
    2008/03/07
    Messages:
    19
    Likes Received:
    0
    What is "Force a Windows Update detection "

    Hi, Smckinn !

    I hope you're having better luck solving your "Updates" problem than I've had in solving mine!!!

    GOOD LUCK !!!

    Hi, Arie !

    I hope you don't mind my asking, but what does it mean to "Force a Windows Update detection" ???

    I haven't run across that term before.

    Thanx !

    ROBIN
    Eugene, Oregon USA
     
    Robin20152,
    #4
  6. 2008/03/10
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Start > Microsoft/Windows Update
     
    PeteC,
    #5
  7. 2008/03/10
    Robin20152

    Robin20152 Inactive

    Joined:
    2008/03/07
    Messages:
    19
    Likes Received:
    0
    Oh! OK! Live & Learn....

    Hi, Pete !

    Oh !

    Okay !

    The only time I've run across the use of the word "force" was the advice somebody gave about installing WinXP SP3/RC2. The advice was, if you were having trouble installing SP3/RC2, to add the term "\wuforce" to a Run command.

    Well, Live & Learn, I guess... :eek:

    ROBIN
    Eugene, Oregon USA
     
    Robin20152,
    #6
  8. 2008/03/10
    Smckinn

    Smckinn Inactive Thread Starter

    Joined:
    2008/03/08
    Messages:
    9
    Likes Received:
    0
    Still won' install

    Good morning. Arie, I have followed your instructions earlier and it seemed to work for a little while until programming caused my system to enter the automatic updates rourine again. The only way I have found to stop it is to follow your directions and then turn automatic updates off. I have ran a forced update and windows tells me I need the same update but it will not install on my machine.

    Hi Robin
    This is driving me nuts!!

    Steve , Indianapolis Indiana USA
     
    Smckinn,
    #7
  9. 2008/03/10
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well, I'd take MS up on their offer of free support for Windows Updates. Mention your trouble installing KB927779, and they should help you out.

    Then come back & let us know.

    I would tell you if I knew the fix for that update, but I don't.
     
    Arie,
    #8

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...