Error 0x8000ffff on Windows Server 2019 Update Installation fails

N

Neo767

Member
Joined
Jan 29, 2020
Posts
24
Error 0x8000ffff on Windows Server 2019, Update Installation fails

Hi
I hope you could help me.
Server 2019 who won`t install any more Windows updates.
Error 0x8000ffff
It also states that it had to reboot to finish a system repair.
Right after you hit the reboot it quots "Windows is beeing prepared dont shut down"
After each reboot the system asks for reason for the reboot, because it thinks it crashed.

Followed the Instructions for posting in "Windows Update Forum" posting instructions
Hope you could help me.
As the server is a VM I exportet it to a my testsystem and could test every solution.


sfc /scannow
A Systemrepair which is requiers a reboot is blocking sfc
Still there after a few reboots

Dism /Online /Cleanup-Image /RestoreHealth
Fehler: 0x8000ffff

SFCFix
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-29 23:57:49.792
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-01-30 00:05:19.624
----------------------EOF-----------------------


What steps have I already tried:
- Forcefully remove Pending Updates (pending.xml is about 19 MB)
System was in an unstable state after this

- Dism with revertpendingactions
Updates are partially applied, so he won`t roll back

- Uninstall the last Update
System become unstable


Checked the CBS log and found an error for
Hashes for file member [l:13]'Defender.psd1' do not match.

Tried the suggested Fix from Microsoft
https://support.microsoft.com/en-us...-flags-windows-defender-ps-files-as-corrupted
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess
DISM Error is still 0x8000ffff

I attached the dism and the CBS logs.

Best regards

Neo
 

Attachments

Hello and welcome!

Please do the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Hi Thank you for your Help.

Sorry for the late response, I didn`t get a email that somebody anwsered in this thread.

Please find attachted the log.
I changed all specific Usersnames in the log to xxxxx.
 

Attachments

softwaremaniac said:
Retry updates please.
Click to expand...

Still getting the 0x8000ffff error if i try installing the Updates or dism with repair option

SCFIX still doesn`t find an error


SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-02-25 19:54:00.523
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-02-25 19:59:05.562
----------------------EOF-----------------------
 
Luckly I took a snapshot before running sfcfix.

I reverted it and copied the CBS file. Please find it attached.
 

Attachments

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
softwaremaniac said:
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
Click to expand...


Here are the requestet Logfiles

Logfile.zip
 
Hi!

Let's try the following fix:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Reboot and retry updating.
 

Attachments

softwaremaniac said:
Hi!

Let's try the following fix:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Reboot and retry updating.
Click to expand...

Please find attached the Logfile.

Problem still persists.
Installation Error on 0x8000ffff
 

Attachments

softwaremaniac said:
What do you mean exactly by saying that the system was in an unstable state after removing pending.xml?
Click to expand...

I hope I get this right, because its been a few weeks.

After removing the pending.xml the system behaves extremly wired.
- Dism with repair-options wanted a recovery system but did not accept any source I provided.
- Installing of the patches also falled.
- Strange errors all across the eventlog

I havent had the time to dig in this further because it was a live system.

If you think it helps, we could try this on my testmachine.
 
softwaremaniac said:
Yes, I would like to see if you get a different error after removing it.
Click to expand...
Hi,
At first the Errorcode is 0x80073712 because he was ready to install CU2020-03

After I searched for the new download it says Error 0xca00a000
Windows Troubleshooter could not find a solution
DISM.exe /Online /Cleanup-image /Restorehealth returns Error 14098
Please find attached the new dism.log


EDIT:
Out of curiosity I snapshoted the VM and removed the Softwaredistribution folder and searched for new Updates
Errorcode 0x80073712 is stated after this
 

Attachments

Last edited:
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