• joscon [Microsoft] joscon [Microsoft]
    23 Nov 2012 4:25 PM

    That's a source issue, use the /LimitAccess switch with the command to avoid using a WSUS server.  Additionally, if you're pointing to a media source, make sure its been updated

  • Anonymous Hmza
    24 Nov 2012 6:27 PM

    Please review my DISM log and point the problem after the /Limitaccess switch plus source that error tells is the Kb2756872 update which it cannot repair

    Total Operation Time: 419 seconds.

    - CDISMPackageManager::Internal_Finalize

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64  - CDISMPackageManager::Internal_Finalize

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64 <----- Ending corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64  - CDISMPackageManager::Internal_Finalize

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock

    2012-11-24 23:11:46, Error                 DISM   DISM Package Manager: PID=1752 TID=64 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    2012-11-24 23:11:46, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2012-11-24 23:11:46, Info                  DISM   DISM Package Manager: PID=1752 TID=64 Finalizing CBS core. - CDISMPackageManager::Finalize

  • Anonymous Hmza
    24 Nov 2012 6:28 PM

    Continued....

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=1752 TID=64 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2012-11-24 23:11:46, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    2012-11-24 23:11:46, Info                  DISM   DISM.EXE:

    2012-11-24 23:11:46, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

    2012-11-24 23:11:46, Info                  DISM   DISM.EXE:

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=2708 TID=1712 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=2708 TID=1712 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2012-11-24 23:11:46, Info                  DISM   DISM Provider Store: PID=2708 TID=1712 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  • joscon [Microsoft] joscon [Microsoft]
    24 Nov 2012 10:08 PM

    DISM logs aren't helpful for this, they only show problems with DISM.  The CBS.log, referred to above is where you'd need to look for the problem.  The exit code you have basically says it cannot get to a source.  Sources can be local or Windows Update

  • Anonymous Hmza
    30 Nov 2012 12:46 PM

    Entering CBS log gives me : access denied message even running the log in the admin cmd gives the same.Is there something wrong with the log?

  • joscon [Microsoft] joscon [Microsoft]
    30 Nov 2012 3:15 PM

    Nope, you just need to open it via notepad at an elevated command prompt.

  • Anonymous Mike
    10 Feb 2013 1:06 AM

    Hey Joscon

    I do have some problem here as well.  After doing a /restorehealth it says its corrupted or unrepairable.  How can I fix this? I cannot see any error within cbs or dism log...

    All that related to the reinstallation of the .net 3.5  

    Even tried to get it from CD as with WU....

    Thx!!

  • joscon [Microsoft] joscon [Microsoft]
    10 Feb 2013 1:17 AM

    Can you put the CBS and DISM logs somewhere for me please?

  • Anonymous Mike
    16 Feb 2013 1:40 PM

    Sorry for the delay.

    DISM http://pastebin.com/g4bYfMA4

    CBS http://pastebin.com/25G0FUrq

    I cannot find what happened.

    Thanks

  • joscon [Microsoft] joscon [Microsoft]
    20 Feb 2013 4:23 PM

    Mike

    The only thing I see here is CSI corruption, that's not something IBCR is meant to recover as far as I know, which is why its failing.  Unfortunately, a lot of CSI based issues aren't repairable without a repair install.  Does your event log show anything like disk corruption or other errors recently?

  • Anonymous Mike
    23 Feb 2013 1:23 PM

    Thanks for the update, its pretty much what I think too.

    However its my dad's comp and it has been this way for a long time, he said.  So figures...

    That said, will a "reinstall" over it would fix it? Or a clean install? Or the feature that "reset" windows in the settings ?

    No big deal either way, but I'll take the easiest, of course.

    Thanks a bunch.

  • Anonymous Mike
    23 Feb 2013 1:24 PM

    Also, no, there is no disk corruption, everything is clean.  Its an upgrade from Win7 to Win8 and I expect it to have gone wrong somewhere...  Its a new comp, less than a year out of the check disk everything was fine.

  • joscon [Microsoft] joscon [Microsoft]
    23 Feb 2013 1:57 PM

    Mike;

    Really, the best thing is a clean install however an in-place upgrade (installing over top), should replace the component store as part of its routine.  I've seen instances where this doesnt happen but it was generally as a result of bad hardware.

  • Anonymous Mike
    24 Feb 2013 4:36 PM

    Joscon,

    Well thanks for the input, I really appreciate.  I will then try to re-install over it... in order to keep as much as possible of his current setup, otherwise will be the whole thing.

    Thanks again!

  • joscon [Microsoft] joscon [Microsoft]
    24 Feb 2013 9:32 PM

    No problem, let me know how it goes.

<>