Cumulative update keeps failing to install / rolling back - SPP Installer access denied

TripleM

Member
Joined
Oct 8, 2022
Posts
19
I recently purchased a new computer with Windows 11 Home installed. Not long afterwards, I started receiving an error that a Windows 11 Cumulative Update failed to install.

I tried running standard steps like renaming the SoftwareDistribution folder, scf /scannow and RestoreHealth, and also manually installing the update from the Microsoft Catalogue. The Catalogue install also failed to install the first couple of times, but after some combination of repeating the above steps, it appeared to install fine.

However, it continued to show an update was available in Windows Update, and continued to fail.

Now every so often it prompts me to restart to install the update. In my original attempt, it restarted fine, though now when I restart, it hangs on the restarting screen - have left it for about 30 minutes at times. When I eventually force power off (and in my original attempt), it then says it's installing the updates, then an error has occurred and it has to roll back to the previous version.

In the CBS log (CbsPersist_20221008205503.log in the attached folder), the relevant part appears to be:
Code:
2022-10-09 09:32:49, Info                  CSI    000008cd Begin executing advanced installer phase 31 index 0 (sequence 0)
    Old component: [l:0]''
    New component: [l:0]''
    Install mode: delta
    Smart installer: true
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: 'SppInstaller'
2022-10-09 09:32:49, Error                 CSI    000008ce (F) SPP Installer: SLpUpdateComponentTokens completed with hr=0x80070005[gle=0x80004005]
2022-10-09 09:32:49, Error                 CSI    000008cf (F) SPP Installer: ProcessInstallOrUninstall (SppInst) completed with hr=0x80070005[gle=0x80004005]
2022-10-09 09:32:49, Info                  CSI    000008d0@2022/10/8:20:32:49.551 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};(null);524273us
2022-10-09 09:32:49, Info                  CSI    000008d1 End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED)

