[SOLVED] Windows Server 2016 PDC - DISM ERROR_FILE_NOT_FOUND or E_OUTOFMEMORY

F

FrenchTech

Well-known member
Joined
Apr 14, 2020
Posts
72
Hi all,

We installed a physical Windows Server 2016 Std server with an OEM DVD, domain controller, DNS/DHCP server, update OK, so far so good.

After several weeks, we needed to install additional components (XPS Viewer for example) and the installation did not work (0x80073701).

Attempt to repair via DISM but it does not work:
dism / online / cleanup-image / restorehealth => HRESULT = 0x8007000e - E_OUTOFMEMORY (the server has 64GB of RAM!)

Attempt to repair with local source ... failed
dism / online / cleanup-image / restorehealth /source:WIM:F:\sources\install.wim:2 / limitaccess => Error in operation: source for package or file not found, ResolveSource () unsuccessful. (CBS HRESULT = 0x800f081f)

We are trying something else:
DISM / Online / Cleanup-Image / StartComponentCleanup => HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND

Same here :
dism.exe / online / Cleanup-Image / StartComponentCleanup / ResetBase / restorehealth => HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE

The server has been restarted several times, the updates are done, if someone has an idea, I'm interested!

Thank you
 
Hi,

Thank you for your answer.

I followed the procedure but unfortunately, the SFCFix software remains blocked after a few steps on the message (more than 1 hour) :
Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.

Deployment image management and maintenance tool
Version: 10.0.14393.3241

Image version: 10.0.14393.3241

[========================== 100.0% ====================== =====]
Error: 0x800f0906

Unable to download source files.
Use the "source" option to specify the location of the files needed to restore functionality. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file is located in C: \ Windows \ Logs \ DISM \ dism.log

Can you tell me where is the log file that should open so that I try to recover its content and paste it here?

Thanks
 

Attachments

Hi! You have provided everything I need.


FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. 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.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4103720 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Hi!

Thanks.


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 run DISM again. Attach CBS.log.
 

Attachments

Hi!

Thank you.

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.
 
Hi !

Not this time.
now, if I try to add the XPS viewer, I get the error message: TID = 10128 Failed to process features change - CEnableDisableFeatureCommandObject :: InternalExecute (hr: 0x80073701) on DISM log
 
Hi!

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

see below contents of Fixlog file :
Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 15-04-2020
Exécuté par administrateur (17-04-2020 17:58:10) Run:2
Exécuté depuis C:\Users\Administrateur\Desktop
Profils chargés: KlNagSvc9A807AD29B9E & administrateur & MSSQL$SQLKASP (Profils disponibles: odelpierre & adebock & aplisson & gmay & maintenance & KlNagSvc9A807AD29B9E & mcguaegebeur & mdcollet & mbeyaert & jjgirard & administrateur & MSSQL$SQLKASP)
Mode d'amorçage: Normal
==============================================

fixlist contenu:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
CreateRestorePoint:
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-x..oyment-languagepack_31bf3856ad364e35_10.0.14393.0_tr-tr_53567e665e65fcd8]
"S256H"=hex:2d,22,2e,bf,25,ec,63,20,c3,1f,32,8f,05,10,7d,20,bc,d5,38,22,49,fb,\
bf,a3,ab,10,58,af,ef,eb,d8,88
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,58,70,73,\
2d,58,70,73,2d,56,69,65,77,65,72,2d,44,65,70,6c,6f,79,6d,65,6e,74,2d,4c,61,\
6e,67,75,61,67,65,50,61,63,6b,2c,20,43,75,6c,74,75,72,65,3d,74,72,2d,54,52,\
2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,30,2c,20,50,\
75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,\
36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,\
75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,\
6f,6e,53,78,53
"CF"=dword:0000000c
"c!microsoft-w..anguagepack_31bf3856ad364e35_10.0.14393.0_53567e665e65fcd8"=hex:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.14393.0_53567e665e65fcd8]
"appid"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,58,70,73,2d,\
58,70,73,2d,56,69,65,77,65,72,2d,44,65,70,6c,6f,79,6d,65,6e,74,2d,4c,61,6e,\
67,75,61,67,65,50,61,63,6b,2c,20,43,75,6c,74,75,72,65,3d,74,72,2d,54,52,2c,\
20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,30,2c,20,50,75,\
62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,\
34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,\
72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,\
6e,53,78,53
"CatalogThumbprint"="6598810abbcda53e25572c30d9859085c4dc69fe4b87ad4dd9826f10533b0682"
"p!CBS_microsoft-windows-xps-foundation-server-package~31bf3856ad36_9b08d17f6029d756"=hex:73,\
00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
58,70,73,2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,53,65,72,76,65,72,2d,50,61,63,\
6b,61,67,65,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,\
36,34,7e,74,72,2d,54,52,7e,31,30,2e,30,2e,31,34,33,39,33,2e,30,2e,58,70,73,\
2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,58,70,73,2d,56,69,65,77,65,72
"s!CBS_microsoft-windows-xps-foundation-server-package~31bf3856ad36_9b08d17f6029d756"=hex:73,\
00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
58,70,73,2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,53,65,72,76,65,72,2d,50,61,63,\
6b,61,67,65,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,\
36,34,7e,74,72,2d,54,52,7e,31,30,2e,30,2e,31,34,33,39,33,2e,30,2e,58,70,73,\
2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,58,70,73,2d,56,69,65,77,65,72
"i!CBS_microsoft-windows-xps-foundation-server-package~31bf3856ad36_9b08d17f6029d756"=hex:73,\
00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
58,70,73,2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,53,65,72,76,65,72,2d,50,61,63,\
6b,61,67,65,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,\
36,34,7e,74,72,2d,54,52,7e,31,30,2e,30,2e,31,34,33,39,33,2e,30,2e,58,70,73,\
2d,46,6f,75,6e,64,61,74,69,6f,6e,2d,58,70,73,2d,56,69,65,77,65,72


EndRegedit:
*****************


========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========

L'op‚ration a r‚ussi.


========= Fin de CMD: =========

Erreur: (0) Impossible de créer un point de restauration.
Registre ====> L'op�ration a r�ussi.


==== Fin de Fixlog 17:58:14 ====
 
Awesome ! It's working !!!!!! :-)

it worked for the XPS viewer but when I try the same with the Framework .net 3.5, I get the error code 0x80073701 again

See zipped cbs.log file
 

Attachments

I think I understand that Turkish language packages are problematic but I don't know how to fix this overall.

Do you think I will have the problem with each addition of roles or components?
 
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