WIndows 11 ical file

Started with a new healthcare provider. Their booking system sends out calendar files using the ‘ical’ extension. If I save the file, edit it to resave it under ‘.ics’ it opens correctly as a calendar file. But windows 11 is frustrating my half-hearted attempts to just introduce it to the idea that this is an ics file. Any way of humoring emclient to recognize it? Am getting lazy about editing the registry in my old age.

martes 10 marzo 2026 :: 1709hrs (UTC +0100)

Hey @glatiak

The following works for me in Windows & MacOS

To “Convert” or Use .ical Files:
Rename File Extension:
In Windows Explorer or macOS Finder…
Right-Click the file, choose “Rename,” and change the .ical extension to .ics.

You can Double Click the .ics file to create an entry in eMC

skybat

¡Buena suerte!

¡Saludos desde Sevilla la soleada en España!
¡Mis mejores deseos y mantente a salvo!

[email protected]

Hablo español, luego portugués, inglés, francés y alemán
con conocimiento de varios otros idiomas.

1 Like

Thanks. That is effectively what I ended up doing but it makes an unnecessary extra step when the file is attached to an email. I want to be able to open it without that extra step but emclient is not in the ‘open with’ list that w11 provides. Thankfully I dont get many of these but would be nice to not do a multistep workaround.

martes 10 marzo 2026 :: 2001hrs (UTC +0100)

Hey @glatiak

In Windows 11 go to:
Apps >Default Apps >Choose default by file type
Search for .ics then select eM Client to make it default

skybat

¡Buena suerte!

¡Saludos desde Sevilla la soleada en España!
¡Mis mejores deseos y mantente a salvo!

[email protected]

Hablo español, luego portugués, inglés, francés y alemán
con conocimiento de varios otros idiomas.

Thanks, but the problem was not a failure to recognize an ics file but that the scheduling vendor tagged the file as an ‘ical’ file. With prior versions of windoze there was an extension list accessible to mortals where one could add a file extension and association. But w11 moved that into the registry. I have done a lot of work inside the registry over the years, but think this issue is more than a poor little me problem.