Can't update to KB5060842 (June 2025)

I

Inasnum

New Member
Messages
11
Reaction score
1
I can't for the life of me update to KB5060842 via NTlite. I do it to online image it says "component store corruption" despite no scans show any corruption. I decided to try to do host-refresh and it has a new error I've never seen saying "Error 0x800703ee - [1006] The volume for a file has been externally altered so that the opened file is no longer valid". Tried it both with the NTlite update installer and going to the Windows update catalog and manually downloading it. What gives?
 

Attachments

The past 3 non-preview updates had failures using Ntlite also. For some reason preview updates install fine. I always turn servicing stack compatibility on so idk. But at least those other times I could at least do host-refresh until now.
 
Hi,

when you say preview, is it Beta Preview or Release Preview?
If Beta, then don't mix Beta and Release, it produces issues - unrelated to NTLite.

If however it is due to removals, then please do a Host Refresh using the latest version released today.
 
Release Preview. I don't mess with Insider stuff. I updated Ntlite today to latest version before I even tried updating or using Host Refresh. Both have errors
 
If you cannot install an update, do a Host Refresh.
If you got an error doing that as well, please attach zipped:
  • C:\$Windows.~BT\Sources\Panther\setupact.log
 
I can't even install the update to the ISO extracted folder that is used to Host Refresh
 
Inasnum said:
I can't even install the update to the ISO extracted folder that is used to Host Refresh
Click to expand...
Hm, then your DISM is broken - that is not something normal nor removals can cause it - unless Servicing Stack was removed which I doubt.
Send me %temp%\ntlite_dism.log for integrating only Cumulative Update to a clean non-edited ISO, the moment it fails.
And don't add any other actions, just send me that file plus C:\Windows\Logs\CBS\cbs.log zipped together.
 
You try update Windows 11 Professional 24H2 x64 - 10.0.26100.1742 on NTL from your host Windows 11 Professional 24H2 x64 - 10.0.26100.4061 - why do Host Refresh on a mounted image? It's not possible.
Working on a mounted image install updates first and do Apply, load updated image in NTL again and do your removals and tweaks.
 
francis11 said:
You try update Windows 11 Professional 24H2 x64 - 10.0.26100.1742 on NTL from your host Windows 11 Professional 24H2 x64 - 10.0.26100.4061 - why do Host Refresh on a mounted image? It's not possible.
Working on a mounted image install updates first and do Apply, load updated image in NTL again and do your removals and tweaks.
Click to expand...
The 4061 version you are seeing was an iso ripped folder I already updated. It’s what my online install was installed from that I save as a backup for host refresh’s and DISM fix image if the normal DISM scan fix method doesn’t work correctly. This process has worked well for me for a long time now. I realized why this was a problem this time, Microsoft must have upped their anti-bypass stuff cause all that was causing the problem with host refresh was that I had an empty appraiserres.dll in there and a bypass tweaked setup.exe from when even with NTlite tweaks tpm bypass (host included) on both install and boot images I wasn’t able to get past the setup.exe in upgrade mode cause of TPM requirements without using an empty appraiserres.dll AND the rufus setup.exe bypass to get by it. This time, as soon as I restored the proper appraiserres.dll and setup.exe it worked properly. Somehow they can tell it’s altered now.

​

 
Try check Settings\ System\ Setup requirement - TPM and secure boot - Host and disable instead of using a tweaked setup.exe and the home cooked appraiserres.dll.
 
francis11 said:
Try check Settings\ System\ Setup requirement - TPM and secure boot - Host and disable instead of using a tweaked setup.exe and the home cooked appraiserres.dll.
Click to expand...
That’s what I always do, that’s what I meant by “tpm bypass (host included)”. I just remember there was a period of time from 23h2 to now where no matter if I did every single tpm bypass option in NTlite and copied it to Boot/Install/WinRe, no matter what I couldn’t get past the tpm requirement in setup.exe when doing a host refresh. The only way was if I did the empty apparaiserres.dll, which worked for a bit but then it wouldn’t work unless I also also did the tweaked setup.exe. I’ve continued to do all of these things out of caution ever since with host refresh. Never had problems till now. Luckily tho the TPM tweaks on their own worked for me this time.
 
Setup requirement - RAM only applies to a clean install. It has no effect for an in-place upgrade.

Copying a null apparaiserres.dll fixes a number of different problems, because it doesn't just enforce the basic HW requirements, but can also have other blocking rules like checking for SSE4.2 instruction set, and specific gated drivers or apps which are known to cause problems.

Maybe NTLite should follow Rufus' lead in removing specific AppCompatFlag keys before launching Setup.exe.
https://github.com/pbatard/rufus/issues/2568#issuecomment-2387934171

