[SOLVED] WS2016 Update error 0x80070003 and DISM error 1734 the array bounds are invalid

[Maxstar]

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.

prnms003.inf

• 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.

 

[novikoff]

Attached Search

 

[novikoff]

Attached Search English Version

 

[Maxstar]

Please run the following script as well to check the prnms003.inf file.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

 

[novikoff]

Attached SFCFix

 

[Maxstar]

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

 

[novikoff]

Attached SFCFix

 

[Maxstar]

Please reboot the server and attempt to update. If it fails attach a new copy of the CBS logs and the setupapi.dev.log file.

 

[novikoff]

The OS tried to install updates for a very long time - it rebooted by 67% - tried again and wrote that it could not install updates and rolled back. There may be a problem with the KB5022289 update - there were no problems with updates before it. Is it possible to temporarily disable the installation of this update?
Attached CBS and setupapi.dev.log

 

[novikoff]

OS downloads KB5022289 update again - I don't understand how to stop it?

 

[novikoff]

Using the "Show or hide updates" utility, I hide the KB5022289 update. Downloaded the update
KB4589210 from the January update package - got up successfully. Apparently the problem is in KB5022289.

 

[Maxstar]

Please don't install other updates or hiding them, this makes it more difficult to resolve this issue.

Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[novikoff]

Good morning.
Update KB5022289 is constantly downloading and trying to install. This leads to reboots and rollback server updates, and sometimes hangs during installation or rollback. Therefore, I had to turn off this update, because the server has the work load. Update KB5022289 is downloaded as a cab file. You can try to install it at any time.
Result DISM:
DISM system
Version: 10.0.14393.4169

Version of the image: 10.0.14393.4169

[==========================100.0%==========================]
Recovery has been completed successfully.
The operation has been completed successfully.

 

[Maxstar]

2023-02-06 17:24:17, Info                  CSI    00000200 Loading user account SID S-1-5-21-1690063197-4030611139-3235995255-500
2023-02-06 17:24:17, Info                  CSI    00000201 Loading user account SID S-1-5-21-2705350124-596544029-2804636408-1122
2023-02-06 17:24:17, Info                  CSI    00000202 Loading user account SID S-1-5-21-2705350124-596544029-2804636408-1125
2023-02-06 17:24:17, Info                  CSI    00000203 Loading user account SID S-1-5-21-2705350124-596544029-2804636408-1128
2023-02-06 17:24:17, Info                  CSI    00000204 Loading user account SID S-1-5-21-303467522-632721244-1183953779-1151
2023-02-06 17:24:17, Error                 CSI    00000205@2023/2/6:14:24:17.284 (F) onecore\base\wcp\rtllib\inc\auto_hive.h(180): Error c0000033 [Error,Facility=(system),Code=51 (0x0033)] originated in function Windows::Rtl::AutoHive::Load expression: (null)
[gle=0x80004005]

Good morning too,

Please provide a export of the ProfileList.

• 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.

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" /s > "%userprofile%\desktop\ProfileList.txt"

• When finished, a logfile called ProfileList.txt is saved on your desktop.
• Post the logfile as attachment in your next reply.

 

[novikoff]

Attached ProfileList.
WS2016 has the role of a terminal and a web server. There are terminal connection profiles, but it didn't hurt before

 

[Maxstar]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-21-303467522-632721244-1183953779-1151
    ProfileImagePath    REG_EXPAND_SZ    C:\Users\..000
    ForensiTMigrated    REG_DWORD    0x1

That shouldn't be a problem, but the profile above seems to be the issue. This is the last profile as showed in the CBS log before the error message. Do you know which users SID this is?

 

[novikoff]

The link to this profile is only in the registry. Screenshots are attached. Apparently, these are the remnants of Forensit Profile Wizard program. Previously, this server was transferred to another domain using it.

 

[Maxstar]

Thanks, the first screenshot shows two double accounts with a different SID, and the account with 501 at the end is not listed in the profilelist?

 

[novikoff]

These are different accounts - one local, the other domain. 501 also has two guest accounts - local and domain. Screenshots are attached. Some accounts do not have a profile, because they did not log in to this server

 

[Maxstar]

Thanks for the clarification, I would suggest to remove the profile remnant of Forensit Profile Wizard program first and then try to update again to see what happens this time.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-21-303467522-632721244-1183953779-1151