Windows Update KB4556799 fails at 100% Error 0x80071160

Ex_Brit said:

Question, in a "repair" install does Win10 allow for a choice of which system to use? (In my case C: or O:) or do I have to do it when logged into my O: drive?

I reviewed your dism log from post 1 and see that dism failed due to O: not being recognized, this was apparent through-out the log.

Is this log current or old?


2019-06-19 08:24:55, Info DISM DISM WIM Provider: PID=10996 TID=1996 [O:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-06-19 08:24:55, Info DISM DISM Imaging Provider: PID=10996 TID=1996 The provider WimManager does not support CreateDismImage on O:\ - CGenericImagingManager::CreateDismImage
2019-06-19 08:24:55, Info DISM DISM Imaging Provider: PID=10996 TID=1996 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage




Sorry, that was the incorrect dism code I had posted.

Ex_Brit said:

That's was a new log. How very odd. Until this update I never had any hint that there was a problem.

I'm no log scanning expert but I noticed many errors relating to O: not being valid. I'm looking for a solution now.

Ex_Brit said:

Thanks

I'm sorry Peter, I've used dism extensively but only repairing Windows on C: . I'm certain there's a method to repairing images located elsewhere. I have another remote image I can experiment on.


Did you attempt to run dism from O: if that's where the corrupted image resides?

Ex_Brit said:

From O: yes.
Regarding a W10 installer recognizing other drives for a repair, I have a feeling that was never allowed but I was hoping someone at MS had finally seen the light and given W10 abilities allowed in previous OS's. My favourite was Vista Ultimate, it had all the bells and whistles and then things started disappearing after that. In some cases hardly noticeable but in others bad. One doesn't expect retrograde abilities as one progresses up the Windows ladder. So now I have a full installation disk and am waiting until I hear back from you.

I successfully launched dism from F: which has an older Windows image, however; it still identified my winver as the current OS.

F:\Windows\System32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool

Version: 10.0.17134.1

Image Version: 10.0.17763.973

No component store corruption detected.The operation completed successfully.


F:\Windows\System32>c:
C:\Windows\System32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool

Version: 10.0.17763.771

Image Version: 10.0.17763.973

No component store corruption detected.The operation completed successfully.


I would recommend you start a new thread titled something like; How to run dism on backup image drive O:

Sorry I'm not familiar enough with how to complete this task but I'm confident there are many others here who can assist.

Ex_Brit said:

Question, in a "repair" install does Win10 allow for a choice of which system to use? (In my case C: or O:) or do I have to do it when logged into my O: drive?

I don't know if I am missing something here, but I don't see why you cannot try the Repair Install on drive:\O (when you are logged in on it). — Always important not to forget to backup first. If that still doesn't work by not allowing you to install this update, you definitely have a corrupt installation for drive:\O. In that case, as per your first proposition, I would go for the formatting process and start from scratch to rebuild this partition: O, if it is that important to you. Once again, don't forget to save any important data to another drive before formatting.

That way, you will save some time instead of spelunking for solutions with DISM command-lines. Just my thought.