[SOLVED] Windows Server 2019 - KB5017315 fails 0x800f0922

Hi,

Question, is the Hyper-V feature installed on this server? To gather some more information, please run the following command in an elevated command prompt.
Code: 
Dism /online /Get-Features /format:table | find "Microsoft-Hyper-V"
Copy and paste the result in your next post.
 
No, this is not a Hyper-V machine, nor is it installed.

C:\Windows\system32>Dism /online /Get-Features /format:table | find "Microsoft-Hyper-V"
Microsoft-Hyper-V | Disabled
Microsoft-Hyper-V-Offline | Disabled
Microsoft-Hyper-V-Online | Disabled
Microsoft-Hyper-V-Management-Clients | Disabled
Microsoft-Hyper-V-Management-PowerShell | Disabled
 
Hi,

Could you please provide an export of the following registry key, attach regexp.txt to your next post.
  • Click the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • Copy and paste the following command line and press Enter.
Code: 
reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" "%userprofile%\desktop\regexp.txt"
  • When finished, a logfile called regexp.txt is saved on your desktop.
  • Post the logfile as attachment in your next reply.
 
Last edited:
Here you go...

The October update is going to hit this weekend and I'm certain it is going to fail as well.
 
Hi,

I think this problem needs some deeper investigation, so I would advise to pause the updates up to 35 days.
1. Open Settings > Updates and Security > Advanced Options.
2. Here you can disable Windows Update for a while (35 days)

Pause-updates.png

It seems there is a problem with one of the accounts on this server, however I'll need to do some research to figure out what it could be.

Question: The profile below is not listed in the profile list, do you know which account's are present, and whether potentially corrupted (unused) accounts are exist?

Registry\USER\S-1-5-21-4293667947-2900317051-3627133161-1112

Rich (BB code): 
2022-10-03 07:29:48, Error                 CSI    0000033c (F) STATUS_OBJECT_NAME_NOT_FOUND #119519# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x8450bfbda8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[61]'\Registry\USER\S-1-5-21-4293667947-2900317051-3627133161-1112'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1354743660)[gle=0xd0000034]
2022-10-03 07:29:48, Error                 CSI    0000033d@2022/10/3:11:29:48.956 (F) onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-10-03 07:29:48, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2022-10-03 07:29:48, Info                  CBS    Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2022-10-03 07:29:48, Error                 CSI    0000033e (F) STATUS_OBJECT_NAME_NOT_FOUND #119518# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ), oa = @0x8450bfc298->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[61]'\REGISTRY\USER\S-1-5-21-4293667947-2900317051-3627133161-1112'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1354744208)[gle=0xd0000034]
2022-10-03 07:29:48, Error                 CSI    0000033f (F) STATUS_OBJECT_NAME_NOT_FOUND #119516# from Windows::Rtl::SystemImplementation::CUserProfile::OpenProfileRootKey(...)[gle=0xd0000034]
2022-10-03 07:29:48, Info                  CSI    00000340@2022/10/3:11:29:48.958 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{f60fff05-7c5c-48dd-a1d2-b75aa14ad9b4};(null);161906463us
2022-10-03 07:29:48, Info                  CSI    00000341 End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) 

2022-10-03 07:29:48, Error      [0x018063] CSI    00000342 (F) Failed execution of queue item Installer: Per-User Registry Installer ({f60fff05-7c5c-48dd-a1d2-b75aa14ad9b4}) with HRESULT HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND).  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]

Rich (BB code): 
2022-10-03 07:30:17, Info                  CSI    00000379 The queue has completed running, and AI failures have occured.
2022-10-03 07:30:17, Info                  CSI    0000037a ==Error Summary Start==
2022-10-03 07:30:17, Error                 CSI    0000037b (F) Installer: Per-User Registry Installer    Binary Name: wcp.dll    ErrorCode: 80070002    Phase: 31    Mode: Delta    Component: NONE[gle=0x80004005]
2022-10-03 07:30:17, Info                  CSI    0000037c ==Error Summary End==
2022-10-03 07:30:17, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 100.
2022-10-03 07:30:21, Info                  CSI    0000037d Failed unloading hive file: \??\C:\Users\Administrator\NTUSER.DAT, key: \Registry\User\S-1-5-21-4293667947-2900317051-3627133161-500, with flags: 0, NTSTATUS: -1073741535

2022-10-03 07:30:21, Error                 CSI    0000037e@2022/10/3:11:30:21.641 (F) internal\onecorebase\inc\auto_hive.h(358): Error STATUS_CANNOT_DELETE originated in function Windows::Rtl::AutoHive::Unload expression: UnloadStatus
[gle=0x80004005]
 
Oh, frak! I think I mixed up files from the two open cases I have here.

The "rollback" incident occurred on a server that was not the one I pulled the user list from - and was not the server that the first link pointed to.

I am >SO< sorry. I should have put some kind of indicator as to which server was which in the titles so I could track better.

Here is the correct version of the reg export that matches the cbs / dism logs.
 

Attachments

Hi,

No problem at all, I will ask a moderator/admin to remove the other attachement (post#5) from this thread.
 
Hi,

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.
 
It seems that running this utility is unnecessary.
The server that has rolled back updates for the past two months has successfully installed October's patches.
I'm closing this out - with my thanks and apologies for having troubled you with misleading data.

The server linked to in the initial post has, unfortunately, once again fallen victim. Will be opening a new thread for that.

Larry
 
Hi,

Glad to hear the latest LCU installed successfully, hopefully you won't have any future issues with this server. If so, please refer to this thread, just as a reference regarding the previous problems.
 
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