![tell what version of microsoft office i have tell what version of microsoft office i have](https://support.content.office.net/en-us/media/d9761500-d0a8-47f6-bf34-95b161385aa7.png)
- #TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE CODE#
- #TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE LICENSE#
- #TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE DOWNLOAD#
- #TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE WINDOWS#
Somehow I do not feel easy about this as of now. "Add-ins and other extensibility solutions that are compatible with Office 2016 will most likely be compatible with Office 2019 or will require only minimal testing."
![tell what version of microsoft office i have tell what version of microsoft office i have](https://i.stack.imgur.com/O5sD4.png)
While this entry could easily be added to case 16, who knows if this entry may not also be used for updates to 365? And what other entries might be used in other scenarios/on other machines? Looks like potential proliferation of entries asking for updates everytime another entry has been discovered. Ken's macro returns 0, though it is not 'too old to bother with'ĪrrEntryNames(x) has one entry which reads "MigrationToV5Done"
#TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE WINDOWS#
(And I may have to create yet another windows installation with Office 2016 for testing. I've made a quick check for a few new features of 2019 and the application splash screen at startup also states inmistakenly 2019. If I click on Show additional licensing information it shows both 2019 and below that entry it shows 2016. I've been running Office 20 in parallel and I've been hoping that 2019 will coexist, too.
![tell what version of microsoft office i have tell what version of microsoft office i have](https://www.engineeredcode.com/wp-content/uploads/2019/05/FastTrack.jpg)
Today I've installed 2019 and to my surprise I've made the discovery that the version number is still reported as 16. I've put off the installation of Office 2019 for a long time. Īny news for a solution of this version number problem? (It's not been a problem for me yet, but it may become one.) This entry was posted in Excel, General, Office 2007, Office 2010, Office 2013, Office 2016 by Ken Puls. So if you do test, please let us know what channel you are on in addition to whether or not it works! I am starting to wonder if this key is only present for Insiders. This should pick it up no matter where in the key the 365 term shows up.
#TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE CODE#
I'd love it if people could give this a try and see if it returns correctly based on the versions of Excel you're running, particularly if you have a flavor of Office 365 or Excel 2019.ĮDIT: I have made a small change to the code and sample file in case "O365" is not at the beginning of the registry key.
#TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE DOWNLOAD#
If you'd prefer to just download a workbook with the code in it, here you go. If InStr(arrEntryNames(x), "2019") > 0 Then If InStr(arrEntryNames(x), "365") > 0 Then RegistryObject.EnumValues &H80000001, keyPath, arrEntryNames, arrValueTypes Set registryObject = GetObject("winmgmts:!\\" & rootDirectory & "\root\default:StdRegProv") KeyPath = "Software\Microsoft\Office\" & CStr(Application.Version) & "\Common\Licensing\LicensingNext" 'Written by Ken Puls (Dim registryObject As Object Function to check the application version in Modern Office So anyone with Office 365 installed should receive 365 as a return, otherwise you'll get a four digit number representing the version you have installed.
#TELL WHAT VERSION OF MICROSOFT OFFICE I HAVE LICENSE#
It's purpose is fairly simple: Test the application and see if it is a perpetual license or a subscription install, and return the version number. Given that, I've pulled together this function. While I haven't tested with other SKUs, this would seem to indicate a pattern I hope we can rely on. And even better, that key holds values like "O365ProPlusRetail" vs "Office2019ProfessionalPlus". So how can we check the application version in modern Office?Īfter doing a little digging, I finally found a registry key that seems to appear in Office 2019 and Office 365, but does not exist in Office 2016. I needed to find a way to programatically enumerate whether a user is running Office 2016, Office 2019 or Office 365, as I had to do something different in each case. This past week I ran into a scenario where I needed to do exactly this. As there are now things that work differently for Office 365 than the perpetual licenses, this is another potential problem for developers. (Bastien discusses this i n a blog post a few months ago.) But worse, while he focuses on 2016 vs 2019, there is also no way to test between these and Office 365 subscription versions. From Office 2016 onwards, Microsoft has not revved the Application.Version number - they all show as 16.0 - giving you no way to differentiate between versions. But then Office 365 came out, and 2019, and things fell apart.Ĭonducting a check of the application version in Modern Office is not as straight forward. You just used a little test of Val(Application.Version) to return the number. In the good old days, it was easy to check the application version in Office with VBA.