Server 2019 reverting all updates

[azidhaka]

Hello all,

I have a Windows Server 2019, version 1809, build 17763.3770, that cannot install any updates for two months now, always reverting them. Here's what was tried until now:

1. sfc /scannow completes with: Windows Resource Protection did not find any integrity violations.

2. Dism /Online /Cleanup-Image /RestoreHealth goes to 94.4% and then: Error: 0x800f081f; The source files could not be found.
Here I tried specifying /Source with multiple install.wim files, for example the original install image and the latest one from Microsoft, all unsuccessful with the same error message.

3. SFCFix runs until DISM, has the same error as above and stays like that forever.

CBS logs and ComponentsScanner log attached. Thanks in advance!

 

[Gary R]

Can you please supply me with a copy of 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.
• The file will likely be too large to upload here, if so please upload to a file sharing service.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

PS. Going to be out for most of the morning (my time GMT) so will be this afternoon before I see your reply.

 

[azidhaka]

Thank you, here it is.

 

[Gary R]

Thanks.

Need to consult with my colleagues on something found in your CBS.log and COMPONENTS hive, which is going to cause some delay, also close to midnight here, so will be tomorrow at the earliest before I get back to you.

 

[Gary R]

Sorry for the delay, had problems sourcing the necessary files to patch things.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download SFCFix.exe and save it to your desktop.
• Download the attachment SFCFix.zip and also save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[azidhaka]

Thank you!

DISM ran successfully, I can test installing updates this night when the server is not in use.
Attached SFCFix.txt and CBS.log.

 

[Gary R]

Not seeing any errors in your logs, so yes please try updating your server when you can.

If successful please let me know.

If not, please post me the CBS.log created after your update attempt.

 

[azidhaka]

Hi, finally managed to try and install the updates in the middle of the night, sorry about the delay.
Unfortunately all updates reverted again, i am attaching CBS.log right after the system booted.

 

[Gary R]

Your log shows a .... 0x80070020 - ERROR_SHARING_VIOLATION ... but unfortunately CBS does not give us enough information to know what's causing it.

We need to run a scan whilst your computer is updating, so that we can determine what's causing the error.

• Download and run Process Monitor
  • Leave this running while you perform the next steps.
• Try updating the system just like you have in the past.
• Stop Process Monitor as soon as it fails.
  • You can simply do this by clicking the "Square" icon on the toolbar (third one from the left) or by hitting Ctrl+E
• Select the File menu ... Save ... and save the file to your Desktop.
  • The name will be LogFile.PML.
• Zip the file, and upload to a file sharing service.
• Provide the link to LogFile.PML
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Also attach a copy of your ... C:\Windows\Logs\CBS\CBS.log ... with your reply.

 

[azidhaka]

Unfortunately, a disaster happened.

After staging the updates for installation again and rebooting, the VM with that Server 2019 will not start anymore - Inaccessible Boot Device. Which is very strange for a VM, i guess the VMware paravirtual driver pvscsi got damaged somehow by the constant installation/revert of updates and Windows cannot see its boot disk.

Anyway, after trying to revive it for a day, I restored from earlier backup and paused the updates.

I am thinking about rebuilding that server from scratch, can't trust that installation anymore. What do you think?

 

[Gary R]

Well we haven't done anything that would cause that kind of problem, which would tend to suggest that there's some underlying issue with your machine that was not apparent in any of the logs you submitted.

Just what that might be is impossible to determine from the information so far available.

A rebuild or a repair install is certainly what I'd recommend for a "quick" (well quicker than trying to analyse and repair things manually anyway) resolution to your problems.

 

[Gary R]

This topic is now closed.

If you still need any help and need it re-opening, then please contact a staff member, or open a new topic and wait for a new helper.