SOLVED

What PE headers are invalid in files to be packaged?

%3CLINGO-SUB%20id%3D%22lingo-sub-324149%22%20slang%3D%22en-US%22%3EWhat%20PE%20headers%20are%20invalid%20in%20files%20to%20be%20packaged%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324149%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI've%20seen%20in%20the%20log%20files%20for%20the%20MSIX%20Packaging%20Tool%20the%20following%20line%3A%3C%2FP%3E%3CPRE%3EAnalyzing%20%5B%7BCommon%20Programs%7D%5D%5Cmyfile.ext%20for%20invalid%20PE%20Headers.%3C%2FPRE%3E%3CP%3EI%20have%20the%20ability%20to%20check%20the%20PE%20headers%20in%20my%20customer's%20files%20before%20sending%20them%20to%20be%20packaged.%26nbsp%3B%20Can%20you%20tell%20me%20what%20would%20make%20them%20invalid%20so%20I%20can%20pre-emptively%20check%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324735%22%20slang%3D%22en-US%22%3ERe%3A%20What%20PE%20headers%20are%20invalid%20in%20files%20to%20be%20packaged%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324735%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20not%20run%20into%20any%20issues%20yet%20but%20I%20haven't%20run%20the%20tool%20at%20scale%20yet.%3C%2FP%3E%3CP%3EI%20was%20just%20hoping%20to%20get%20ahead%20of%20any%20issues%20before%20sending%20an%20app%20through%20the%20tool.%3C%2FP%3E%3CP%3EI'm%20already%20checking%20the%20headers%20to%20look%20for%20the%20kernel%20drivers%2C%20printer%20drivers%2C16bit%20files%20(on%20x64%20OSs)%20etc.%20that%20are%20unsupported%20by%20MSIX.%26nbsp%3B%20Was%20hoping%20for%20a%20list%20of%20anything%20else%20I%20may%20have%20missed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324731%22%20slang%3D%22en-US%22%3ERe%3A%20What%20PE%20headers%20are%20invalid%20in%20files%20to%20be%20packaged%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324731%22%20slang%3D%22en-US%22%3E%3CP%3EStandard%20check%20to%20ensure%20the%20header%20is%20valid%20%5Bvalid%20Win32%20application%2C%20Import%20Tables%2C%20%5D%20and%20to%20get%20in%20front%20of%20any%20LoadLib%20issues.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20you%20getting%20errors%3F%20If%20you%20are%20repackaging%20a%20standard%20installer%2C%20you%20are%20not%20likely%20to%20run%20into%20any%20issues%20here.%20Hopefully%20you're%20customer's%20aren't%20playing%20with%20ResHack%2C%20otherwise%2C%20nothing%20to%20worry%20about.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi

I've seen in the log files for the MSIX Packaging Tool the following line:

Analyzing [{Common Programs}]\myfile.ext for invalid PE Headers.

I have the ability to check the PE headers in my customer's files before sending them to be packaged.  Can you tell me what would make them invalid so I can pre-emptively check?

Thanks

2 Replies
Best Response confirmed by carl_b (New Contributor)
Solution

Standard check to ensure the header is valid [valid Win32 application, Import Tables, ] and to get in front of any LoadLib issues. 

 

Are you getting errors? If you are repackaging a standard installer, you are not likely to run into any issues here. Hopefully you're customer's aren't playing with ResHack, otherwise, nothing to worry about.

I've not run into any issues yet but I haven't run the tool at scale yet.

I was just hoping to get ahead of any issues before sending an app through the tool.

I'm already checking the headers to look for the kernel drivers, printer drivers,16bit files (on x64 OSs) etc. that are unsupported by MSIX.  Was hoping for a list of anything else I may have missed.