Developers found a way to break or opt out from Microsoft Store Web installers if forced on their apps

Microsoft just announced they are experimenting with a new Microsoft Store web installer for apps, where the download and install experience will be improved when users download apps from the Microsoft Store website.

However, Rafael Rivera, who made the app Ear Trumpet, wasn’t happy with Microsoft. He said on X  that Microsoft is using a new method to package apps that he thinks look suspicious and collect too much data. He also mentioned that Microsoft is not using the version of .NET he designed his app for.

The Microsoft Store team has started quietly wrapping apps, like EarTrumpet, with some malware-looking .NET executable wrapper (with my app's name of course) chock full of telemetry and other code. They also target netfx 4.7.2 when my app targets netfx 4.6.2, wtf? pic.twitter.com/oQFIz0G2lE

— Rafael Rivera (@WithinRafael) April 20, 2024

Even though Microsoft said the new method was optional, Rivera felt it was forced on him without his choice.

Well, it turns out that all this is a misunderstanding. Rudy Huyn explained how developers can avoid using the new installer by changing a setting in their app’s code.

Very good question. Developers can choose how they want their badge to behave. Only badges with launchMode=direct will use the new Store installer for the web. pic.twitter.com/kwhn7vfw6A

— Rudy Huyn (@RudyHuyn) April 21, 2024

Rivera later found out from Microsoft’s website that if developers don’t specify a certain setting, their apps will automatically use the new download method. He suggesteed a way for developers to make sure they’re not using the new installer if they don’t want to:

To opt-out, ?mode=mini or ?mode=full must be added to your app URIs/badges. No mode or ?mode=direct will currently send you down this EXE path.

Rivera also mentioned another unofficial method to interfere with the new installers, involving placing certain files in a specific folder.

You can plant a few of your favorite DLLs into Downloads and bounce off those shiny new Microsoft Store installers 👍

ncrypt.dll, cryptsp.dll, cryptbase.dll, bcrypt.dll, msvcp140_clr0400.dll, profapi.dll, enStoreInstaller.resources.dll, d3d9.dll, etc. pic.twitter.com/aAdjb98L3M

— Rafael Rivera (@WithinRafael) April 22, 2024

It’s not clear if Rivera was the only one affected by this change or if other developers were too, but you should check if your app is in perfect order. Also, now you know how to opt out of the new web download mode and how to get your DLL files in.

Have you had any similar experience with the Store web installer? Let’s talk about that in the comments section below.