KB920685 won't install

Discussion in 'Windows Small Business Server' started by Robert, Sep 17, 2006.

  1. Robert

    Robert Guest

    Update KB920685 keeps failing. Other than the error code below, windows
    update tells me nothing. I have no idea how to troubleshoot this to get it
    installed. Any ideas? It's on SBS2003 (without SP1).

    Error Code: 0x8007F01E

    Thanks,
    Robert
     
    Robert, Sep 17, 2006
    #1
    1. Advertisements

  2. Find the log file ...and can you post it here?
     
    Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP], Sep 17, 2006
    #2
    1. Advertisements

  3. Robert

    Robert Guest

    Where is the log file located?

     
    Robert, Sep 18, 2006
    #3
  4. Usually under the c:\windows folder but you can do a start, find 920685.log
     
    Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP], Sep 18, 2006
    #4
  5. Robert

    Robert Guest

    It's been a while, but just getting back to this issue.

    The log file has many attempts in it so I am only taking the latest install
    attempt. Here it is:

    0.579: 2006/10/02 19:42:12.495 (local)
    0.579:
    C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\ab07915f1729fc2141dbaf4814eb9323\update\update.exe (version 6.2.29.0)
    0.579: Hotfix started with following command line: /si
    /ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    8.110: ---- Old Information In The Registry ------
    8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    8.110: Destination:
    8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    8.110: Destination:
    8.110: ---- New Information In The Registry ------
    8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    8.110: Destination:
    8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    8.110: Destination:
    8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    8.125: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB920685$
    8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
    0xe0000102
    8.141: ref tag c:\windows\system32\sp4.cab does not exist
    8.141: ref tag c:\windows\system32\sp3.cab does not exist
    8.141: ref tag c:\windows\system32\sp2.cab does not exist
    8.141: ref tag c:\windows\system32\sp1.cab does not exist
    8.141: ref tag c:\windows\system32\driver.cab does not exist
    8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    8.157: ref tag c:\windows\system32\wms4.cab does not exist
    8.157: ref tag c:\windows\system32\wms41.cab does not exist
    8.157: ref tag c:\windows\system32\ims.cab does not exist
    8.157: ref tag c:\windows\system32\ims1.cab does not exist
    8.157: ref tag c:\windows\system32\ins.cab does not exist
    8.157: ref tag c:\windows\system32\ins1.cab does not exist
    8.157: Starting AnalyzeComponents
    8.157: AnalyzePhaseZero used 0 ticks
    8.157: No c:\windows\INF\updtblk.inf file.
    8.157: OEM file scan used 0 ticks
    8.157: AnalyzePhaseOne: used 0 ticks
    8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    8.157: AnalyzeComponents: Hotpatching is disabled.
    8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    8.157: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.157: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.157: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.157: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.157: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.172: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.172: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.172: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.172: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.172: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.188: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.204: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.204: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.204: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.204: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.219: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.219: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.297: KB920685 Setup encountered an error: The update.ver file is not
    correct.
    8.360: AnalyzeForBranching used 31 ticks.
    8.360: AnalyzePhaseTwo used 0 ticks
    8.360: AnalyzePhaseThree used 0 ticks
    8.360: AnalyzePhaseFive used 0 ticks
    8.360: AnalyzePhaseSix used 0 ticks
    8.360: AnalyzeComponents used 203 ticks
    8.360: Downloading 0 files
    8.360: bPatchMode = TRUE
    8.360: Inventory complete: ReturnStatus=0, 235 ticks
    8.360: Num Ticks for invent : 235
    8.360: [dumpDownloadTask] We have all necessary files for the package to
    install. Return STATUS_READY_TO_INSTALL
    8.360: dumpDownloadTask returned 0xf201 (ready to install)
    9.516: KB920685 installation did not complete.
    9.516: Update.exe extended error code = 0xf201
     
    Robert, Oct 3, 2006
    #5
  6. Hi Robert,

    Thanks for posting back. I appreciate your time.

    Based on my research, the issue may occur due to that the default Dcom
    permissions was modified. When the default access permissions for dcom had
    been modified to allow access for other users and services, the adding of
    these users and services consequently removes the inherent "Administrators"
    allow access permission which is there by default.

    Please try to the steps below to resolve the issue:

    1. You can bring the Dcom Default Access Permissions back to default by
    backing up following registry key:

    HKLM\SOFTWARE\Microsoft\Ole

    2. Deleting the following values if they exist (which will be present only
    if the default Dcom settings were modified.)

    DefaultAccessPermission (only present if Default Access Permissions
    were modified)
    LegacyImpersonationLevel (only present if Impersonation Level was
    modified)
    LegacyAuthenticationLevel (only present if Default Authentication Level
    was modified)

    3. Then try to apply the update again. What is the result?

    I appreciate your time.

    Have a nice day!

    Sincerely,

    Jenny Wu
    Microsoft CSS Online Newsgroup Support
    Get Secure! - www.microsoft.com/security
    ======================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    ======================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    <>
    4eb9323\update\update.exe (version 6.2.29.0)
     
    Jenny wu [MSFT], Oct 5, 2006
    #6
  7. Robert

    Robert Guest

    Just want to make sure I understand. Should I delete the key or just the data?

    FYI - HKLM\SOFTWARE\Microsoft\Ole only has the following keys:

    DefaultLaunchPermission
    DefaultDCOM
    LegacyImpersonationLevel

    Thanks,
    Robert

     
    Robert, Oct 17, 2006
    #7
  8. Robert

    Crina Li Guest

    Hi Robert,

    Thanks for your update.

    You should delete the keys Jenny has mentioned.

    Thanks for your time.

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: KB920685 won't install
    | thread-index: AcbxkuQVZcVWWV+RRWmTqeLs45ZBxg==
    | X-WBNR-Posting-Host: 24.115.210.83
    | From: =?Utf-8?B?Um9iZXJ0?= <>
    | References: <>
    <>
    <>
    <>
    <>
    <>
    | Subject: Re: KB920685 won't install
    | Date: Mon, 16 Oct 2006 19:21:02 -0700
    | Lines: 231
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGXA01.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:305493
    | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Just want to make sure I understand. Should I delete the key or just the
    data?
    |
    | FYI - HKLM\SOFTWARE\Microsoft\Ole only has the following keys:
    |
    | DefaultLaunchPermission
    | DefaultDCOM
    | LegacyImpersonationLevel
    |
    | Thanks,
    | Robert
    |
    | ""Jenny wu [MSFT]"" wrote:
    |
    | > Hi Robert,
    | >
    | > Thanks for posting back. I appreciate your time.
    | >
    | > Based on my research, the issue may occur due to that the default Dcom
    | > permissions was modified. When the default access permissions for dcom
    had
    | > been modified to allow access for other users and services, the adding
    of
    | > these users and services consequently removes the inherent
    "Administrators"
    | > allow access permission which is there by default.
    | >
    | > Please try to the steps below to resolve the issue:
    | >
    | > 1. You can bring the Dcom Default Access Permissions back to default by
    | > backing up following registry key:
    | >
    | > HKLM\SOFTWARE\Microsoft\Ole
    | >
    | > 2. Deleting the following values if they exist (which will be present
    only
    | > if the default Dcom settings were modified.)
    | >
    | > DefaultAccessPermission (only present if Default Access
    Permissions
    | > were modified)
    | > LegacyImpersonationLevel (only present if Impersonation Level was
    | > modified)
    | > LegacyAuthenticationLevel (only present if Default Authentication
    Level
    | > was modified)
    | >
    | > 3. Then try to apply the update again. What is the result?
    | >
    | > I appreciate your time.
    | >
    | > Have a nice day!
    | >
    | > Sincerely,
    | >
    | > Jenny Wu
    | > Microsoft CSS Online Newsgroup Support
    | > Get Secure! - www.microsoft.com/security
    | > ======================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > ======================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    | >
    | > --------------------
    | > >Thread-Topic: KB920685 won't install
    | > >thread-index: Acbmjzf/TGLkehn2RvaYxNCKNoYGhg==
    | > >X-WBNR-Posting-Host: 24.229.31.55
    | > >From: =?Utf-8?B?Um9iZXJ0?= <>
    | > >References: <>
    | > <>
    | > <>
    | > <>
    | > >Subject: Re: KB920685 won't install
    | > >Date: Mon, 2 Oct 2006 18:57:02 -0700
    | > >Lines: 119
    | > >Message-ID: <>
    | > >MIME-Version: 1.0
    | > >Content-Type: text/plain;
    | > > charset="Utf-8"
    | > >Content-Transfer-Encoding: 7bit
    | > >X-Newsreader: Microsoft CDO for Windows 2000
    | > >Content-Class: urn:content-classes:message
    | > >Importance: normal
    | > >Priority: normal
    | > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > >Newsgroups: microsoft.public.windows.server.sbs
    | > >Path: TK2MSFTNGXA01.phx.gbl
    | > >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:302012
    | > >NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > >X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > >
    | > >It's been a while, but just getting back to this issue.
    | > >
    | > >The log file has many attempts in it so I am only taking the latest
    | > install
    | > >attempt. Here it is:
    | > >
    | > >0.579: 2006/10/02 19:42:12.495 (local)
    | > >0.579:
    | >
    | > 4eb9323\update\update.exe (version 6.2.29.0)
    | > >0.579: Hotfix started with following command line: /si
    | > >/ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    | > >8.110: ---- Old Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.110: ---- New Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    | > >8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    | > >8.125: CreateUninstall = 1,Directory =
    C:\WINDOWS\$NtUninstallKB920685$
    | > >8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
    failed:
    | > >0xe0000102
    | > >8.141: ref tag c:\windows\system32\sp4.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp3.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp2.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp1.cab does not exist
    | > >8.141: ref tag c:\windows\system32\driver.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms4.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms41.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins1.cab does not exist
    | > >8.157: Starting AnalyzeComponents
    | > >8.157: AnalyzePhaseZero used 0 ticks
    | > >8.157: No c:\windows\INF\updtblk.inf file.
    | > >8.157: OEM file scan used 0 ticks
    | > >8.157: AnalyzePhaseOne: used 0 ticks
    | > >8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    | > >8.157: AnalyzeComponents: Hotpatching is disabled.
    | > >8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.188: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.297: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.360: AnalyzeForBranching used 31 ticks.
    | > >8.360: AnalyzePhaseTwo used 0 ticks
    | > >8.360: AnalyzePhaseThree used 0 ticks
    | > >8.360: AnalyzePhaseFive used 0 ticks
    | > >8.360: AnalyzePhaseSix used 0 ticks
    | > >8.360: AnalyzeComponents used 203 ticks
    | > >8.360: Downloading 0 files
    | > >8.360: bPatchMode = TRUE
    | > >8.360: Inventory complete: ReturnStatus=0, 235 ticks
    | > >8.360: Num Ticks for invent : 235
    | > >8.360: [dumpDownloadTask] We have all necessary files for the package
    to
    | > >install. Return STATUS_READY_TO_INSTALL
    | > >8.360: dumpDownloadTask returned 0xf201 (ready to install)
    | > >9.516: KB920685 installation did not complete.
    | > >9.516: Update.exe extended error code = 0xf201
    | > >
    | > >"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >
    | > >> Usually under the c:\windows folder but you can do a start, find
    | > 920685.log
    | > >>
    | > >> Robert wrote:
    | > >> > Where is the log file located?
    | > >> >
    | > >> > "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >> >
    | > >> >> Find the log file ...and can you post it here?
    | > >> >>
    | > >> >> Robert wrote:
    | > >> >>> Update KB920685 keeps failing. Other than the error code below,
    | > windows
    | > >> >>> update tells me nothing. I have no idea how to troubleshoot
    this to
    | > get it
    | > >> >>> installed. Any ideas? It's on SBS2003 (without SP1).
    | > >> >>>
    | > >> >>> Error Code: 0x8007F01E
    | > >> >>>
    | > >> >>> Thanks,
    | > >> >>> Robert
    | > >>
    | > >
    | >
    | >
    |
     
    Crina Li, Oct 17, 2006
    #8
  9. Robert

    Robert Guest

    OK, I only had the LegacyImpersonationLevel key present, but I deleted it,
    but my updates are still failing. I said updates, because since this issue
    started I know have a total of 5 that are failing.

    Thanks!

     
    Robert, Oct 20, 2006
    #9
  10. Robert

    Crina Li Guest

    Hi Robert,

    Thanks for your update.

    To narrow down the problem, would you please help me collect the following
    information?

    1. Can you install the update manually?
    2. Please try a clean boot to see how thing goes:

    1) Click Start, click Run, and then in the Open box, type "MSCONFIG"
    (without the quotation marks). Click OK.
    2) In the System Configuration Utility (MSConfig) window, click to select
    the Selective Startup button.
    3) Click to clear the check mark from the "Load startup items" below
    Selective Startup.
    4) Click the Services tab, click to check the "Hide All Microsoft Services"
    box, and remove all the check marks from the remained Non-Microsoft
    Services. Please note that the Exchange services could be marked as
    non-Microsoft. Please do not disable those services.
    5) Click OK to close the MSConfig window. Click Yes when you are asked to
    restart your computer in order to enable the changes.
    6) After restarting, please check whether this issue will reoccur.

    Thanks for your time and I look forward to hearing from you.

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: KB920685 won't install
    | thread-index: Acbz7bCPsGsAYbwyST+4hA9YeoPpFA==
    | X-WBNR-Posting-Host: 207.46.199.61
    | From: =?Utf-8?B?Um9iZXJ0?= <>
    | References: <>
    <>
    <>
    <>
    <>
    <>
    | Subject: Re: KB920685 won't install
    | Date: Thu, 19 Oct 2006 19:16:02 -0700
    | Lines: 226
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGXA01.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:306497
    | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | OK, I only had the LegacyImpersonationLevel key present, but I deleted
    it,
    | but my updates are still failing. I said updates, because since this
    issue
    | started I know have a total of 5 that are failing.
    |
    | Thanks!
    |
    | ""Jenny wu [MSFT]"" wrote:
    |
    | > Hi Robert,
    | >
    | > Thanks for posting back. I appreciate your time.
    | >
    | > Based on my research, the issue may occur due to that the default Dcom
    | > permissions was modified. When the default access permissions for dcom
    had
    | > been modified to allow access for other users and services, the adding
    of
    | > these users and services consequently removes the inherent
    "Administrators"
    | > allow access permission which is there by default.
    | >
    | > Please try to the steps below to resolve the issue:
    | >
    | > 1. You can bring the Dcom Default Access Permissions back to default by
    | > backing up following registry key:
    | >
    | > HKLM\SOFTWARE\Microsoft\Ole
    | >
    | > 2. Deleting the following values if they exist (which will be present
    only
    | > if the default Dcom settings were modified.)
    | >
    | > DefaultAccessPermission (only present if Default Access
    Permissions
    | > were modified)
    | > LegacyImpersonationLevel (only present if Impersonation Level was
    | > modified)
    | > LegacyAuthenticationLevel (only present if Default Authentication
    Level
    | > was modified)
    | >
    | > 3. Then try to apply the update again. What is the result?
    | >
    | > I appreciate your time.
    | >
    | > Have a nice day!
    | >
    | > Sincerely,
    | >
    | > Jenny Wu
    | > Microsoft CSS Online Newsgroup Support
    | > Get Secure! - www.microsoft.com/security
    | > ======================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > ======================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    | >
    | > --------------------
    | > >Thread-Topic: KB920685 won't install
    | > >thread-index: Acbmjzf/TGLkehn2RvaYxNCKNoYGhg==
    | > >X-WBNR-Posting-Host: 24.229.31.55
    | > >From: =?Utf-8?B?Um9iZXJ0?= <>
    | > >References: <>
    | > <>
    | > <>
    | > <>
    | > >Subject: Re: KB920685 won't install
    | > >Date: Mon, 2 Oct 2006 18:57:02 -0700
    | > >Lines: 119
    | > >Message-ID: <>
    | > >MIME-Version: 1.0
    | > >Content-Type: text/plain;
    | > > charset="Utf-8"
    | > >Content-Transfer-Encoding: 7bit
    | > >X-Newsreader: Microsoft CDO for Windows 2000
    | > >Content-Class: urn:content-classes:message
    | > >Importance: normal
    | > >Priority: normal
    | > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > >Newsgroups: microsoft.public.windows.server.sbs
    | > >Path: TK2MSFTNGXA01.phx.gbl
    | > >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:302012
    | > >NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > >X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > >
    | > >It's been a while, but just getting back to this issue.
    | > >
    | > >The log file has many attempts in it so I am only taking the latest
    | > install
    | > >attempt. Here it is:
    | > >
    | > >0.579: 2006/10/02 19:42:12.495 (local)
    | > >0.579:
    | >
    | > 4eb9323\update\update.exe (version 6.2.29.0)
    | > >0.579: Hotfix started with following command line: /si
    | > >/ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    | > >8.110: ---- Old Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.110: ---- New Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    | > >8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    | > >8.125: CreateUninstall = 1,Directory =
    C:\WINDOWS\$NtUninstallKB920685$
    | > >8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
    failed:
    | > >0xe0000102
    | > >8.141: ref tag c:\windows\system32\sp4.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp3.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp2.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp1.cab does not exist
    | > >8.141: ref tag c:\windows\system32\driver.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms4.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms41.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins1.cab does not exist
    | > >8.157: Starting AnalyzeComponents
    | > >8.157: AnalyzePhaseZero used 0 ticks
    | > >8.157: No c:\windows\INF\updtblk.inf file.
    | > >8.157: OEM file scan used 0 ticks
    | > >8.157: AnalyzePhaseOne: used 0 ticks
    | > >8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    | > >8.157: AnalyzeComponents: Hotpatching is disabled.
    | > >8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.188: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.297: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.360: AnalyzeForBranching used 31 ticks.
    | > >8.360: AnalyzePhaseTwo used 0 ticks
    | > >8.360: AnalyzePhaseThree used 0 ticks
    | > >8.360: AnalyzePhaseFive used 0 ticks
    | > >8.360: AnalyzePhaseSix used 0 ticks
    | > >8.360: AnalyzeComponents used 203 ticks
    | > >8.360: Downloading 0 files
    | > >8.360: bPatchMode = TRUE
    | > >8.360: Inventory complete: ReturnStatus=0, 235 ticks
    | > >8.360: Num Ticks for invent : 235
    | > >8.360: [dumpDownloadTask] We have all necessary files for the package
    to
    | > >install. Return STATUS_READY_TO_INSTALL
    | > >8.360: dumpDownloadTask returned 0xf201 (ready to install)
    | > >9.516: KB920685 installation did not complete.
    | > >9.516: Update.exe extended error code = 0xf201
    | > >
    | > >"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >
    | > >> Usually under the c:\windows folder but you can do a start, find
    | > 920685.log
    | > >>
    | > >> Robert wrote:
    | > >> > Where is the log file located?
    | > >> >
    | > >> > "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >> >
    | > >> >> Find the log file ...and can you post it here?
    | > >> >>
    | > >> >> Robert wrote:
    | > >> >>> Update KB920685 keeps failing. Other than the error code below,
    | > windows
    | > >> >>> update tells me nothing. I have no idea how to troubleshoot
    this to
    | > get it
    | > >> >>> installed. Any ideas? It's on SBS2003 (without SP1).
    | > >> >>>
    | > >> >>> Error Code: 0x8007F01E
    | > >> >>>
    | > >> >>> Thanks,
    | > >> >>> Robert
    | > >>
    | > >
    | >
    | >
    |
     
    Crina Li, Oct 20, 2006
    #10
  11. Robert

    Becky Guest

    Where to you find the Dcom default access permission to change the registery
    keys. I am also having problems with the kb920685



     
    Becky, Oct 21, 2006
    #11
  12. Robert

    Crina Li Guest

    Hi Becky,

    Thanks for your update.

    You can access HKLM\SOFTWARE\Microsoft\Ole from registry key and follow
    Jenny's steps to see how thing goes.

    If the issue still occurs, you may better to open a new post. Microsoft
    engineers can only focus on one issue per thread. Although we provide other
    information for your reference, we recommend you post different incidents
    in different threads to keep the thread clean. In doing so, it will ensure
    your issues are resolved in a timely manner.

    Thanks for your understanding!

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: KB920685 won't install
    | thread-index: Acb1KdNXfgPLU/Q3TuisXVzKwmvOgQ==
    | X-WBNR-Posting-Host: 69.88.199.230
    | From: =?Utf-8?B?QmVja3k=?= <>
    | References: <>
    <>
    <>
    <>
    <>
    <>
    | Subject: Re: KB920685 won't install
    | Date: Sat, 21 Oct 2006 08:59:01 -0700
    | Lines: 225
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGXA01.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:306793
    | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Where to you find the Dcom default access permission to change the
    registery
    | keys. I am also having problems with the kb920685
    |
    |
    |
    | ""Jenny wu [MSFT]"" wrote:
    |
    | > Hi Robert,
    | >
    | > Thanks for posting back. I appreciate your time.
    | >
    | > Based on my research, the issue may occur due to that the default Dcom
    | > permissions was modified. When the default access permissions for dcom
    had
    | > been modified to allow access for other users and services, the adding
    of
    | > these users and services consequently removes the inherent
    "Administrators"
    | > allow access permission which is there by default.
    | >
    | > Please try to the steps below to resolve the issue:
    | >
    | > 1. You can bring the Dcom Default Access Permissions back to default by
    | > backing up following registry key:
    | >
    | > HKLM\SOFTWARE\Microsoft\Ole
    | >
    | > 2. Deleting the following values if they exist (which will be present
    only
    | > if the default Dcom settings were modified.)
    | >
    | > DefaultAccessPermission (only present if Default Access
    Permissions
    | > were modified)
    | > LegacyImpersonationLevel (only present if Impersonation Level was
    | > modified)
    | > LegacyAuthenticationLevel (only present if Default Authentication
    Level
    | > was modified)
    | >
    | > 3. Then try to apply the update again. What is the result?
    | >
    | > I appreciate your time.
    | >
    | > Have a nice day!
    | >
    | > Sincerely,
    | >
    | > Jenny Wu
    | > Microsoft CSS Online Newsgroup Support
    | > Get Secure! - www.microsoft.com/security
    | > ======================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > ======================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    | >
    | > --------------------
    | > >Thread-Topic: KB920685 won't install
    | > >thread-index: Acbmjzf/TGLkehn2RvaYxNCKNoYGhg==
    | > >X-WBNR-Posting-Host: 24.229.31.55
    | > >From: =?Utf-8?B?Um9iZXJ0?= <>
    | > >References: <>
    | > <>
    | > <>
    | > <>
    | > >Subject: Re: KB920685 won't install
    | > >Date: Mon, 2 Oct 2006 18:57:02 -0700
    | > >Lines: 119
    | > >Message-ID: <>
    | > >MIME-Version: 1.0
    | > >Content-Type: text/plain;
    | > > charset="Utf-8"
    | > >Content-Transfer-Encoding: 7bit
    | > >X-Newsreader: Microsoft CDO for Windows 2000
    | > >Content-Class: urn:content-classes:message
    | > >Importance: normal
    | > >Priority: normal
    | > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > >Newsgroups: microsoft.public.windows.server.sbs
    | > >Path: TK2MSFTNGXA01.phx.gbl
    | > >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:302012
    | > >NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > >X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > >
    | > >It's been a while, but just getting back to this issue.
    | > >
    | > >The log file has many attempts in it so I am only taking the latest
    | > install
    | > >attempt. Here it is:
    | > >
    | > >0.579: 2006/10/02 19:42:12.495 (local)
    | > >0.579:
    | >
    | > 4eb9323\update\update.exe (version 6.2.29.0)
    | > >0.579: Hotfix started with following command line: /si
    | > >/ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    | > >8.110: ---- Old Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.110: ---- New Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    | > >8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    | > >8.125: CreateUninstall = 1,Directory =
    C:\WINDOWS\$NtUninstallKB920685$
    | > >8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
    failed:
    | > >0xe0000102
    | > >8.141: ref tag c:\windows\system32\sp4.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp3.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp2.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp1.cab does not exist
    | > >8.141: ref tag c:\windows\system32\driver.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms4.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms41.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins1.cab does not exist
    | > >8.157: Starting AnalyzeComponents
    | > >8.157: AnalyzePhaseZero used 0 ticks
    | > >8.157: No c:\windows\INF\updtblk.inf file.
    | > >8.157: OEM file scan used 0 ticks
    | > >8.157: AnalyzePhaseOne: used 0 ticks
    | > >8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    | > >8.157: AnalyzeComponents: Hotpatching is disabled.
    | > >8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.188: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.297: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.360: AnalyzeForBranching used 31 ticks.
    | > >8.360: AnalyzePhaseTwo used 0 ticks
    | > >8.360: AnalyzePhaseThree used 0 ticks
    | > >8.360: AnalyzePhaseFive used 0 ticks
    | > >8.360: AnalyzePhaseSix used 0 ticks
    | > >8.360: AnalyzeComponents used 203 ticks
    | > >8.360: Downloading 0 files
    | > >8.360: bPatchMode = TRUE
    | > >8.360: Inventory complete: ReturnStatus=0, 235 ticks
    | > >8.360: Num Ticks for invent : 235
    | > >8.360: [dumpDownloadTask] We have all necessary files for the package
    to
    | > >install. Return STATUS_READY_TO_INSTALL
    | > >8.360: dumpDownloadTask returned 0xf201 (ready to install)
    | > >9.516: KB920685 installation did not complete.
    | > >9.516: Update.exe extended error code = 0xf201
    | > >
    | > >"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >
    | > >> Usually under the c:\windows folder but you can do a start, find
    | > 920685.log
    | > >>
    | > >> Robert wrote:
    | > >> > Where is the log file located?
    | > >> >
    | > >> > "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >> >
    | > >> >> Find the log file ...and can you post it here?
    | > >> >>
    | > >> >> Robert wrote:
    | > >> >>> Update KB920685 keeps failing. Other than the error code below,
    | > windows
    | > >> >>> update tells me nothing. I have no idea how to troubleshoot
    this to
    | > get it
    | > >> >>> installed. Any ideas? It's on SBS2003 (without SP1).
    | > >> >>>
    | > >> >>> Error Code: 0x8007F01E
    | > >> >>>
    | > >> >>> Thanks,
    | > >> >>> Robert
    | > >>
    | > >
    | >
    | >
    |
     
    Crina Li, Oct 23, 2006
    #12
  13. Robert

    Robert Guest

    I followed your instructions and still can't install. I now have 5 updates
    that are failing. When you say manual install, do you mean navigating to the
    c:windows\software distribution ........ folder and double clicking
    update.exe?

    When I do that I get error message "Failed to install catalog files."



     
    Robert, Oct 29, 2006
    #13
  14. Robert

    chace zhang Guest

    Hi,

    Thank you for continue contacting.

    As Crina is not in the office, I will be working with you on this issue.

    Manually install these update means download from Microsoft website, and
    install it on your SBS Server.

    Fro instance: you could download Security Update for Windows Server 2003
    (KB920685) from following address and double click to install it.

    http://www.microsoft.com/downloads/details.aspx?FamilyID=0182E8E7-9755-46CC-
    A393-C1E95FD508B2&displaylang=en


    Hope this helps, please let me know the result, if anything unclear, please
    do not hesitate to let me know.

    Have a nice day!

    Best Regards,

    Chace Zhang (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | Thread-Topic: KB920685 won't install
    | thread-index: Acb7o1kQGDHN+aE5QXelB56MBqzbXw==
    | X-WBNR-Posting-Host: 24.229.31.55
    | From: =?Utf-8?B?Um9iZXJ0?= <>
    | References: <>
    <>
    <>
    <>
    <>
    <>
    <>
    <>
    | Subject: Re: KB920685 won't install
    | Date: Sun, 29 Oct 2006 13:44:01 -0800
    | Lines: 311
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGXA01.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:308920
    | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | I followed your instructions and still can't install. I now have 5
    updates
    | that are failing. When you say manual install, do you mean navigating to
    the
    | c:windows\software distribution ........ folder and double clicking
    | update.exe?
    |
    | When I do that I get error message "Failed to install catalog files."
    |
    |
    |
    | ""Crina Li"" wrote:
    |
    | > Hi Robert,
    | >
    | > Thanks for your update.
    | >
    | > To narrow down the problem, would you please help me collect the
    following
    | > information?
    | >
    | > 1. Can you install the update manually?
    | > 2. Please try a clean boot to see how thing goes:
    | >
    | > 1) Click Start, click Run, and then in the Open box, type "MSCONFIG"
    | > (without the quotation marks). Click OK.
    | > 2) In the System Configuration Utility (MSConfig) window, click to
    select
    | > the Selective Startup button.
    | > 3) Click to clear the check mark from the "Load startup items" below
    | > Selective Startup.
    | > 4) Click the Services tab, click to check the "Hide All Microsoft
    Services"
    | > box, and remove all the check marks from the remained Non-Microsoft
    | > Services. Please note that the Exchange services could be marked as
    | > non-Microsoft. Please do not disable those services.
    | > 5) Click OK to close the MSConfig window. Click Yes when you are asked
    to
    | > restart your computer in order to enable the changes.
    | > 6) After restarting, please check whether this issue will reoccur.
    | >
    | > Thanks for your time and I look forward to hearing from you.
    | >
    | > Best regards,
    | >
    | > Crina Li (MSFT)
    | >
    | > Microsoft CSS Online Newsgroup Support
    | >
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | >
    | > =====================================================
    | >
    | > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    | > --------------------
    | > | Thread-Topic: KB920685 won't install
    | > | thread-index: Acbz7bCPsGsAYbwyST+4hA9YeoPpFA==
    | > | X-WBNR-Posting-Host: 207.46.199.61
    | > | From: =?Utf-8?B?Um9iZXJ0?= <>
    | > | References: <>
    | > <>
    | > <>
    | > <>
    | > <>
    | > <>
    | > | Subject: Re: KB920685 won't install
    | > | Date: Thu, 19 Oct 2006 19:16:02 -0700
    | > | Lines: 226
    | > | Message-ID: <>
    | > | MIME-Version: 1.0
    | > | Content-Type: text/plain;
    | > | charset="Utf-8"
    | > | Content-Transfer-Encoding: 7bit
    | > | X-Newsreader: Microsoft CDO for Windows 2000
    | > | Content-Class: urn:content-classes:message
    | > | Importance: normal
    | > | Priority: normal
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | Path: TK2MSFTNGXA01.phx.gbl
    | > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:306497
    | > | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > |
    | > | OK, I only had the LegacyImpersonationLevel key present, but I
    deleted
    | > it,
    | > | but my updates are still failing. I said updates, because since this
    | > issue
    | > | started I know have a total of 5 that are failing.
    | > |
    | > | Thanks!
    | > |
    | > | ""Jenny wu [MSFT]"" wrote:
    | > |
    | > | > Hi Robert,
    | > | >
    | > | > Thanks for posting back. I appreciate your time.
    | > | >
    | > | > Based on my research, the issue may occur due to that the default
    Dcom
    | > | > permissions was modified. When the default access permissions for
    dcom
    | > had
    | > | > been modified to allow access for other users and services, the
    adding
    | > of
    | > | > these users and services consequently removes the inherent
    | > "Administrators"
    | > | > allow access permission which is there by default.
    | > | >
    | > | > Please try to the steps below to resolve the issue:
    | > | >
    | > | > 1. You can bring the Dcom Default Access Permissions back to
    default by
    | > | > backing up following registry key:
    | > | >
    | > | > HKLM\SOFTWARE\Microsoft\Ole
    | > | >
    | > | > 2. Deleting the following values if they exist (which will be
    present
    | > only
    | > | > if the default Dcom settings were modified.)
    | > | >
    | > | > DefaultAccessPermission (only present if Default Access
    | > Permissions
    | > | > were modified)
    | > | > LegacyImpersonationLevel (only present if Impersonation Level
    was
    | > | > modified)
    | > | > LegacyAuthenticationLevel (only present if Default
    Authentication
    | > Level
    | > | > was modified)
    | > | >
    | > | > 3. Then try to apply the update again. What is the result?
    | > | >
    | > | > I appreciate your time.
    | > | >
    | > | > Have a nice day!
    | > | >
    | > | > Sincerely,
    | > | >
    | > | > Jenny Wu
    | > | > Microsoft CSS Online Newsgroup Support
    | > | > Get Secure! - www.microsoft.com/security
    | > | > ======================================================
    | > | > This newsgroup only focuses on SBS technical issues. If you have
    issues
    | > | > regarding other Microsoft products, you'd better post in the
    | > corresponding
    | > | > newsgroups so that they can be resolved in an efficient and timely
    | > manner.
    | > | > You can locate the newsgroup here:
    | > | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | >
    | > | > When opening a new thread via the web interface, we recommend you
    check
    | > the
    | > | > "Notify me of replies" box to receive e-mail notifications when
    there
    | > are
    | > | > any updates in your thread. When responding to posts via your
    | > newsreader,
    | > | > please "Reply to Group" so that others may learn and benefit from
    your
    | > | > issue.
    | > | >
    | > | > Microsoft engineers can only focus on one issue per thread.
    Although we
    | > | > provide other information for your reference, we recommend you post
    | > | > different incidents in different threads to keep the thread clean.
    In
    | > doing
    | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | >
    | > | > For urgent issues, you may want to contact Microsoft CSS directly.
    | > Please
    | > | > check http://support.microsoft.com for regional support phone
    numbers.
    | > | >
    | > | > Any input or comments in this thread are highly appreciated.
    | > | > ======================================================
    | > | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | > | >
    | > | > --------------------
    | > | > >Thread-Topic: KB920685 won't install
    | > | > >thread-index: Acbmjzf/TGLkehn2RvaYxNCKNoYGhg==
    | > | > >X-WBNR-Posting-Host: 24.229.31.55
    | > | > >From: =?Utf-8?B?Um9iZXJ0?= <>
    | > | > >References: <>
    | > | > <>
    | > | > <>
    | > | > <>
    | > | > >Subject: Re: KB920685 won't install
    | > | > >Date: Mon, 2 Oct 2006 18:57:02 -0700
    | > | > >Lines: 119
    | > | > >Message-ID: <>
    | > | > >MIME-Version: 1.0
    | > | > >Content-Type: text/plain;
    | > | > > charset="Utf-8"
    | > | > >Content-Transfer-Encoding: 7bit
    | > | > >X-Newsreader: Microsoft CDO for Windows 2000
    | > | > >Content-Class: urn:content-classes:message
    | > | > >Importance: normal
    | > | > >Priority: normal
    | > | > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > | > >Newsgroups: microsoft.public.windows.server.sbs
    | > | > >Path: TK2MSFTNGXA01.phx.gbl
    | > | > >Xref: TK2MSFTNGXA01.phx.gbl
    microsoft.public.windows.server.sbs:302012
    | > | > >NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > | > >X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > >
    | > | > >It's been a while, but just getting back to this issue.
    | > | > >
    | > | > >The log file has many attempts in it so I am only taking the
    latest
    | > | > install
    | > | > >attempt. Here it is:
    | > | > >
    | > | > >0.579: 2006/10/02 19:42:12.495 (local)
    | > | > >0.579:
    | > | >
    | >
    | > | > 4eb9323\update\update.exe (version 6.2.29.0)
    | > | > >0.579: Hotfix started with following command line: /si
    | > | > >/ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    | > | > >8.110: ---- Old Information In The Registry ------
    | > | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > | > >8.110: Destination:
    | > | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > | > >8.110: Destination:
    | > | > >8.110: ---- New Information In The Registry ------
    | > | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > | > >8.110: Destination:
    | > | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > | > >8.110: Destination:
    | > | > >8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    | > | > >8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    | > | > >8.125: CreateUninstall = 1,Directory =
    | > C:\WINDOWS\$NtUninstallKB920685$
    | > | > >8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
    | > failed:
    | > | > >0xe0000102
    | > | > >8.141: ref tag c:\windows\system32\sp4.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\sp3.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\sp2.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\sp1.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\driver.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    | > | > >8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\wms4.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\wms41.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\ims.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\ims1.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\ins.cab does not exist
    | > | > >8.157: ref tag c:\windows\system32\ins1.cab does not exist
    | > | > >8.157: Starting AnalyzeComponents
    | > | > >8.157: AnalyzePhaseZero used 0 ticks
    | > | > >8.157: No c:\windows\INF\updtblk.inf file.
    | > | > >8.157: OEM file scan used 0 ticks
    | > | > >8.157: AnalyzePhaseOne: used 0 ticks
    | > | > >8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    | > | > >8.157: AnalyzeComponents: Hotpatching is disabled.
    | > | > >8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    | > | > >8.157: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.157: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.157: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.157: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.157: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.172: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.172: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.172: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.172: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.172: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.188: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.204: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.204: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.204: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    | > | > >correct.
    | > | > >8.204: KB920685 Setup encountered an error: The update.ver file
    is
    | > not
    |
     
    chace zhang, Nov 1, 2006
    #14
  15. Robert

    KUHill Guest

    I'm having this same exact issue on one SBS box with six updates now that
    fail with the same 0x8007f01e errors. I've tried everything suggested here
    without any luck. I've googled quite a few folks with this issue, but no
    solution. Has anyone managed to fix this problem?

    Thanks,
    KHill

     
    KUHill, Nov 8, 2006
    #15
  16. Robert

    chace zhang Guest

    Hi,

    Thanks for your posting here.

    Please understand that our newsgroup is an issue based service, meaning we
    usually respond to one question/issue per post. This will lessen the
    confusion for both of us, as well as ensure that our results are accurate
    and not a result of a test for a different question. Therefore to keep
    this thread clean, I recommend you to open a new thread for further
    discussion. A support engineer will be assigned (maybe it will be me again).

    Thank you for your understanding and we look forward to hearing from you
    soon.


    Best Regards,

    Chace Zhang (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.


    --------------------
    | Thread-Topic: KB920685 won't install
    | thread-index: AccDkXH6AhvzhzkuRaOtgW95AvQh0g==
    | X-WBNR-Posting-Host: 128.227.142.89
    | From: =?Utf-8?B?S1VIaWxs?= <>
    | References: <>
    <>
    <>
    <>
    <>
    <>
    | Subject: Re: KB920685 won't install
    | Date: Wed, 8 Nov 2006 15:56:02 -0800
    | Lines: 228
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGXA01.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:311298
    | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | I'm having this same exact issue on one SBS box with six updates now that
    | fail with the same 0x8007f01e errors. I've tried everything suggested
    here
    | without any luck. I've googled quite a few folks with this issue, but no
    | solution. Has anyone managed to fix this problem?
    |
    | Thanks,
    | KHill
    |
    | ""Jenny wu [MSFT]"" wrote:
    |
    | > Hi Robert,
    | >
    | > Thanks for posting back. I appreciate your time.
    | >
    | > Based on my research, the issue may occur due to that the default Dcom
    | > permissions was modified. When the default access permissions for dcom
    had
    | > been modified to allow access for other users and services, the adding
    of
    | > these users and services consequently removes the inherent
    "Administrators"
    | > allow access permission which is there by default.
    | >
    | > Please try to the steps below to resolve the issue:
    | >
    | > 1. You can bring the Dcom Default Access Permissions back to default by
    | > backing up following registry key:
    | >
    | > HKLM\SOFTWARE\Microsoft\Ole
    | >
    | > 2. Deleting the following values if they exist (which will be present
    only
    | > if the default Dcom settings were modified.)
    | >
    | > DefaultAccessPermission (only present if Default Access
    Permissions
    | > were modified)
    | > LegacyImpersonationLevel (only present if Impersonation Level was
    | > modified)
    | > LegacyAuthenticationLevel (only present if Default Authentication
    Level
    | > was modified)
    | >
    | > 3. Then try to apply the update again. What is the result?
    | >
    | > I appreciate your time.
    | >
    | > Have a nice day!
    | >
    | > Sincerely,
    | >
    | > Jenny Wu
    | > Microsoft CSS Online Newsgroup Support
    | > Get Secure! - www.microsoft.com/security
    | > ======================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > ======================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    | >
    | > --------------------
    | > >Thread-Topic: KB920685 won't install
    | > >thread-index: Acbmjzf/TGLkehn2RvaYxNCKNoYGhg==
    | > >X-WBNR-Posting-Host: 24.229.31.55
    | > >From: =?Utf-8?B?Um9iZXJ0?= <>
    | > >References: <>
    | > <>
    | > <>
    | > <>
    | > >Subject: Re: KB920685 won't install
    | > >Date: Mon, 2 Oct 2006 18:57:02 -0700
    | > >Lines: 119
    | > >Message-ID: <>
    | > >MIME-Version: 1.0
    | > >Content-Type: text/plain;
    | > > charset="Utf-8"
    | > >Content-Transfer-Encoding: 7bit
    | > >X-Newsreader: Microsoft CDO for Windows 2000
    | > >Content-Class: urn:content-classes:message
    | > >Importance: normal
    | > >Priority: normal
    | > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
    | > >Newsgroups: microsoft.public.windows.server.sbs
    | > >Path: TK2MSFTNGXA01.phx.gbl
    | > >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:302012
    | > >NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
    | > >X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > >
    | > >It's been a while, but just getting back to this issue.
    | > >
    | > >The log file has many attempts in it so I am only taking the latest
    | > install
    | > >attempt. Here it is:
    | > >
    | > >0.579: 2006/10/02 19:42:12.495 (local)
    | > >0.579:
    | >
    | > 4eb9323\update\update.exe (version 6.2.29.0)
    | > >0.579: Hotfix started with following command line: /si
    | > >/ParentInfo:d5faa1d59f515949ac17e13d2c6852dd
    | > >8.110: ---- Old Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.110: ---- New Information In The Registry ------
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$\spuninst
    | > >8.110: Destination:
    | > >8.110: Source:C:\WINDOWS\$NtUninstallKB920685$
    | > >8.110: Destination:
    | > >8.125: SetProductTypes: InfProductBuildType=BuildType.IL
    | > >8.125: SetAltOsLoaderPath: No section uses DirId 65701; done.
    | > >8.125: CreateUninstall = 1,Directory =
    C:\WINDOWS\$NtUninstallKB920685$
    | > >8.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
    failed:
    | > >0xe0000102
    | > >8.141: ref tag c:\windows\system32\sp4.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp3.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp2.cab does not exist
    | > >8.141: ref tag c:\windows\system32\sp1.cab does not exist
    | > >8.141: ref tag c:\windows\system32\driver.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext.cab does not exist
    | > >8.141: ref tag c:\windows\system32\fp40ext1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms4.cab does not exist
    | > >8.157: ref tag c:\windows\system32\wms41.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ims1.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins.cab does not exist
    | > >8.157: ref tag c:\windows\system32\ins1.cab does not exist
    | > >8.157: Starting AnalyzeComponents
    | > >8.157: AnalyzePhaseZero used 0 ticks
    | > >8.157: No c:\windows\INF\updtblk.inf file.
    | > >8.157: OEM file scan used 0 ticks
    | > >8.157: AnalyzePhaseOne: used 0 ticks
    | > >8.157: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    | > >8.157: AnalyzeComponents: Hotpatching is disabled.
    | > >8.157: FindFirstFile c:\windows\$hf_mig$\*.*
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.157: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.172: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.188: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.204: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.219: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.297: KB920685 Setup encountered an error: The update.ver file is
    not
    | > >correct.
    | > >8.360: AnalyzeForBranching used 31 ticks.
    | > >8.360: AnalyzePhaseTwo used 0 ticks
    | > >8.360: AnalyzePhaseThree used 0 ticks
    | > >8.360: AnalyzePhaseFive used 0 ticks
    | > >8.360: AnalyzePhaseSix used 0 ticks
    | > >8.360: AnalyzeComponents used 203 ticks
    | > >8.360: Downloading 0 files
    | > >8.360: bPatchMode = TRUE
    | > >8.360: Inventory complete: ReturnStatus=0, 235 ticks
    | > >8.360: Num Ticks for invent : 235
    | > >8.360: [dumpDownloadTask] We have all necessary files for the package
    to
    | > >install. Return STATUS_READY_TO_INSTALL
    | > >8.360: dumpDownloadTask returned 0xf201 (ready to install)
    | > >9.516: KB920685 installation did not complete.
    | > >9.516: Update.exe extended error code = 0xf201
    | > >
    | > >"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >
    | > >> Usually under the c:\windows folder but you can do a start, find
    | > 920685.log
    | > >>
    | > >> Robert wrote:
    | > >> > Where is the log file located?
    | > >> >
    | > >> > "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
    | > >> >
    | > >> >> Find the log file ...and can you post it here?
    | > >> >>
    | > >> >> Robert wrote:
    | > >> >>> Update KB920685 keeps failing. Other than the error code below,
    | > windows
    | > >> >>> update tells me nothing. I have no idea how to troubleshoot
    this to
    | > get it
    | > >> >>> installed. Any ideas? It's on SBS2003 (without SP1).
    | > >> >>>
    | > >> >>> Error Code: 0x8007F01E
    | > >> >>>
    | > >> >>> Thanks,
    | > >> >>> Robert
    | > >>
    | > >
    | >
    | >
    |
     
    chace zhang, Nov 9, 2006
    #16
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.