Original report by me.
Assemblies with "type=driverUpdate" are treated in a special way. Their files are placed into
System32\DriverStore\FileRepository[assembly_driverstore_keyform]*
Preserving whatever file structure they have listed.
Most of the time, their files don't list any target folder, so ManifestEnum's FileBrowser places them into root folder (or System32, depending on the approach).
This is incorrect, these assemblies should be treated in a special way. Maybe we should do this in the FileBrowser, or maybe when importing.
Original report by me.
Assemblies with "type=driverUpdate" are treated in a special way. Their files are placed into
System32\DriverStore\FileRepository[assembly_driverstore_keyform]*
Preserving whatever file structure they have listed.
Most of the time, their files don't list any target folder, so ManifestEnum's FileBrowser places them into root folder (or System32, depending on the approach).
This is incorrect, these assemblies should be treated in a special way. Maybe we should do this in the FileBrowser, or maybe when importing.