FOD packages not recognised?

T

TT9tWhD$q

Member
  • host: W10 x64 1909 b18363.657
  • NTL Home 1.9.0.7304 portable

packages been downloaded from UUP dump and renamed to the corresponding name and *.cab extension and are placed in \NTLite\Updates\10.0.1909.x64.FOD but when applying NTL skips those files and prints

> Operation requires missing files

What am I missing?
 

Attachments

  • log.txt
    9.2 KB
Did you look into the log file? Cannot find a correlation to folder/file permission.

The source folder is readable/accessible and the *.cab files opening fine in the OS explorer. The NTL log does not indicate an issue there.

As for the destination folder tmp\Win10_1909_English_x64\sources\sxs (extracted ISO with 7-zip) files and folder chain have flags enabled:

  • modify
  • read and execute
  • read
  • write
for:

  • authenticated users
  • system
  • administrators

and NTL is being executed as administrator. Adding files/folders via the OS's files explorer works fine.
 
The issue seems to be caused by a conflict in the naming convention between what UUP provides vs. what DISM expects, e.g. UUP (even with its renaming script) provides

1582102750545.png

vs. DISM expectation:

  • Microsoft-Windows-Xps-Xps-Viewer-Opt-Package~31bf3856ad364e35~amd64~~.cab

Having renamed the file at source the FOD is then being successfully applied.
 
Is there any more efficient way to figure out the package naming convention expected by DISM than having to first run NTL apply and trawl trough the DISM logs?
 
You must log in or register to reply here.
Back
Top