Version 1.06.0034

[WalterSobchak9515]

Has this version still not passed smart screen yet??? It's been months.

The MS store version (which I can't use to deploy to machines in my tenant) shows to be the current 1.06.0034. So is it actually already approved and you just haven't updated it on the release page yet?

Thanks!

[WalterSobchak9515]

Any idea when this will be available for production use?

[Weatherlights]

Yes it is. You can easily check this yourself by the way: Simply download the app in Microsoft Edge: When there is a security message showing it is likely that Smartscreen came in the way.

If you deploy the app using Intune you do not need the Smartscreen approval at all since apps installed by an MDM solution bypass Smartscreen.

[WalterSobchak9515]

Yes it is. You can easily check this yourself by the way: Simply download the app in Microsoft Edge: When there is a security message showing it is likely that Smartscreen came in the way.

If you deploy the app using Intune you do not need the Smartscreen approval at all since apps installed by an MDM solution bypass Smartscreen.

Ah, that is good to know, I thought defender smart screen may still block it due to it not being approved. Thank you!!!

[Weatherlights]

Nahhh... it is just an essential prerequisite for the Microsoft Store :) and of course helpfull when you use advanced Defender Features like Defender Application Control.

[fabssnn]

It's a bit annoying that Windows takes so long to release... :/

[WalterSobchak9515]

This is regarding the newest update: 1.06.0036.msi

When I try to replace my older version of this in Intune, I get the following error which prevents me from updating the current app:

The version currently in Intune: 1.06.0021.msi

I realize that I can create a new app using the new MSI, but I guess because the GUID / product code differs, then this blocks me from using it to replace the current version?

[Weatherlights]

Please try another version first. I switched installation technology at one point and it might be that there is no direct update path between 1.06.0021 and 1.06.0036.

[WalterSobchak9515]

Based on the releases you have, there is only one version between and that is 1.06.0034.msi, same result with that msi:

[Weatherlights]

What you can do... but I recommend you to validate this first since I have not tested it: You can create a new app, assign in and exclude the old app (maybe to a single device first). The setup of the new version should handle an inplace upgrade.

[WalterSobchak9515]

Ok, that is what I was doing anyway was testing with a single machine using the original app deployment method just updating the MSI.

I created a new app, assigned a single machine that currently had 1.06.0021 installed. It updated it to 1.06.0036. Seems to be fine, but no application update testing yet using the new version.

Edit: From what I see, it looks like you are working on updating to WAU 2.2.0, is that correct?

[Weatherlights]

Yes there is also one approach that is promising. I will implement that in the beta channel pretty soon. I just do not like the approach since it technically means I am "messing" with the MSI database. But it is one that works and it is feasibly in terms of workload.

Currently I am testing a new approach to avoid the SmartScreen approval which also seems to work so I am flexible again in terms of updates.