Fixing crash issue with Win32 content prep tool

[nikyusof]

• Updating the binaries that fixes the issue with Win32 content prep tool crashing.
• Fixes IntuneWinAppUtil.exe crashes the whole terminal without any error message displayed #108

[scidonem]

This has broken the tool for me, causing it to crash with the below:

INFO   Validating parameters
INFO   Validated parameters within 2 milliseconds
INFO   Removing temporary files
ERROR  System.IO.IOException: The handle is invalid.

   at System.IO.__Error.WinIOError(Int[32] errorCode, String maybeFullPath)
   at System.Console.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)
   at Microsoft.Management.Service.IntuneWinAppUtil.LogUtil.PrintProgress(AppContext context)
   at Microsoft.Management.Service.IntuneWinAppUtil.PackageUtil.CreatePackage(String folder, String setupFile, String outputFolder, String catalogFolder)
   at Microsoft.Management.Service.IntuneWinAppUtil.Program.Main(String[] args)

[nikyusof]

@scidonem would you mind providing these:

• OS version.
• Command line platform (Powershell, CMD, etc.). Provide version as well.
• Command that you ran that encountered this error.

Can you also try the same command on the previous version to see if you are getting the same error or not?

[githubpow]

Hello @nikyusof

With new tool version or the last version, the tool crashes even though I do .\IntuneWinAppUtil.exe -h

OS version: Win11 22H2 (OS build 22621.2506)
Command line platform: Powershell 5.1 build 22621 rev 2506
crashing command lines:
.\IntuneWinAppUtil.exe -h
.\IntuneWinAppUtil.exe -c .\source\ -s .\source\xxx.exe -o .\output\

My workaround is still open the Powershell console maximized. I don't which Windows update caused this issue, I have the latest cumulative update 2023-10 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5031323) installed.

[hh-trj]

@nikyusof It's crashing for me, as well. The previous version is also crashing. Having PowerShell maximized fixes the issue.

OS version - Windows 11 23H2 (22631.2428)
Command line platform (Powershell, CMD, etc.). Provide version as well - PowerShell 5.1.22621.2428
Command that you ran that encountered this error:

& "$($env:USERPROFILE)\IntuneWinAppUtil.exe" -c "$($env:USERPROFILE)\source\repos\intunewin-microsoft-winget\src" -s "Install-App.ps1" -o "$($env:USERPROFILE)\source\repos\intunewin-microsoft-winget\dist"

[Joly0]

For me this is working, but why wasnt there a new release or anything? The Binary go swapped, but nothing else. No additional information or anything?

[scidonem]

@scidonem would you mind providing these:

• OS version.
• Command line platform (Powershell, CMD, etc.). Provide version as well.
• Command that you ran that encountered this error.

Can you also try the same command on the previous version to see if you are getting the same error or not?

OS version Windows Server 2022
Running in PowerShell via WinRM with no GUI (runs as part of GitHub workflow)

Command runs fine in previous version so have pinned that version in the workflow for now.

              ."${{ github.workspace }}/intune/util/Microsoft-Win32-Content-Prep-Tool/IntuneWinAppUtil.exe" -q -c "$($_.FullName)" -s "Deploy-Application.exe" -o "${{ github.workspace }}/intune/output"

[DanoThom]

This change has caused the prep tool to fail for me in Azure DevOps pipelines in a powershell task with the same 'handle' error:
ERROR System.IO.IOException: The handle is invalid

Anyone aware of a workaround for this in a similar headless environment?

EDIT: Pinning to version 1.8.4 of the tool now works in the pipeline.

[scidonem]

Yes. use the previous version Same problem here in a GitHub pipeline. That'll teach me for checkout the latest source every time and not pinning a release tag 😃

…

________________________________ From: Dan ***@***.***> Sent: Tuesday, November 7, 2023 6:54:52 PM To: microsoft/Microsoft-Win32-Content-Prep-Tool ***@***.***> Cc: Michael Scidone ***@***.***>; Mention ***@***.***> Subject: Re: [microsoft/Microsoft-Win32-Content-Prep-Tool] Fixing crash issue with Win32 content prep tool (PR #109) This change has caused the prep tool to fail for me in Azure DevOps pipelines in a powershell task with the same 'handle' error: ERROR System. IO. IOException: The handle is invalid Anyone aware of a workaround for this in a similar headless This change has caused the prep tool to fail for me in Azure DevOps pipelines in a powershell task with the same 'handle' error: ERROR System.IO.IOException: The handle is invalid Anyone aware of a workaround for this in a similar headless environment? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool/pull/109*issuecomment-1798271372__;Iw!!OVe7agNpIlw!P5gLnI6n4ITx1naw3LR-9pJ50cUxFmS28BIpdTkV25qUd-fnjwy_kSk5DRNwLMeoa4IeXxsibJKQ6LkYziqNPVqlaSn-QA$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AXTJY26ESOFQ2HPO5GBV53DYDIHPZAVCNFSM6AAAAAA63OKYR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJYGI3TCMZXGI__;!!OVe7agNpIlw!P5gLnI6n4ITx1naw3LR-9pJ50cUxFmS28BIpdTkV25qUd-fnjwy_kSk5DRNwLMeoa4IeXxsibJKQ6LkYziqNPVpjhBvrzg$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[stutf]

I also confirm this bug - mine always crashed at 61 or 62 percent.
I tried both v1.8.4 and v1.8.5 with same issue.
I tried both Powershell and CMD with same issue, both inside the 'Windows Terminal'
Maximizing the window fixes the crash in both Powershell and CMD, both inside 'Windows Terminal'
I'm running W11 23H2.

[MattKeenSA]

Maximizing the window fixes the crash in both Powershell and CMD, both inside 'Windows Terminal' I'm running W11 23H2.

I can confirm this works for me too, Maximised Terminal/CMD window allow the process to run and create the package.