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
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
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
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?
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!!
Sorry for the delay.
DISM http://pastebin.com/g4bYfMA4
CBS http://pastebin.com/25G0FUrq
I cannot find what happened.
Thanks
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.
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,
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!