Windows Update on Win7 x64 just going round in circles

Discussion in 'Windows 7 Help and Support' started by nginmu, May 1, 2016.

  1. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Completely fresh reinstall of Windows 7 Ultimate x64 on a Dell Inspiron 1570 laptop.

    Using the entire 160 Gb new hard disk, formatted as per windows setup.

    Installing from a USB stick loaded with W7 installation files purchased from ebay. I am using the SLIC in the machine's BIOS together with a matching xrm-ms certificate file via slmgr.vbs to perform OEM SLP activation - this has proceeded uneventfully and control panel reports 'Genuine Windows'.

    It absolutely will not download Windows Updates. It just sits there with the blue progress bar going across. And across. And across. For days (I think, in truth, the longest I have left it running for is probably.. 20 hours?)

    I've tried a number of fixes I've found elsewhere on the net:

    - running .net_cleanup_tool.exe from Microsoft. It appears to uninstall all .net components apart from those (2.0, 3.0, 3.5?) that are preinstalled as part of W7, and then installing .NetFx35ClientSetup.exe and .NetFx45_Full_setup.exe both from MS.

    - MicrosoftFixit50123.msi

    - WindowsUpdateDiagnostic.diagcab

    - Completely turning off all firewalls

    - ensuring WU & BITS services are started

    - running windows_repair_aio_setup.exe from a site called tweaking 'full stop Charlie Oscar Mike'

    - installing WU standalone installer, Windows6.1-KB947821-v34-x64.msu

    - installing WindowsUpdateAgent-7.6-x64.exe




    error messages I have encountered along the way so far:

    Windows Update error 0x8024402C(2016-04-29-T-07_33_09A);
    Service registration is missing or corrupt;
    Access to the path 'C:\Windows\softwaredistribution' is denied;
    standalone WU installer: Installer encountered an error: 0x8024800c
    standalone WU installer: Installer encountered an error: 0x8024001e

    can anyone help me get Windows Update working?
     
    #1 nginmu, May 1, 2016
    Last edited: May 1, 2016
  2. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Hi Have you tried this? This was taken from a @kemical help reply!;) and copied here!!
    Please run these scans to check for and repair corruption:

    File scans
    Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
    sfc /scannow
    press enter and await results

    In the same command prompt and after the above scan has finished type:
    dism /online /cleanup-image /restorehealth
    Press enter and await results (longer this time).

    If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
     
  3. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Thanks buddy - I've tried sfc /scannow (sorry, omitted to mention that one) but not in the exact manner you suggest. Will try it...
     
  4. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
  5. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    yeah, did go there & ran MicrosoftFixit50123.msi, it completed ok but didn't solve the problem.87% through the first pass of sfc /scannow right now.

    edit.. ok done 1st pass. results:

    Code:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>
    
    going onto next bit
     
  6. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Looks goods! I have added 3 links to this thread!;) You may get more replies from other members latter.
    Hang in there!;)
     
  7. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    hmm.. error..
     

    Attached Files:

  8. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    relevant portion of dism log

    Code:
    2016-05-01 12:50:48, Info  DISM  DISM Provider Store: PID=1580 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-05-01 12:50:48, Info  DISM  DISM Provider Store: PID=1580 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:24, Info  DISM  PID=556 Scratch directory set to 'C:\Users\Paul\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
    2016-05-01 23:52:24, Info  DISM  PID=556 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Manager: PID=556 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM.EXE:
    2016-05-01 23:52:24, Info  DISM  DISM.EXE: <----- Starting Dism.exe session ----->
    2016-05-01 23:52:24, Info  DISM  DISM.EXE:
    2016-05-01 23:52:24, Info  DISM  DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
    2016-05-01 23:52:24, Info  DISM  DISM.EXE: Executing command line: dism  /online /cleanup-image /restorehealth
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Getting Provider FolderManager - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Getting Provider FolderManager - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=556 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Manager: PID=556 Successfully loaded the ImageSession at "C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC" - CDISMManager::LoadImageSession
    2016-05-01 23:52:24, Info  DISM  DISM Image Session: PID=3028 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:24, Info  DISM  DISM OS Provider: PID=3028 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM OS Provider: PID=3028 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2016-05-01 23:52:24, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Warning  DISM  DISM Provider Store: PID=3028 Failed to Load the provider: C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Manager: PID=556 Image session successfully loaded from the temporary location: C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC - CDISMManager::CreateImageSession
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  CSI  00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2016-05-01 23:52:25, Info  CSI  00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Target image information: OS Version=6.1.7601.17514, Image architecture=amd64
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  CSI  00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2016-05-01 23:52:25, Info  CSI  00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2016-05-01 23:52:25, Info  CSI  00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2016-05-01 23:52:25, Info  CSI  00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  CSI  00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2016-05-01 23:52:25, Info  CSI  00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
    2016-05-01 23:52:25, Info  DISM  DISM OS Provider: PID=3028 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
    2016-05-01 23:52:25, Info  DISM  DISM Driver Manager: PID=3028 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Loading Provider from location C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Connecting to the provider located at C:\Users\Paul\AppData\Local\Temp\2CFEC487-2864-4EB0-BE9D-A4E5CD438DBC\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: OSServices
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: MsiManager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: IntlManager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: DriverManager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: SmiManager
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2016-05-01 23:52:25, Info  DISM  DISM Transmog Provider: PID=3028 Current image session is [ONLINE] - CTransmogManager::GetMode
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 The option(restorehealth) is not recognized in this context. - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2016-05-01 23:52:25, Info  DISM  DISM Image Session: PID=3028 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Package Manager: PID=3028 Finalizing CBS core. - CDISMPackageManager::Finalize
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=3028 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: Image session has been closed. Reboot required=no.
    2016-05-01 23:52:25, Info  DISM  DISM.EXE:
    2016-05-01 23:52:25, Info  DISM  DISM.EXE: <----- Ending Dism.exe session ----->
    2016-05-01 23:52:25, Info  DISM  DISM.EXE:
    2016-05-01 23:52:25, Info  DISM  DISM Image Session: PID=556 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=556 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=556 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-05-01 23:52:25, Info  DISM  DISM Provider Store: PID=556 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    
    
     
  9. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Hi Maybe @kemical will see this thread and reply. I suggest restart and then run sfc /scannow again.
    I have heard the big bogs say it can take 3 attempts to fix all the errors??
     
  10. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Right.. will give it a go. I saw you posted a link to 'How do I reset Windows Update components?' & there's some stuff in there I haven't tried yet, so I'll give that a go tomorrow; bed calls now. Thanks for helping. Getting really frustrated with this Windows Update prob but, I get like a dog with a bone when something won't work lol.. determined to get it fixed!
     
  11. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Hi You are not the only one having trouble with the W7 up dates. Users are reporting that it takes days.
    I'm thinking some of this is because there is a lot of demand.
    I'm sure you will Get-er-Done! A good nights sleep will help!;)
    PS Welcome to the forum!
     
  12. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Yes it's crossed my mind there's actually no problem, it's just the server's not responding maybe? I dunno. Anyways.. in danger of a serious attack of insomnia if I don't make myself log off & go to bed lol. Cheers till the morrow :)

    [edit.. I've just tried updating using 'autopatcher' & it's worked fine. Still rather get the proper Microsoft offering working though ;-)
     
    #12 nginmu, May 1, 2016
    Last edited: May 2, 2016
  13. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Sorry to double-post. I spoke too soon.. Autopatcher actually isn't doing it.

    It downloaded all the updates with absolutely no problem. But when it came to install time - it hung at 98% on the first item.

    I noticed I could get that item to complete by opening task manager and 'ending process' on wusa.exe *32

    Autopatcher then proceeded to the next update - same thing again. It re-invoked wusa.exe, and hung at 98%. I killed wusa.exe, and it completed.

    And on and on..

    Eventually I went into C:\Windows\system32, took ownership of, and renamed wusa.exe to xxxxxxxwusa.exe

    Cleared prefetch, and did a heavy duty disk cleanup incl. system files, and ran ccleaner. Then rebooted.

    Same thing again! wusa,exe *32 popping up - from where I don't know (I thought the above would have removed any cached copies of it)

    I don't know why wusa.exe is coming up as the 32-bit version of the Windows Update Standalone Installer.. but wondering if it's the cause of the problems (it's a 64 bit system and OS?) Maybe this wusa.exe is supplied by autopatcher..

    Anyway, getting the feeling that somewhere along the line, wusa.exe might be involved in the overall problem of W7 updates stalling forever?
     
  14. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Sorry friend! I have no experience with wusa ! I'm a little confused, but that's normal for me. Are you trying uninstall wusa??
    This may not be what you're asking, but when I uninstall a program I use a free app called search everything. It will find all the files and folders and you can delete them. I also use regedit to clean the registry, but you really need to know what you're doing when messing with the registry!
    Here's link for Search Everything. It's a great program to have for searching your PC! It will find every thing! Keep me informed on your progress!
    Everything Search Engine
     
  15. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    I was just hoping to disable it just as a diagnostic.. to see if stopping it made any difference to the windows update problem. I'm probably on a wild goose chase though. I got the idea into my head that because it showed up in task manager as wusa.exe *32, on a 64 bit system, and was appearing to stall the installation of the updates, then maybe it should have been wusa.exe *64.. Anyway I still have to run through those other suggestions you posted. In charge of 2 x 6 year olds atm though, doesn't mix well with computer tinkering lol. Back at it after MacDonalds.

    :)



    [edit

    Been through everything several times now - no joy I'm afraid. Seems a tough nut this one.

    [edit

    Killed wusa.exe:

    Code:
    del C:\Windows\System32\wusa.exe
    del C:\Windows\winsxs\x86_microsoft-windows-wusa_31bf3856ad364e35_6.1.7601.17514_none_af07fb6876def437\wusa.exe
    del C:\Windows\SysWOW64\wusa.exe
    del C:\Windows\Prefetch\*.pf
    
    Now, autopatcher runs perfectly (except whenever it takes an .msu update to 98%, it now asks which program it should use to open it..)

    So.. looks like I'm able to download updates from Microsoft servers just fine; there's definitely something dicky going on with wusa.exe
     
    #15 nginmu, May 2, 2016
    Last edited: May 2, 2016
  16. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Does this look like I have a bad copy of wusa.exe on my installation media?

    Logfile from sfc /scannow

    Code:
    2016-05-02 22:15:11, Info  CSI  000002eb [SR] Cannot repair member file [l:16{8}]"wusa.exe" of Microsoft-Windows-WUSA, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
    2016-05-02 22:15:12, Info  CSI  000002ec [SR] Cannot repair member file [l:16{8}]"wusa.exe" of Microsoft-Windows-WUSA, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
    2016-05-02 22:15:12, Info  CSI  000002ed [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
    2016-05-02 22:15:12, Info  CSI  000002ee [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:16{8}]"wusa.exe"; source file in store is also corrupted
    
    
     
  17. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    #17 holdum333, May 2, 2016
    Last edited: May 2, 2016
  18. nginmu

    nginmu New Member

    Joined:
    May 1, 2016
    Messages:
    16
    Likes Received:
    0
    Thanks buddy. Well I scanned all the copies of wusa.exe, and none came up with any infection. I checked the md5's on the files & they are all recognised widely on the net so, I guess they are as they should be. I absolutely hate to give up but this one's a rock hard brick wall eh :-( just have to explain to the customer he should maybe consider either win 10 or a flavour of Linux.
     
  19. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Your welcome! I'll bet you're not giving up, just taking a little break. I really like W10.
    Where did you end up? With just wusa errors? My first time hearing about wusa.exe. I'm going to keep searching.
    I learn new things every day, but I also forget things!:rofl:Don't be a stranger here. Come back and share your knowledge!
     
  20. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    I found wusa.exe on my W10!
    Capture48.JPG
     

Share This Page

Loading...