[ Back to all articles ](https://addcal.co/blog.md) outlook new outlook ics troubleshooting ICS Not Working in New Outlook? Why, and the Fix ================================================ By Tom •October 9, 2026 You double-click an .ics file and new Outlook does nothing. Or Outlook opens, tells you the import worked, and the event is nowhere. Or you get "Something went wrong. You may want to try again." or, since mid 2025, "The operation failed." Classic Outlook opened the same file in one click, every time, for as long as anyone can remember. Two different things are going on, and the fix depends on which one you've got. This post covers how to tell new Outlook from classic, the import dialog that opens where you cannot see it, the four things in a file that new Outlook rejects and classic quietly accepted, how to read the file to tell which, and the fix for each, whether you are the one importing or the one sending. First: which Outlook are you in? -------------------------------- New Outlook for Windows is the one with a "New Outlook" toggle in the top right and no File menu. It is Outlook on the web in a window, and its calendar behaves like Outlook.com. Classic Outlook has the File menu and the ribbon. Both can be installed at once, and that is where the first confusion comes from: switching to new Outlook does not move the .ics file association with it. Right-click a file, choose Open with, and Windows lists two entries called Outlook with the same icon, one for each. A fair few people in the [Microsoft Q&A thread on this](https://learn.microsoft.com/en-us/answers/a/12174640) were picking the wrong one for months without knowing there were two. Everything below is about new Outlook. If classic opens the file and shows you the event, the file's fine and you can stop reading. Problem one: the import dialog is open, you just cannot see it -------------------------------------------------------------- Double-click an .ics file with new Outlook as the default and this is what happens: Outlook loads the file into an import dialog inside the Calendar module, and doesn't switch you to Calendar. Mail stays on screen. Nothing changes. The dialog is sitting there waiting for you to pick a calendar, behind a tab you aren't looking at. This has been the top-voted explanation on the Microsoft Q&A thread since August 2025: "When you double click on an .ics file, the new Outlook will not show anything. You need to select the calendar tab, and only then you'll see the event import dialog." A second report in October 2025 put it as the focus not being set to Calendar. Several people on the same thread say the dialog shows up roughly three times in ten, which is about what you'd expect if it depends on which module happened to be open when you clicked. The fix, if the file itself is fine: 1. Double-click the file, then click the **Calendar** icon in the left rail. An "Add calendar" dialog should be open on the **Upload from file** page with your file already loaded. 2. Open the **Select a calendar** dropdown and pick one. New Outlook will not pick it for you, even if you only have one. 3. Click **Import**. The dialog does not always confirm anything. Go to the event's date to check it landed. If no dialog is waiting, start it yourself. Microsoft's own steps for [importing a calendar in Outlook.com](https://support.microsoft.com/en-us/office/import-or-subscribe-to-a-calendar-in-outlook-com-cff1429c-5af6-41ec-a5b4-74f2c278e98c) are the same in new Outlook: Calendar, **Add calendar**, **Upload from file**, **Browse** to the .ics, choose the destination calendar, **Import**. Dragging the file onto the calendar view opens the same dialog. If Add calendar only offers "From Address Book" and "From Internet", you are in classic Outlook, and classic opens .ics files by double-click anyway. There's one more route that works when the others refuse, and it's the one that kept coming up across two years of that thread: email. An .ics attached to a message gets a dropdown on the attachment with **Add to calendar**, and that path handles files from outside your organisation that the file-based import turns down. If the file's on your disk, attach it to a draft to yourself, send it, and use the dropdown on the copy in your inbox. Problem two: new Outlook rejects the file ----------------------------------------- If the dialog appears, you click Import, and you get "Something went wrong" or a success message with no event, the file has something in it that classic tolerated and new Outlook doesn't. Classic Outlook has always been forgiving about what it accepts. New Outlook uses the Outlook.com parser, which is stricter in four ways we know of. ### 1. The file is not UTF-8 The oldest report is from [March 2024](https://learn.microsoft.com/en-us/answers/a/9480261): import reports success, calendar stays empty, every file, every method. An administrator traced it a month later to files written by an old ASP Mail system in UTF-16 Little Endian, which classic Outlook had been reading without complaint for years. New Outlook accepts the upload and imports nothing. Open the file in Notepad++ or VS Code and look at the encoding in the status bar. If it is anything other than UTF-8, convert it, save, import again. The administrator's own note: this was never a problem until the upgrade, which is why nobody suspected the files. ### 2. It is a meeting request, not an event An .ics file can carry a `METHOD` line at the top. `METHOD:PUBLISH` means "here is an event, add it". `METHOD:REQUEST` means "here is a meeting invitation from an organiser to you", and the [iTIP standard](https://datatracker.ietf.org/doc/html/rfc5546#section-3.2.2) expects it to arrive by email with an ORGANIZER and ATTENDEE list so the client can reply. Classic Outlook opened a REQUEST file from disk as a plain appointment. New Outlook hands it to the invitation flow, which has no message to reply to, and fails. A December 2025 report on the Q&A thread fixed a batch of these by opening each file in Notepad and deleting the word REQUEST. The proper fix is on the sender's side: PUBLISH, or no METHOD line at all. ### 3. There is no UID Every VEVENT must have a `UID` line ([RFC 5545, section 3.8.4.7](https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.4.7)). Classic Outlook made one up when it was missing, and new Outlook won't. The same December 2025 report lists missing UIDs as the other cause in the batch. Hand-written files and old CRM email templates are the usual source. Add a UID and a DTSTAMP to the event and it imports. ### 4. Property order, and the location field This is the newest one and the least documented. In October 2025, the maintainer of Agical, a widely used .ics generator for Marketo, reported on the [Adobe community](https://experienceleaguecommunities.adobe.com/marketo-27/issue-with-ics-calendar-file-in-new-outlook-anyone-else-185553) that new Outlook wants the properties in a particular order the spec does not require, and that the location field stays blank unless the file carries a Microsoft-only property, `X-MICROSOFT-LOCATIONSOURCE`. Agical was patched on 15 October. The exact order wasn't published and we haven't been able to confirm it independently, so we're flagging it without being able to tell you what the order is. What we can say is that every file we've seen import cleanly puts VERSION and PRODID straight after BEGIN:VCALENDAR, any VTIMEZONE blocks before the first VEVENT, and UID and DTSTAMP at the top of the event. Files from current libraries already look like that. Hand-built and templated ones often don't, and this is the one fault you can't reliably fix in Notepad. Regenerate the file. How to tell which one you have: read the file --------------------------------------------- An .ics file is plain text. Open it in a text editor, or paste it into the [ICS viewer](https://addcal.co/tools/ics-viewer.md), which parses it and shows each event with its fields, and check in this order: - Check the encoding first. Anything other than UTF-8 is fault 1. - Look for a `METHOD:` line near the top. If it says REQUEST, that's fault 2. - Each VEVENT needs a `UID:` line. No UID, fault 3. - Then the first three lines. They should be BEGIN:VCALENDAR, VERSION and PRODID, with any VTIMEZONE before the first VEVENT. Anything else points at fault 4. - And make sure it's an .ics at all. If what you downloaded is HTML, the link redirected you to a sign-in or error page instead of a calendar file. Since October 2025 Outlook's own shared-calendar .ics links have been doing this for some people, returning a 302 to an Outlook error page, and the import then fails with "The operation failed." There's no file to fix in that case. If the viewer parses the file with every field present and new Outlook still rejects it, you are in fault 4 territory and the fix belongs to whoever generated it. The fix if you are sending -------------------------- You can't fix the hidden dialog from your end, but you can make the rejected-file problem go away entirely. 1. **Write UTF-8, no byte order mark, CRLF line endings.** If your generator has an encoding setting, this is the one to check first. 2. **Leave METHOD out, or use PUBLISH.** REQUEST is for invitations sent by email with attendees. An "add to calendar" file is not one. 3. **Every event gets a UID and a DTSTAMP.** Generate the UID once per event and keep it stable, so a re-download updates the entry instead of duplicating it. 4. **Keep the order conventional.** VERSION and PRODID first, VTIMEZONE above the events, UID and DTSTAMP at the top of each VEVENT, and a LOCATION line when there is a location. 5. **Do not put a calendar name in a single-event file.** Outlook treats a file carrying `X-WR-CALNAME` as a new calendar to create ([MS-STANOICAL](https://learn.microsoft.com/en-us/openspecs/exchange_standards/ms-stanoical/)), so your one event lands in a calendar of its own. Apple Calendar wants the name. Outlook does not. 6. **Offer Outlook.com and Office 365 links alongside the file.** These open the web calendar with the event pre-filled and no file in between, so there is nothing for the parser to reject and no dialog to hide. On a Windows machine running new Outlook, that is the path with the fewest moving parts. 7. **Test in new Outlook, classic Outlook and Outlook on the web.** They're three parsers sharing one name, and a file that's fine in two of them can fail in the third. For reference, this is the file AddCal hands to Outlook for a timed event, trimmed to the lines that matter: ``` BEGIN:VCALENDAR VERSION:2.0 PRODID:-//AddCal-1.0//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Australia/Sydney BEGIN:STANDARD DTSTART:20270404T030000 TZOFFSETFROM:+1100 TZOFFSETTO:+1000 END:STANDARD BEGIN:DAYLIGHT DTSTART:20271003T020000 TZOFFSETFROM:+1000 TZOFFSETTO:+1100 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:evt_ab12cd34ef56 DTSTAMP:20261009T215519Z DTSTART;TZID=Australia/Sydney:20270902T093000 DTEND;TZID=Australia/Sydney:20270902T103000 SUMMARY:Quarterly planning session DESCRIPTION:Agenda and dial-in details. LOCATION:Level 3 boardroom STATUS:CONFIRMED TRANSP:OPAQUE END:VEVENT END:VCALENDAR ``` No METHOD, a UID, UTF-8, the time zone defined above the event, and no calendar name. The `X-MS-OLK-FORCEINSPECTOROPEN` line is a Microsoft extension that tells classic Outlook to open the appointment window straight away instead of importing silently. New Outlook ignores it, which is fine. What AddCal does about it ------------------------- An [AddCal event link](https://addcal.co/solutions/add-to-calendar-links.md) gives a Windows user three Outlook options, and only one of them is a file. Outlook.com and Office 365 open the event pre-filled in the web calendar, so new Outlook's import dialog never comes into it. The Outlook option downloads the file above: UTF-8, no METHOD, a stable UID per event, the zone defined before the event, and no calendar name so it does not spawn a calendar. All-day events are written as plain dates with no time zone block, which is the shape Microsoft's own [MS-OXCICAL](https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-oxcical/) specification asks for and the one that stops an all-day event turning into a two-day one. You can make a link for free, with no account, at the [add to calendar link generator](https://addcal.co/tools/add-to-calendar-link-generator.md), or a single correct file at the [ICS generator](https://addcal.co/tools/ics-generator.md). If the file is fine and you just want the recipient's steps written out, [how to add an ICS file to Outlook](https://addcal.co/blog/how-to-add-an-ics-file-to-outlook.md) covers new, classic and web. Last updated on October 9, 2026 ![Tom](https://cdn.addcal.co/static/authors/atymic.jpg)### Tom Founder Built Calndr.link in 2020 because an event link broke in Outlook and it annoyed him enough to fix it properly. Six years later he can tell you exactly how each calendar app mangles a timezone, which is a worse party trick than it sounds. Otherwise found hanging off a rock somewhere in Australia. [GitHub](https://github.com/atymic)[X](https://x.com/atymic) ### Related articles [ICS Timezone Wrong in Google Calendar: Why Events Shift, and the Fix An imported .ics lands at the wrong time in Google Calendar for one of three reasons: a zone name Google does not know, a floating time read in your zone, or a bad daylight-saving rule. How to tell which, and the fix for each.](https://addcal.co/blog/ics-timezone-wrong-in-google-calendar.md)[How to Send a Calendar Invite (Any Calendar App) What a calendar invite actually is under the hood, how to send one properly in Google Calendar, Outlook, Apple Calendar and Gmail, the etiquette that gets people to accept, and why cross-organisation invites so often fail.](https://addcal.co/blog/how-to-send-a-calendar-invite.md)[Add to Calendar Link Not Working on iPhone? Why, and the Fix Tap Add to Calendar on an iPhone from Facebook, Instagram or WhatsApp and nothing happens. The link is fine; the in-app browser cannot hand a file to Calendar. How to tell which browser you are in, the fix, and how to build a link that works anyway.](https://addcal.co/blog/add-to-calendar-link-not-working-on-iphone.md) [ Browse all articles ](https://addcal.co/blog.md)