Install-Printer.ps1 Suddenly not working

[JustoStyle]

Have deployed many of printers with this script but myself and anther coleege are having a issue with the script now where it produces this in the log file

##################################
<time="15:29:04.648 570" date="06-28-2024">
##################################
Install Printer using the following values...
Port Name: IP_10.86.1.53
Printer IP: 10.86.1.53
Printer Name: Unley - Sharp MX-3070V
Driver Name: SHARP MX-3070V PCL6
INF File: su0emenu.inf
<Staging Driver to Windows Driver Store using INF "su0emenu.inf"> <time="15:29:04.827 570" date="06-28-2024">
<Running command: Start-Process pnputil.exe -ArgumentList /add-driver su0emenu.inf -wait -passthru> <time="15:29:04.849 570" date="06-28-2024">
<time="15:29:04.970 570" date="06-28-2024">
<System.InvalidOperationException: This command cannot be run due to the error: The system cannot find the file specified.
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)> <time="15:29:04.995 570" date="06-28-2024">
<time="15:29:05.079 570" date="06-28-2024">

and this in the event log.

It seems that the install cant find the INF file but i have checked and even decrypted the intunewin to check and the file is in there. Anyone else seen this it seems like an issue with intune deployment in general but posting there to see if anyone is able to assist.

Thank you,
J

[krilumino]

What is the path of the .inf file, relative to the directory where install-printer.ps1 (or pnputil) is being called from?

[JustoStyle]

Everything is in the root of the intunewim.

[JustoStyle]

Running the script in its folder that gets packed into the wim. Runs fine the only thing i have noticed has started happening is it being up a box to trust the pusblisher of then driver.

Something seems to have change as if i upload a know working intunewim it no longer works and throws the cant find file path error above.

So maybe its something with how the intunewim is getting unpacked for new intunewims only.

[sebastianbinder]

Is this topic still unsolved for you? Did you find any solution or a working modification for the script? Experiencing the same error.

[krilumino]

Rewriting my comment from earlier. As shown in OP's log...

<Running command: Start-Process pnputil.exe -ArgumentList /add-driver su0emenu.inf -wait -passthru> <time="15:29:04.849 570" date="06-28-2024">
<time="15:29:04.970 570" date="06-28-2024">
<System.InvalidOperationException: This command cannot be run due to the error: The system cannot find the file specified.

This error is generated by start-process when it cannot find the file path, in this case "pnputil.exe". This notoriously can happen if powershell x86 is running on a x64 host. Do you know if the script is being run in x86 powershell?

Install-Printer.ps1 is supposed to check for this, and try to run the script in the correct architecture:
If ($ENV:PROCESSOR_ARCHITEW6432 -eq "AMD64") { Try { &"$ENV:WINDIR\SysNative\WindowsPowershell\v1.0\PowerShell.exe" -File $PSCOMMANDPATH #... }

However, the problem to me seems that when this x64 call returns, the full script still tries to run in the powershell x86.
You can try adding an exit command after it calls powershell x64. See what the log looks like then.
You could also try to run the script natively on the server/endpoint in both powershell x86 and x64 and see if the results/symptoms are the same.
Do you know if your initial PS is running in x86 context? Can you try to have it run in x64 instead?
I don't necessarily expect this to resolve the issue, but it could help eliminate a potential false positive.