The Microsoft Store integration in Intune allows admins to deploy and manage UWP and Win32 apps directly from the store. While this makes apps like Adobe Creative Cloud easy to install, some have begun facing unexpected errors that disrupt workflows. Let’s explore the issue and a practical workaround using WinTuner.
Adobe Creative Cloud Missing Latest Package Version
The new Microsoft Store seems like an obvious choice when dealing with Adobe Creative Cloud distributions. The idea is simple: Browse for an app and deploy it. This is described in the following Microsoft documentation: Add Microsoft Store apps to Microsoft Intune | Microsoft Learn
Adobe Inc. has published its apps for ease of installation, which has worked well. Still, recently, it has failed with an error message, as seen in the animation above: “The selected app does not have a valid latest package version.”
The root cause of this seems to be unknown version information for the version available in store.
As seen in the image above, a WinGet search for “Adobe Creative” shows that the application is available through both msstore and winget, where the msstore version is missing version information.
WinTuner To The Rescue
With Adobe Creative Cloud’s distribution broken, I was looking for an easy way to package and prepare the application. Popular third-party solutions like Patch My PC and Scappman do not have Adobe Create Cloud in their catalogs.
This made me think of WinTuner, a tool from MVP Stephan van Rooij that packages any app from Winget to Intune. Now is the time to look deeper into this open-source product.
Installation of WinTuner
The installation of WinTuner requires PowerShell 7. If you don’t have that already, you can easily get PowerShell 7 from Microsoft: Installing PowerShell on Windows – PowerShell | Microsoft Learn
The Wintuner installation is available both in CLI and PowerShell versions. I run with the PowerShell variant, and the installation itself is easily done.
Install-Module -Name WinTuner
Import-Module WinTunerUse WinTuner To Search For Applications
Once the module is installed, I can search for WinGet packages.
Search-WtWinGetPackage Adobe.CreativeCloud
The search returns the following result.
I need the PackageId to create a package.
Use WinTuner To Create The Package
I will now use the New-WtWinGetPackage command to create a package of the application from WinGet.
New-WtWingetPackage -PackageId Adobe.CreativeCloud -PackageFolder c:\Temp\AppsThis command runs fast and creates the following output.
The following content is created in the specified folder
The app icon is created in the root folder for the application, next to the versioning folder.
Use WinTuner To Deploy The WinGet Win32 Package
Before deploying the package, I like to connect to the tenant. Adding “-test” to the connect command will try to get a token immediately. Otherwise, it will get a token the first time it connects to the graph. This will open a web browser to authenticate and consent to the rights.
With the connection, it’s time to deploy the Win32 app using WinTuner.
Connect-WtWinTuner -Username "simon.skotheimsvik@XXXXXXX.onmicrosoft.com" -Test
Deploy-WtWin32App -PackageFolder "C:\Temp\Apps\Adobe.CreativeCloud\6.3.0.207"The deployment gives the following result in PowerShell.
The app is now available in Intune. I like the informative Notes section that describes its origin.
The app should now be available in the Company Portal.
End users can now serve themselves despite initial challenges of adding it using the Microsoft Store.
WinTuner Wrap up
To sum up my experience with WinTuner, it truly came through for me when managing Adobe Creative Cloud challenges using Microsoft Store for Microsoft Intune. The platform’s comprehensive online documentation made it quick and easy to get up and running.
While I haven’t explored every feature in-depth, I can confidently say that WinTuner delivers excellent value for its price range. And the best part? It’s open-source and completely free!
Tnx for this post.
Does the apps auto update?
Hi Rob K, Thanks for the feedback on my post. This is what keeps us going on sharing content with the community 🙏
The WinGet apps do not update by themself once distributed to the endpoints.
There are however a way to update all apps you pushed this way with some commands. This could typically be handled by a remediation script. I haven’t blogged about this yet, but I might do it as a follow up to this post😉