Add-IntuneWin32App.ps1 'CommitFile' failed error with PowerShell 7.4.0

[jaspain]

Using PowerShell 7.40, Microsoft.Graph 2.91, IntuneWinAppUtil.exe 1.85, and IntuneWin32App 1.42, Add-Intunewin32App.ps1 generates the warnings:

WARNING: Intune service request for operation 'CommitFile' failed
WARNING: Failed to create Win32 app, commit file request operation failed

The intunewin file upload fails. Using PowerShell 7.39 instead of 7.40 along with the same versions of the other components, the upload succeeds. See Add-IntuneWin32App.ps1, line 621.

[jaspain]

Looking at this further, the error occurs in Add-Intunewin32App.ps1, line 617. The request to commit the uploaded content returns a commitFileFailed response with PowerShell 7.4.0, commitFileSuccess with PowerShell 7.3.9.

I created a simplified test environment by excerpting the code and data needed to create a 7-Zip Intune app DebugAddingIntuneWin32App.zip. Here the error occurs at Test-AddingIntuneWin32App.ps1, line 449, with PowerShell 7.4.0. The 7-Zip Intune app is successfully created with PowerShell 7.3.9. To run the test environment, install the desired version of PowerShell 7, along with modules Microsoft.Graph 2.91, IntuneWin32App 1.42, and MSAL.PS 4.37.0.0. Connect-MSIntuneGraph to your tenant, and execute Test-AddingIntuneWin32App.ps1.

Verbose output of the test environment is included in the zip file: Test-AddingIntuneWin32App v7.3.9 Output.txt and Test-AddingIntuneWin32App v7.4.0 Output.txt. Comparing these two files, one difference that stands out is in line 19 of both files where the content encoding is iso-8859-1 for v7.3.9 and utf-8 with 7.40. The payload sizes in line 15 are different as well. It's not clear what's going on here, but note that the Invoke-AzureStorageBlobUploadChunk function in Test-AddingIntuneWin32App.ps1, line 214, specifies iso-8859-1 encoding. This bears further investigation.

[jaspain]

I think the problem is with Invoke-WebRequest in function Invoke-AzureStorageBlobUploadChunk (see PowerShell\Modules\IntuneWin32App\1.4.2\Private\Invoke-AzureStorageBlobUploadChunk.ps1, line 43). The documetation Invoke-WebRequest states in the Description section "Beginning in PowerShell 7.4, character encoding for requests defaults to UTF-8 instead of ASCII. If you need a different encoding, you must set the charset attribute in the Content-Type header."

[jaspain]

Ok. That's the problem. Here's the proposed fix: PowerShell\Modules\IntuneWin32App\1.4.2\Private\Invoke-AzureStorageBlobUploadChunk.ps1, insert after line 38:
"content-type" = "text/plain; charset=iso-8859-1"

The definition of $Headers becomes:

	$Headers = @{
		"content-type" = "text/plain; charset=iso-8859-1"
		"x-ms-blob-type" = "BlockBlob"
	}

This should work in PowerShell 5, where the ContentType parameter of PowerShell 7's Invoke-WebRequest isn't implemented. I tested it and confirmed that it works in PowerShell 7.39, where this is the default content type anyway, and in PowerShell 7.40, where this content type needs to be explicitly set to override the default utf-8.

[fabrisodotps1]

I can confirm this behavior and the suggested fix also works. Thank you for the detailed analysis @jaspain

[MarkMae]

@jaspain Top! Thank you for the work! 👍

[jaspain]

Remains an issue in v1.4.3.

[NickolajA]

Excellent analysis @jaspain, thank you! I'll have this fixed in 1.4.4.

[jaspain]

Thank you, @NickolajA. Jeff.

[abidkayanimoj]

Thank you, @jaspain. I ended up with this error last week and finally a colleague of mine found your article and pass it to me. it works.