Error 0x80070002 on one Windows Server 2016

Please run the following command in an elevated prompt and post the result.
Code: 
dism /online /remove-package /packagename:Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4739.2
 
Hmm, not present! Please run this command again and post the result.
Code: 
DISM /online /get-packages /format:table > "%USERPROFILE%\desktop\Packages.txt"
 
Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code: 
wusa /uninstall /KB:5041951
  • Let me know if it says it was successful or you get the message: The update KB5041951 is not installed on this computer.
 
Rich (BB code): 
Package_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0                                                    | Installed         | Security Update | 29.04.2022 08:32

Rich (BB code): 
2025-01-07 14:59:28, Error                 CBS    Failed to call external evaluate applicability on package: Package_34_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0, Update: 5011570-54_neutral [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-07 14:59:28, Info                  CBS    Failed to evaluate applicability state for XML package: Package_34_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-07 14:59:28, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

It seems there's an odd issue with older Servicing Stack Updates, we've already tried to force a reinstall with DISM which ended up in an error

Right-click on the file
577bf0efb8088-FRST.png
FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Files button.
Code: 
Package_1_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0.*;Package_34_for_KB5011570~31bf3856ad364e35~amd64~~14393.5001.1.0.*
  • 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.
 
Follow these instructions to install an update with DISM.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into it, and press enter. (Leave the CMD window open!)
Code: 
MD C:\WUTemp
  • Now, download the following update (KB5039885) to: C:\WUTemp - Or copy this file from the download directory to C:\WUTemp. (Important!)
    Downloadlink: KB5039885
  • Copy and paste the following commands one at a time into the command prompt and press enter after each.
Code: 
CD C:\WUTemp
EXPAND.exe windows10.0-kb5039885-x64-ndp48_bfa4d2aeefdb5ddd43fe417c5ddf4135be1c9837.msu -f:* C:\WUTemp
DISM.exe /Online /Add-Package /PackagePath:C:\WUtemp\Windows10.0-KB5039885-x64-NDP48.cab
  • Let me know if it says it was successful or if there are any errors. Or take a screenshot of the command prompt window and paste it into your next reply.
 
Please run the following command again with Process Monitor running:

Code: 
DISM /online /cleanup-image /AnalyzeComponentStore

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the DISM command
3. Stop Process Monitor a minute after it fails. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.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 the LogFile.PML and upload it to WeTransfer | Send Large Files Fast - Up To 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
 
I'm not sure what's happening on this server! Now the CBS log shows errors for updates e.g. (KB4089510 / KB4089510) from 2017 / 2018! So far as I can see this server is installed in 2021, so it's very strange that the CBS log shows issues for updates before that date - and of which no references can be found in the provided hive files?
 
I tried to install and "add-package" some updates that were missing, regarding cbs.logs (Service Stack Update) but it was unsuccessfull. If you don't have any other idea, I will try my luck with a Inplace-Upgrade
 
Yes, we've tried that before to install updates with DISM which also failed. So I think an in-place-upgrade would be the best and safest option and to avoid strange issues in the future.
 
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