Most robust, as it respects Shell links and special folder redirection.
Remove-Item -Path "C:\Users\User\Desktop\MyApp.lnk:Zone.Identifier" -Force Not recommended for untrusted sources. Windows 11 promotes MSIX packaging. A packaged app does not have a direct .exe path. Instead, its shortcut uses an AppUserModelID (AUMID) .
# Find AUMID Get-StartApps | Where-Object $_.Name -like "*MyApp*" $shortcut.TargetPath = "shell:AppsFolder\Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" $shortcut.Save() how to add app to desktop windows 11
// Simplified COM call chain CoCreateInstance(CLSID_ShellLink, NULL, CLSCTX_INPROC_SERVER, IID_IShellLink, &pShellLink); pShellLink->SetPath(L"C:\\Program Files\\App\\app.exe"); pShellLink->SetDescription(L"Launch App"); IPersistFile* pPersistFile; pShellLink->QueryInterface(IID_IPersistFile, &pPersistFile); pPersistFile->Save(L"C:\\Users\\User\\Desktop\\App.lnk", TRUE); If OneDrive Known Folder Move is active, the desktop path redirects to C:\Users\<User>\OneDrive\Desktop . The Shell abstracts this via the CSIDL_DESKTOP (0x0000) or FOLDERID_Desktop . 3. Method 2: Programmatic Deployment (PowerShell / CMD) For IT administration, scripting is preferred. Windows 11 introduces no breaking changes to these methods.
When added programmatically, Windows may add an Zone.Identifier alternate data stream (ADS). To suppress SmartScreen warnings: Most robust, as it respects Shell links and
Create (or Update for persistent refresh)
A desktop shortcut to a RemoteApp is a .rdp file with remoteapplicationmode:i:1 and remoteapplicationprogram:s:AppAlias . A packaged app does not have a direct
Starting with build 22000, packaged apps launched via desktop shortcut use the new Undocked Taskbar integration; the shortcut invokes ApplicationFrameHost.exe as broker. 5. Method 4: RemoteApps (RDS / Azure Virtual Desktop) For enterprise VDI environments, RemoteApps are published via .rdp files or MSRDC (Microsoft Remote Desktop Client) .