[SOLVED] Host refresh - Failed in SAFE_OS phase during APPLY_IMAGE

[HolyK]

SOLVED!

Hi!

I have perfectly working modified Win10 Pro 22H2 (19045.2364) installation. Recently i needed to use OBS Studio and found that screen capture is not working due to missing Microsoft.Windows.CapturePicker (100% the cause, I've validated that in VM)

I wanted to use Host refresh to re-add the removed system component but sadly the refresh fails with:

0x80070003 - 0x2000C
The installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation

Note that the error occurred in VM where I wanted to test this before I do the same on my live system. The VM has the same reduced version as my live system with NTLite (Activated).

Steps i did (followed the Docs):
- Extracted the original (unmodified) Windows installation ISO (the one from which i build my modified installation)
- In NTLite -> Tools -> Host Refresh -> Add -> Added the directory with the extracted original Win ISO
- Import Preset -> Imported the preset i used to build my modified installation and then selected it in the drop-down menu (Attached to post as well)
- Prompt for manual adjustment is checked
- After the ISO is loaded i went to Components and Re-checked the "Capture Picker" system app
- I did not changed anything else, no additional patches were added. Just Apply -> Continue and the build process started
- Win upgrade starts, it goes through the check phase, followed by the blue "Installing Win10" screen. Then it restarts to "Working on Updates" screen, restarts again and then i see "Undoing changes made to your computer" and then the error screen above.

Google did not helped much with the error. I've build the ISO twice (as some posts mentioned corrupted installation), no luck.

Any suggestions/help how to fix this? Am I doing something wrong?

BTW: Is there any another/alternative way how to re-install that one previously removed system application CapturePicker ? That is pretty much what i need.

Thank you in advance for help!

 

[HolyK]

SOLVED: It was a C: drive space issue. Apparently 28GB (!) free space was not sufficient. Added another +50GB to the VM and the error did not occurred again. F! Microsoft and their cryptic error codes...

nuhi Maybe a small suggestion to add a note that removal of CapturePicker breaks the OBS (and most likely any other capturing SW using the Windows screencapture API)

 

[clarensio]

SOLVED: It was a C: drive space issue. Apparently 28GB (!) free space was not sufficient. Added another +50GB to the VM and the error did not occurred again. F! Microsoft and their cryptic error codes...

nuhi Maybe a small suggestion to add a note that removal of CapturePicker breaks the OBS (and most likely any other capturing SW using the Windows screencapture API)

Personally, I have been removing for a long time (Win 10 and Win 11 23H2):

<c>captureservice 'Capture service'</c>​

<c>microsoft.windows.capturepicker 'Capture Picker'</c>​

and OBS Studio (from 27.2.4 to the current 30.1.2) installs and works perfectly (even in VM).
I would investigate the actual cause "more thoroughly".

 

[HolyK]

Personally, I have been removing for a long time (Win 10 and Win 11 23H2):

<c>captureservice 'Capture service'</c>​

<c>microsoft.windows.capturepicker 'Capture Picker'</c>​

and OBS Studio (from 27.2.4 to the current 30.1.2) installs and works perfectly (even in VM).
I would investigate the actual cause "more thoroughly".

OBS has two capture methods.

BitBlt ( DXGI Desktop Duplication API ) - In general it works OK but it has issues with certain windows/app types - mainly HW accelerated SW. Either it shows black screen or it glitches. I had issues capturing google meet within HW accelerated browser. It broke the window content upon size change, etc. Also it must run on the same GPU as display, which can get a bit tricky if you have multiple displays/GPUs and apps "locked" to certain GPU.

Windows 10 ( Windows Graphics Capture API ). It works flawlessly, resizing window or moving it outside of the capture area and back works w/o issues. Yes, there is that annoying orange border but personally i don't care, it is not present in the output video anyway. Also it works cross-GPU so no more messing with App locking to specific GPU. The function/API is apparently delivered by the Capture Picker Application.



And I am pretty much sure that removing Capture Picker breaks the second one. When I was chasing the cause i've ended up with two nearly identical ISOs/VMs where the only difference was that one had Capture Picker removed. And for that one OBS was showing black screen when WGC capture method was selected.

Hope it is more clear now.

 

[clarensio]

OBS has two capture methods.

BitBlt ( DXGI Desktop Duplication API ) - In general it works OK but it has issues with certain windows/app types - mainly HW accelerated SW. Either it shows black screen or it glitches. I had issues capturing google meet within HW accelerated browser. It broke the window content upon size change, etc. Also it must run on the same GPU as display, which can get a bit tricky if you have multiple displays/GPUs and apps "locked" to certain GPU.

Windows 10 ( Windows Graphics Capture API ). It works flawlessly, resizing window or moving it outside of the capture area and back works w/o issues. Yes, there is that annoying orange border but personally i don't care, it is not present in the output video anyway. Also it works cross-GPU so no more messing with App locking to specific GPU. The function/API is apparently delivered by the Capture Picker Application.

View attachment 11788

And I am pretty much sure that removing Capture Picker breaks the second one. When I was chasing the cause i've ended up with two nearly identical ISOs/VMs where the only difference was that one had Capture Picker removed. And for that one OBS was showing black screen when WGC capture method was selected.

Hope it is more clear now.

I wanted to thank you because actually (and I had never noticed this) without the "capture picker" the Windows Graphics Capture API mode was not available.