Windows 10 update error 0x800f0922 (possibly also tied into 0x80070005)

D

duck

Member
Joined
Dec 1, 2022
Posts
8
I've been having issues with updating Windows 10 ever since I updated to KB5012170. The update installed correctly, however every consecutive update has failed with the same error code - 0x800f0922. The only updates that do not fail are .NET and Security updates, they download and install correctly. Every cumulative and feature update fails.

My laptop came with Windows 10 Pro ver. pre-installed upon purchase. It was reset to factory settings when received to skip the bloatware that came pre-installed.

A full/clean reinstall currently is off the table as I do not have an outter HDD/SSD where I can back my data up to. I'm also wary about attempting to do a partial re-install, because the updates keep failing and I'm not convinced that it will fix it based on the posts I've read across different forums.

Additionally, I've noticed in the event viewer a constant error "Update Windows license and product key tokens failed with 0x80070005." It shows up several times a day, from what I can tell through filtering, but I'm not sure when it started. I've seen some people mention that it is possibly tied to my current issue, as it may relate to permissions being broken somewhere, but because I'm not experienced with this, I'm not sure whether it truly is the case or not. I just figured it might be worth mentioning.
 

Attachments

Maxstar said:
Hi and welcome to Sysnative,

This is a known issue with the Secure Boot Update from August, 9 2022 - (KB501210), and this problem still has the status: investigating.

SummaryOriginating updateStatusLast updated
Update might fail to install and you might receive a 0x800f0922 error
Security update for Secure Boot DBX might fail to install.		OS Build 19044.1880
KB5012170
2022-08-09		Investigating2022-10-18
10:04 PT

Source: Windows 10, version 21H2
Click to expand...
Hi, thanks for your fast reply and for taking the time to reply to my post.

I've read about this previously, but I suppose I misunderstood when I read it in this case, as I'm currently updated to KB5012170, updating past it is impossible.

When I initially read this, I understood it as the specific update will fail to install, not the consecutive updates.

Just in case I've confused myself further, here is a screenshot of my update history.

updates.PNG
 
Hi,

Please provide a copy of the CBS folder with all the previous logs.
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Maxstar said:
Hi,

Please provide a copy of the CBS folder with all the previous logs.
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
Click to expand...

Thank you, here it is.
 

Attachments

I've seen different issues after installing KB5012170, either when this update was installed succesfully. But it seems there is a problem with the tokens.dat file as well as reported in the previous CBS logs.

Please open an elevated command prompt and run the following commands:
Code: 
net stop sppsvc
ren %SystemRoot%\system32\spp\store\2.0\tokens.dat tokens.bkp
net start sppsvc
cscript.exe %SystemRoot%\system32\slmgr.vbs /rilc
Reboot the system and attempt to update, if it fails attach a new copy of the CBS log.
 
Maxstar said:
I've seen different issues after installing KB5012170, either when this update was installed succesfully. But it seems there is a problem with the tokens.dat file as well as reported in the previous CBS logs.

Please open an elevated command prompt and run the following commands:
Code: 
net stop sppsvc
ren %SystemRoot%\system32\spp\store\2.0\tokens.dat tokens.bkp
net start sppsvc
cscript.exe %SystemRoot%\system32\slmgr.vbs /rilc
Reboot the system and attempt to update, if it fails attach a new copy of the CBS log.
Click to expand...
Unfortunately it didn't work, here is the log.
 

Attachments

Maxstar said:
Do you have a product key for this Windows 10 Pro version?
Click to expand...
It's a digital key, I don't believe anything in the box the laptop came in had it written down anywhere. I have a Windows sticker underneath my laptop, however it doesn't have a code on it, just a holographic sticker with the Windows 10 logo.
 
Okay, could you please check the activation state in the Settings settings Window.
 
That's fine, once Windows is correctly activated the option disappears. Please check if the event viewer is still reporting this error 0x80070005 for the Tokens.dat file.
 
Maxstar said:
That's fine, once Windows is correctly activated the option disappears. Please check if the event viewer is still reporting this error 0x80070005 for the Tokens.dat file.
Click to expand...
Unfortunately, it still does.

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

Download the 64 bit version: - Farbar Recovery Scan Tool Link

  • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  • Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
  • Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
  • Press the Scan button.
  • Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  • Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
You must log in or register to reply here.

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

Back
Top