Using Classic Outlook on Windows for personal email, calendar, and contact management
Outlook 2024 is part of the Office 2024 product family and can coexist with Office Home & Student 2019, but there are some version‑mix and activation behaviors to be aware of.
From the description, Outlook is starting but showing as Outlook 2019, which matches the known behavior where Office 2024 apps can appear as an earlier version if that earlier version is also licensed on the same Microsoft account.
To get Outlook 2024 correctly recognized and activated without breaking the existing Office Home & Student 2019 apps, follow these steps:
- Make sure Office/Outlook 2024 is fully updated
- Install the latest Office 2024 updates using the steps in Install Office updates. This is required to fix the issue where Office 2024 appears as an earlier version.
- Clear the local license cache for the newer Office family only
- Close all Office apps (Word, Excel, PowerPoint, Outlook, etc.).
- In File Explorer, go to:
-
%LocalAppData%\Microsoft\Office\Licenses
-
- Delete the folder named
5in that directory.- This is the folder used by the newer Office 2024 licensing; deleting it does not remove the Office Home & Student 2019 installation itself.
- Re‑sign in and bind Outlook 2024 to the correct license
- Start Outlook.
- When prompted, sign in with the Microsoft account that owns the Outlook/Office 2024 purchase.
- If given a choice of products, select the Office/Outlook 2024 license.
- Confirm in the product information/backstage that Outlook now shows as part of Office 2024.
These steps only reset the Office 2024 licensing information and re‑associate it with the correct account; they do not uninstall or deactivate the existing Office Home & Student 2019 apps. Excel, Word, and PowerPoint from Office Home & Student 2019 will remain installed and usable.
If, after updating and clearing the 5 license folder, Outlook still shows as 2019 or activation fails, contact Microsoft support at https://support.microsoft.com/home/contact for further account‑specific troubleshooting.
References: