locked
CreateObject getVersion Outlook registry key reference RRS feed

  • Question

  • Posted this elsewhere, but have yet to see a single response. Really could use some insight or suggestions, anything really.


    Issue:

    Program uses CreateObject to create a new email form using locally installed Outlook. Part of this involves a getVersion check in the registry to a key that has a value of a file path under C:\Program Files\WindowsApps\

    that then goes to a folder for Outlook which contains the current build version of the program on the system. After an update, the build version updated and generated a new folder which contains the appropriate dll files and a separate OUTLOOK.exe file used for this automation process.

    The thinking is that the registry key's value was not updated to then match this change after the Office update. The program attempting to create a new email/message form then hits a dead-end as the folder for the previous build is no longer there, it was removed as part of the Office update process. This leads to the program instantly terminating and in the Event Viewer showing a KERNELBASE.dll and .NET framework errors.

    Repetitive online repairs of Office do NOT affect this registry key and the issue persists.

    Conclusion for a resolution is to manually correct the registry key value to point to the correct folder that matches the current build of Outlook.

    Example:  forced an error to show where the registry is looking-

    C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Outlook_16051.11629.20214.0_x86__8wekyb3d8bbwe\Office16\Outlook.exe

    Folder/file path it SHOULD be looking at instead.

    C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Outlook_16051.12130.20344.0_x86__8wekyb3d8bbwe\Office 16\Outlook.exe

    The work-around found was to copy the current build folder, re-name it to the previous build noted in the error so it matches and no longer dead-ends, restoring the function, but an error still occurs after the fact due to there still being a mis-match existing between the registry/actual outlook build version.

    There are redundant keys that reference the same file path - hoping someone can tell me for certain which specific key the command checks to find the version/file path so it can be manually corrected.

    Trying to avoid having to go through each and every key, change the value, see if the process breaks and just trial/error the whole thing. Asked in a couple other places already and just a side-note, does not have anything to do with the store app for Office.

    Thanks for your time and any advice.

    Tuesday, December 10, 2019 2:55 PM

Answers

  • Got it.

    Big thanks to Diane on the community site. Key referenced

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\outlook.exe

    If I alter the path, the automation breaks and causes the errors in the Event Viewer.  Users affected likely still have a path tied to the store app version of Outlook, even if it was previously removed off the system, the registry did not get changed to reflect a pathway to the C2R local version of Outlook. Correct the values to the following and the problem is resolved:

    (Default) C:\Program Files\Microsoft Office\Root\Office 16\OUTLOOK.EXE

    Path C:\Program Files\Microsoft Office\Root\Office 16\

    • Marked as answer by NathanCompass Friday, December 13, 2019 3:13 PM
    Friday, December 13, 2019 3:13 PM

All replies

  • Hi,

    Welcome to our forum.

    Since here we mainly focus on general issues about Outlook desktop client but your issue is more related to the problem between Outlook and store app. So I'm afraid there is few information I can give you.

    I see you have posted this thread elsewhere, you can refer to the suggestions of Diane.

    Hope this can be helpful.

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Wednesday, December 11, 2019 8:26 AM
  • Hi,

    Have you got the issue fixed?

    I'm writing to see if the reply above is helpful to you. If yes, would you mind helping mark the reply as answer? So that others who might have a similar question can benefit from your thread? Thanks for your understanding and support.

    Regards, 

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Thursday, December 12, 2019 8:22 AM
  • Hello Aidan,

    No - issue is not fixed and other information provided related the app store version of Outlook makes no difference and is not related.

    To simplify -

    My immediate question is when the CreateObject command is used that has a getVersion to check the registry for info on the currently installed version of Outlook - which should lead to a value on the registry key that has a file path - 

    I need to know the exact registry key the getVersion part actually checks. Everything else is irrelevant until I know the specific key being used to get to Outlook.

    People seem to know how to get from A to Z, but not the in-between in this case. I've got half a dozen people experiencing the same problem at the moment - if I knew which key is being used I could easily replicate the problem on my own device.

    So far the game plan is to export the entire registry, look for keys with a particular file path and change them until I discover by trial/error which key breaks the process since it doesn't appear to be documented anywhere I've looked online.

    Thursday, December 12, 2019 3:25 PM
  • Got it.

    Big thanks to Diane on the community site. Key referenced

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\outlook.exe

    If I alter the path, the automation breaks and causes the errors in the Event Viewer.  Users affected likely still have a path tied to the store app version of Outlook, even if it was previously removed off the system, the registry did not get changed to reflect a pathway to the C2R local version of Outlook. Correct the values to the following and the problem is resolved:

    (Default) C:\Program Files\Microsoft Office\Root\Office 16\OUTLOOK.EXE

    Path C:\Program Files\Microsoft Office\Root\Office 16\

    • Marked as answer by NathanCompass Friday, December 13, 2019 3:13 PM
    Friday, December 13, 2019 3:13 PM
  • Hi,

    I'm glad to see your issue has been fixed.

    Here I will provide a brief summary of this post for your information. This will make answer searching in the forum easier!

    Request/Expectation:

    CreateObject getVersion Outlook registry key reference

    Solution Summary:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\outlook.exe

    If I alter the path, the automation breaks and causes the errors in the Event Viewer.  Users affected likely still have a path tied to the store app version of Outlook, even if it was previously removed off the system, the registry did not get changed to reflect a pathway to the C2R local version of Outlook. Correct the values to the following and the problem is resolved:

    (Default) C:\Program Files\Microsoft Office\Root\Office 16\OUTLOOK.EXE

    Path C:\Program Files\Microsoft Office\Root\Office 16\



    Reference Links:

    No.

    Regards, 

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.



    Tuesday, December 17, 2019 8:16 AM