Details of the scenario you tried and the problem that is occurring
As a solution to working around the lack of implicit remoting, a few people have reported trying to add modules that are built in to Windows by using the FilesToInclude parameter. Not only is that not supportable, it violates the Windows terms of use.
Suggested solution to the issue
When the path provide to FilesToInclude is under System32, throw an error with a valid description.
“Modules within the System32 folder are provided as built-in for Windows PowerShell.
It is not supportable to add these modules to a package, and it violates the Windows terms of use.”
Details of the scenario you tried and the problem that is occurring
As a solution to working around the lack of implicit remoting, a few people have reported trying to add modules that are built in to Windows by using the FilesToInclude parameter. Not only is that not supportable, it violates the Windows terms of use.
Suggested solution to the issue
When the path provide to FilesToInclude is under System32, throw an error with a valid description.
“Modules within the System32 folder are provided as built-in for Windows PowerShell. It is not supportable to add these modules to a package, and it violates the Windows terms of use.”