# Launch SMS window by default? **URL:** \ **Category:** Help\ **Tags:** kdeconnect\ **Created:** [September 5, 2026, 3:11am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951 "2026-09-05T03:11:14Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 5, 2026, 3:11am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/1 "2026-09-05T03:11:14Z")
KDEconnect 26.04.2 on Windows 11 Is there a way to open the SMS window by default or maybe create a shortcut directly to it? That would be much easier than having to right-click the systray icon, then navigate the context menu to find and open it. Thanks. ---
**Author:** ![smash](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/smash/32/32638_2.png) [@smash](https://discuss.kde.org/u/smash)\ **Post date:** [September 5, 2026, 5:03am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/2 "2026-09-05T05:03:35Z")
KDE Connect has a dedicated `kdeconnect-sms` app. It likely has a launcher on your system already but if it doesn’t you can launch it with `kdeconnect-sms` and assign a keyboard shortcut if you like. ---
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 5, 2026, 11:22am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/3 "2026-09-05T11:22:42Z")
kdeconnect-sms is there, but no shortcut. Since the app is managed by the Windows Store it’s sandboxed and I therefore have no direct access to the installation directory (at least in a terminal, even though my account is a local admin). I tried running it from an admin terminal last night but still got “access denied”. kdeconnect-cli can be run but not \*-sms. I’ll see if somehow I can create a shortcut to \*-sms from my userspace. It would be really nice if a standard installer was available instead of that accursed MSIX version. I really hate MS Store packaging. They’re a pain in the neck to deal with. ---
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 5, 2026, 12:34pm UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/4 "2026-09-05T12:34:23Z")
I just created a shortcut to `kdeconnect-sms.exe` (in an admin PowerShell session) – `powershell -Command "$s=(New-Object -COM WScript.Shell).CreateShortcut('C:\ProgramData\Microsoft\Windows\Start Menu\Programs\KDEconnect SMS.lnk'); $s.TargetPath='C:\Program Files\WindowsApps\KDEe.V.KDEConnect_26.402.6289.0_x64__7vt06qxq7ptv8\bin\kdeconnect-sms.exe'; $s.Save()"` But it still won’t launch. Trying directly from the directory (in an admin terminal) gets this – `C:\Program Files\WindowsApps\KDEe.V.KDEConnect_26.402.6289.0_x64__7vt06qxq7ptv8\bin>kdeconnect-sms.exe` `Access is denied.` I don’t know if that’s a result of the app being delivered by MSIX or it’s inherent. But without a standard installer it’s impossible to test. ---
**Author:** ![smash](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/smash/32/32638_2.png) [@smash](https://discuss.kde.org/u/smash)\ **Post date:** [September 6, 2026, 3:13am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/5 "2026-09-06T03:13:02Z")
> [@lphilpot](#): > > It would be really nice if a standard installer was available instead of that accursed MSIX version There is an exe version on the KDEConnect website: [Download | KDE Connect](https://kdeconnect.kde.org/download.html) ---
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 6, 2026, 3:24am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/6 "2026-09-06T03:24:50Z")
> [@smash](#): > > There is an exe version on the KDEConnect website Whatever path I took to the Store version didn’t mention anything about other formats. I assume I can safely uninstall the MSIX, install the MSI and pick up where I left off (config will remain untouched)? Thanks. ---
**Author:** ![smash](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/smash/32/32638_2.png) [@smash](https://discuss.kde.org/u/smash)\ **Post date:** [September 6, 2026, 3:28am UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/7 "2026-09-06T03:28:19Z")
I don’t use windows so can’t confirm, but that would be my expectation. Uninstallation _shouldn’t_ touch user configuration files. It definitely doesn’t in Linux. ---
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 7, 2026, 6:19pm UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/8 "2026-09-07T18:19:02Z")
That would’ve been my expectation as well, but alas – The config laid down by the sandboxed / MS Store version is completely ignored by the MSI version. A quick cursory comparison of the two doesn’t reveal too many similarities. Maybe after fully (manually) configuring both versions they would be more similar but at that point, what’s the point in copying the config items between them? I really detest MS Store apps. Just a dumb idea from the outset, obviously designed to offload ever more of the user’s control over their computer to Microsoft. I’m disappointed the KDE Connect developers even considered, much less implemented and offered, the app packaged as an MSIX. ---
**Author:** ![lphilpot](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/lphilpot/32/36262_2.png) [@lphilpot](https://discuss.kde.org/u/lphilpot)\ **Post date:** [September 7, 2026, 7:02pm UTC](https://discuss.kde.org/t/launch-sms-window-by-default/49951/9 "2026-09-07T19:02:44Z")
**Update** – At first the reinstalled (MSI) app didn’t see my phone nor any of my existing settings. But when I came back ~45 minutes later it saw (but didn’t trust) my phone and had some of my settings. I was able to re-pair the phone but will have to reconfigure my settings.