MicrosoftStoreAppUpdater script

A simple way to update Microsoft Store Apps This script will inititae update for Microsoft Store Apps and applications available using winget.By default it will delete the logfile if older then 30 days. Should run with local administrative rights or as system When deploying new computers, there might be modern apps without processed updates.Can also update on regular machines in use. Works with Windows 365 Deployments and regular OSD using ConfigMgr/MDT

Automate Configuration Manager Application Creation

A simple script example to automate the application creation process in ConfigMgr or Configuration Manager. RebootBehavior set to NoAction, Accepted values: BasedOnExitCode, NoAction, ForceReboot, ProgramRebootAutoInstall $true – indicates whether a task sequence action can install the applicationAdded Action to Distribute the Content to the DP Group at the end Configuration Manager Checklist:

New Microsoft Edge based on Chromium – error status: 1603

I recently ran into to an issue deploying the New Microsoft Edge, for some reason it kept failing with Error status 1603 on most of the systems. The deployment version was version: 87.0.664.47It kept failing on a lot of systems with build: 1803. I did suspect a missing KB of some kind. However, I did not find any apparent prerequisites missing. Tried the same method for the latest version – 87.0.664.60. Both downloaded from: and everything seemed to be working. It’s now deployed to more then 2000 systems. Any ideas, other then deploying latest and greatest? Let me know.

Deploy Microsoft Edge Chromium Using PowerShell App Deployment Toolkit (PSADT)

The new Microsoft Edge is based on Chromium and was released on January 15, 2020. It is compatible with all supported versions of Windows. Installing the browser will replace the legacy version of Microsoft Edge on Windows 10. Deploy Microsoft Edge Chromium using the PowerShell App Deployment Toolkit. PowerShell App Deployment Toolkit (PSADT) is a great framework to deploy and manage application deployment. It is free of charge. Additionally, it is downloadable from The published script is here on Github Deploy Microsoft Edge This deployment script example does the following within the PSADT framework: Pre-Install:If Microsoft Edge is open, it … Continue reading

MSiX Insider Preview Build 1.2019.522.0

First insider preview release for the upcoming public release in July. New Features: Support for desktop installers that require restart – read more Auto-login option for restart New options in app settings Specify a default cert to sign packages with Specify exit codes for installers that require restart Known “bugs/features” Negative reboot exit codes are currently not supported If Default cert is specified, you still need to select to sign your package During remote or VM restarts, there might be an extra login prompt Restore defaults button doesn’t remove certificate password or installer exit codes There are some UI incongruencies … Continue reading

List Packages that run in user context (Run with user’s rights)

Introduction After last weeks post with the script sample to list Packages that run in user context, there where some good feedback from people still using packages, and requiring a list of packages that install within the user context (Run with user’s rights / Execution mode as user) It seemed that many was still using Packages, either as a result of legacy migration or to avoid some application re-packaging. So here is the followup post, with a new script to list all packages and package with programs that run in user context. From my point of view, its still the … Continue reading

List Applications that run in user context (Install for User)

Introduction When deploying applications sometimes they are created to install within the active users context. This means that the actual installation requires the users to have the needed permissions to the filesystem, registry and etc. In some cases local administrative rights are needed to perform the application installation, this is not a good practice. As applications mature for the modern design of the Windows Operating System or we choose to remove the users administrative rights due to security reasons, we may need to list and change the behavior of existing Applications. This script was created to list applications that is … Continue reading

Cleaning up shortcuts

So the issue at hand;I was replacing a Office application on Windows systems, where i noticed that shortcuts created by the users, was not upgraded/removed when the new office version was installed. The issue seems to be related to users creating custom shortcuts, directly to exe files.I some cases the shortcut name was clear, but in other cases the users had chosen something they found fit. The following PowerShell script was created to remove shortcuts (lnk files) based on the executable. This means you can specific the exe or use a wildcard if there is multiple executable files releated to … Continue reading

MSiX – Remote machine conversions

The MSiX Packaging Tool (1.2019.226.0) Preview now has the ability to connect to a remote machine, where you can run the conversion.This is great news, and solves the normal issue with contamination on “non-sanitised” machines. I have always preferred to do my packaging and re-packaging on Hyper-V Virtual Machines This gives a total control and clean enviroment, with easy ability to get back to a controlled point of reference, using checkpoints. Getting started with remote machine conversions? Fear not! It is quite simple to get started. – PowerShell remoting must be enabled for secure access to the remote machine.– You … Continue reading