2022-10-09 09:32:49, Error      [0x01803c] CSI    000008d2 (F) Failed execution of queue item Installer: SppInstaller ({1b265fd2-721c-4e59-ad55-9d102a5d1d7f}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

The only other thing I wanted to mention - may be entirely unrelated, but anyway - is that when first receiving the computer, I wanted to set up a scheduled task, but upon opening Task Scheduler, I would receive an error that "MMC could not create the snap-in". I followed a tutorial online for using 'Turn Windows features on or off' to turn on .NET Framework 3.5 options, which resolved the problem.

Have run through the steps in the stickied posting instruction thread. Any support would be greatly appreciated.
 

Attachments

Forgot to mention - the update it's currently trying to install is KB5017383. But earlier on it was KB5017328. (I assume cumulative means it just keeps trying to install the latest one, which is why the version numbers are changing.) And SFCFix reports no issues.
 
Last edited:
No takers? :( Even if no solution, does anyone have tips as to how I may go about collecting more information that may help me track down an issue?
 
Hi and welcome to Sysnative,

No takers? :(
Please see this thread on why it may take a while before a helper will reply to your post.



Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Files button.
Code:
sppinst.dll
  • When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
  • Post the logfile Search.txt as attachment in your next reply.
 
Attached.

PS - are there any logs I can provide that may help determine why restarting to install updates is hanging on the restarting screen? The CBS.log timestamps appear to be after I force a reboot. Maybe two unrelated issues, since I never had the restart issue the original time around, but if something is hanging it'd be nice to know what it is.
 

Attachments

Hi,

Yes, we could perform a Process Monitor trace with boot logging. But let's check the Software Protection Platform service first.
Open an elevated command prompt and run the following two commands and post the result in your next reply.
Code:
sc query sppsvc
sc qc sppsvc
 
Code:
C:\Windows\system32>sc query sppsvc

SERVICE_NAME: sppsvc
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\Windows\system32>sc qc sppsvc
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: sppsvc
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START  (DELAYED)
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : C:\Windows\system32\sppsvc.exe
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Software Protection
        DEPENDENCIES       : RpcSs
        SERVICE_START_NAME : NT AUTHORITY\NetworkService

C:\Windows\system32>
 
This looks good, so perform the following steps with ProcMon.

Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install the update just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service like: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
 
See attached.

I actually did something slightly different - apologies, I know you said attempt just like in the past - rather than click update and restart, I clicked update and shut down.

For reference, it took a few moments to do so due to a 'DDE Server Window'. But then it did start attempting the update without hanging - but quickly saying it failed and would roll back.

Have attached that boot log, but I will redo it with update and restart if preferred.

BootLog.zip
 
Here's also the part of the CBS log for cross-referencing timestamps if helpful:

Code:
2022-10-13 21:54:40, Info                  CSI    00000832 Begin executing advanced installer phase 31 index 0 (sequence 0)
    Old component: [l:0]''
    New component: [l:0]''
    Install mode: delta
    Smart installer: true
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: 'SppInstaller'
2022-10-13 21:54:40, Error                 CSI    00000833 (F) SPP Installer: SLpUpdateComponentTokens completed with hr=0x80070005[gle=0x80004005]
2022-10-13 21:54:40, Error                 CSI    00000834 (F) SPP Installer: ProcessInstallOrUninstall (SppInst) completed with hr=0x80070005[gle=0x80004005]
2022-10-13 21:54:40, Info                  CSI    00000835@2022/10/13:08:54:40.383 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};(null);5905us
2022-10-13 21:54:40, Info                  CSI    00000836 End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) 

2022-10-13 21:54:40, Error      [0x01803c] CSI    00000837 (F) Failed execution of queue item Installer: SppInstaller ({1b265fd2-721c-4e59-ad55-9d102a5d1d7f}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2022-10-13 21:54:40, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
 
Yes, please perform a restart instead of a shutdown.

Process Monitor
---------------------------
The file 'C:\Users\User\Desktop\BootLog\Bootlog.pml' was not closed cleanly during capture and is corrupt.

Edit:
The timestamps might be helpfull indeed, so please post a new copy of the CBS.log along with the new ProcMon trace in your next post.
 
OK, restarting didn't hang either - maybe the restart hang was a one off glitch. But still rolled back the update.

Have double checked the exported log opens this time for me before uploading.

BootLog.zip
 

Attachments

Please upload a copy of the COMPONENTS hive, so I can compare some results from the ProcMon with the registry entry's.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Download and run SetupDiag from Microsoft
  • Download
    60e45c659164d-SetupDiag.png
    SetupDiag to your desktop.
  • Right-click on SetupDiag.exe and select Run as administrator.
  • When completed the following files are created: "Logs.zip, SetupDiag.exe.config and SetupDiagResults.log"
  • Attach SetupDiagResults.log and Logs.zip to your next reply.
 
Unfortunately SetupDiagResults.log is empty and no Logs.zip is generated. If I run it via an elevated command prompt rather than right clicking on it (so it doesn't disappear instantly), all it says is:
Code:
SetupDiag was unable to find a relevant log file.  Exiting!
Tried this twice, including immediately after another attempted update, but same result both times.
 
Additional info if helpful - the windows update history page says the update failed with error 0x800f0922.
 
After doing a little more searching for that specific code, I've discovered that if I go into "Turn Windows features on or off", and attempt to turn on .NET Framework 3.5 (includes .NET 2.0 and 3.0), I get the same error code. Maybe related.
 
Hi,

Yes it is absolutely possible, I've seen a similar case before, with this error 0x800f0922 and rollback issues which were related to .NET Framework.

Please run the following commands in an elevated command prompt and let me know the result. And post a new copy of the CBS log after running the commands below.
Code:
dism /online /enable-feature /featurename:netfx3 /all
dism /online /enable-feature /FeatureName:NetFx4Extended-ASPNET45 /all
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top