CodingWonders
Program exception
Hi, @Rapappa.
While I appreciate the fact that you provided an error log, it's not enough for me to diagnose this issue. For this, you need to submit the DynaLog logs.
They are stored in <program directory>\logs\DT_DynaLog.log. For example:
Getting install.wim packages fails with an error
I had the same error when loading install.wim using DISM Tools. I fixed it by disabling Windows Defender Real-Time and Pamper protection.
@jekovcar, it's a bit weird seeing an AV conflict with images.
Can you share your DynaLog diagnostic logs?
Hi there, When loading the install.wim package by DISMTools v0.7Update1 (not MSDN Win11_25H2_6899), I received a message with the error code: 80070003: An error occurred while getting information with the DISM API. Consider reading the message below for more information: The system cannot find the path specified.This does not indicate a program error, but it implies that you will not be able to perform some operations unless the issue is resolved. Does this mean that it is not possible to modify all futures? Thanks for support!
@jekovcar, in your case, it's failing because information about Features on Demand (capabilities) can't be obtained. That means that you can modify packages, features and Store apps, but not capabilities and drivers; as the info processes will stop when they encounter errors.
Can you try running the following as admin?
dism /image="D:\Downloads\w11\mount" /get-capabilities
(I'm assuming the mount path based on the logs)
- If DISM command-line does NOT succeed, then it's something wrong with the image
- If DISM command-line succeeds, this may be a bug with the API
I think it will not succeed. If it doesn't succeed, try looking for a FodMetadata package:
Lite images often tend to remove these.
dism /image="D:\Downloads\w11\mount" /get-capabilities Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26200.6899 Error: 3 The system cannot find the path specified. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
@jekovcar, then it's something wrong with the image. I provided some more information in my previous comment, because most Lite images tend to remove metadata packages related to FoDs.