Code: 
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\HwReqChk" /f /v HwReqChkVars /t REG_MULTI_SZ /s , /d "SQ_SecureBootCapable=TRUE,SQ_SecureBootEnabled=TRUE,SQ_TpmVersion=2,SQ_RamMB=8192,"
reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
 
nuhi said:
Hm, then your DISM is broken - that is not something normal nor removals can cause it - unless Servicing Stack was removed which I doubt.
Send me %temp%\ntlite_dism.log for integrating only Cumulative Update to a clean non-edited ISO, the moment it fails.
And don't add any other actions, just send me that file plus C:\Windows\Logs\CBS\cbs.log zipped together.
Click to expand...
I'm seeing something similar with a bunch of Windows 11 PC's (non-beta, non-insider) I've provisioned via an NTLite USB/ISO I created back in January. It might not be the same issue, please let me know if I need to create a new thread.

2025-06 KB5063060 fails with 0x80073712

[HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

The PC's installed the January through April cumulative updates without issue.

I'm trying to figure out how I can fix these (there's a few dozen) without doing an in-place re-install of Windows 11.

Trying to integrate this KB into the image results in this error;
1750042399985.png

That said, what's the best way to avoid down-the-road cumulative updates failing? I thought I was very light on component removal.
 
mwdksh said:
I'm seeing something similar with a bunch of Windows 11 PC's (non-beta, non-insider) I've provisioned via an NTLite USB/ISO I created back in January. It might not be the same issue, please let me know if I need to create a new thread.

2025-06 KB5063060 fails with 0x80073712

[HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

The PC's installed the January through April cumulative updates without issue.

I'm trying to figure out how I can fix these (there's a few dozen) without doing an in-place re-install of Windows 11.

Trying to integrate this KB into the image results in this error;
View attachment 14511

That said, what's the best way to avoid down-the-road cumulative updates failing? I thought I was very light on component removal.
Click to expand...
Best way to fix those is to run setup.exe from a pre-configured ISO.
Make sure to keep files and settings, more info here and a helper wizard in NTLite called Host Refresh, if the default way did not work.
 
I tried automating a setup.exe quiet in-place upgrade that downloads an ISO (most of our PC's are out in the field), but hit a language-pack mismatch. Our machines are set to English (Australia) (en-AU). Although en-AU inherits from en-GB, Windows seems to treats it differently and setup.exe refused to install quietly. While I could run it manually fine, it wasn't quite the right solution.

I then turned to the "Fix problems using Windows Update" --> "Reinstall now" button in settings.

Greyed out by default on update managed PC's (in our case), through process of elimination, I found that the presence of two registry keys greys it out.

HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Update\DeferFeatureUpdatesPeriodInDays_ProviderSet
HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Update\DeferQualityUpdatesPeriodInDays_ProviderSet

Code: 
# Remove two registry keys
$path = "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Update"
$blockingKeys = @(
    "DeferFeatureUpdatesPeriodInDays_ProviderSet",
    "DeferQualityUpdatesPeriodInDays_ProviderSet"
)

foreach ($key in $blockingKeys) {
    if (Get-ItemProperty -Path $path -Name $key -ErrorAction SilentlyContinue) {
        Remove-ItemProperty -Path $path -Name $key
        Write-Output "Removed: $key"
    }
}

# Wait a moment, then open the settings window
Start-Sleep -Seconds 2
start ms-settings:recovery

"Reinstall now" works well as it treats an in-place reinstall like a Microsoft-pushed build upgrade. The download appears in Windows Update with the tag (repair) and is interruptible unlike a scripted ISO download + setup.exe run which doesn't handle a mid-download restart well.

It does need admin rights to run, but otherwise it's just about the fastest and easiest way I can think of to fix cumulative update issues.
 
mwdksh said:
Code: 
# Remove two registry keys
$path = "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Update"
$blockingKeys = @(
    "DeferFeatureUpdatesPeriodInDays_ProviderSet",
    "DeferQualityUpdatesPeriodInDays_ProviderSet"
)

foreach ($key in $blockingKeys) {
    if (Get-ItemProperty -Path $path -Name $key -ErrorAction SilentlyContinue) {
        Remove-ItemProperty -Path $path -Name $key
        Write-Output "Removed: $key"
    }
}

# Wait a moment, then open the settings window
Start-Sleep -Seconds 2
start ms-settings:recovery
Click to expand...

You could shorten this to:
Code: 
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update\DeferFeatureUpdatesPeriodInDays_ProviderSet /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update\DeferQualityUpdatesPeriodInDays_ProviderSet /f
timeout /t 2 > NUL
start ms-settings:recovery
 
You must log in or register to reply here.
Back
Top