SOLVED

CreateObject getVersion Outlook registry key

%3CLINGO-SUB%20id%3D%22lingo-sub-1045060%22%20slang%3D%22en-US%22%3ECreateObject%20getVersion%20Outlook%20registry%20key%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1045060%22%20slang%3D%22en-US%22%3E%3CP%3EAfternoon%2C%3C%2FP%3E%3CP%3EProgram%20uses%20CreateObject%20to%20create%20a%20new%20email%20form%20using%20Outlook.%20Part%20of%20this%20involves%20a%20getVersion%20check%20in%20the%20registry%20to%20a%20key%20that%20has%20a%20value%20of%20a%20file%20path%20under%20C%3A%5CProgram%20Files%5CWindowsApps%5C%3C%2FP%3E%3CP%3Ethat%20then%20goes%20to%20a%20folder%20for%20Outlook%20which%20contains%20the%20current%20build%20version%20of%20the%20program%20on%20the%20system.%20After%20an%20update%2C%20the%20build%20version%20updated%20and%20generated%20a%20new%20folder%20which%20contains%20dll%20files%20and%20a%20separate%20OUTLOOK.exe%20file%20used%20for%20this%20automation%20process.%20The%20thinking%20is%20that%20the%20registry%20key's%20value%20was%20not%20updated%20to%20then%20match%20this%20change.%20The%20program%20attempting%20to%20create%20a%20new%20email%20then%20hits%20a%20dead-end%20as%20the%20folder%20for%20the%20previous%20build%20is%20no%20longer%20there%2C%20it%20was%20removed%20as%20part%20of%20the%20Office%20update%20process.%20This%20leads%20to%20the%20program%20instantly%20terminating%20and%20in%20the%20Event%20Viewer%20showing%20a%20KERNELBASE.dll%20and%20.NET%20framework%20errors.%3C%2FP%3E%3CP%3ERepetitive%20online%20repairs%20of%20Office%20do%20NOT%20affect%20this%20key%20and%20the%20issue%20persists.%20Conclusion%20for%20a%20resolution%20is%20to%20manually%20correct%20the%20registry%20to%20point%20to%20the%20correct%20folder%20that%20matches%20the%20current%20build%20of%20Outlook.%3C%2FP%3E%3CP%3EExample%3A%26nbsp%3B%20forced%20error%20to%20show%20where%20it%20is%20looking-%20C%3A%5CProgram%20Files%5CWindowsApps%5CMicrosoft.Office.Desktop.Outlook_16051.11629.20214.0_x86__8wekyb3d8bbwe%5COffice16%5COutlook.exe%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20436px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159863iD1CC4C822D710B8F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Outlook%20error.png%22%20title%3D%22Outlook%20error.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3Eforced%20error%20to%20demonstrate%20where%20the%20registry%20value%20looks%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F159864i57AC95AB3041E401%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Outlook%20true%20location.png%22%20title%3D%22Outlook%20true%20location.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3Efolder%20the%20registry%20SHOULD%20be%20pointed%20to%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EFolder%2Ffile%20path%20it%20SHOULD%20be%20looking%20at%20instead.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20work-around%20found%20was%20to%20copy%20the%20current%20build%20folder%2C%20re-name%20it%20to%20the%20previous%20build%20noted%20in%20the%20error%20so%20it%20matches%20and%20no%20longer%20dead-ends%2C%20restoring%20the%20function%2C%20but%20an%20error%20still%20occurs%20after%20the%20fact%20due%20to%20there%20still%20being%20a%20mis-match%20existing.%3C%2FP%3E%3CP%3EThere%20are%20redundant%20keys%20that%20reference%20the%20same%20file%20path%20-%20hoping%20someone%20can%20tell%20me%20for%20certain%20which%20specific%20key%20the%20command%20checks%20to%20find%20the%20version%2Ffile%20path%20so%20it%20can%20be%20manually%20corrected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20kindly%20for%20your%20advice%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1053217%22%20slang%3D%22en-US%22%3ERe%3A%20CreateObject%20getVersion%20Outlook%20registry%20key%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1053217%22%20slang%3D%22en-US%22%3EAny%20input%20on%20this%3F%20It's%20difficult%20to%20comb%20through%20multiple%20registry%20entries%20that%20are%20similar%20to%20identify%20which%20specific%20one%20is%20being%20used%20to%20direct%20to%20the%20appropriate%20file%20path.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20your%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1062971%22%20slang%3D%22en-US%22%3ERe%3A%20CreateObject%20getVersion%20Outlook%20registry%20key%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1062971%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20posted%20a%20similar%20entry%20on%20social.technet%20and%20on%20the%20community%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3ETo%20simplify%20-%3C%2FP%3E%3CP%20class%3D%22%22%3EMy%20immediate%20question%20is%20when%20the%20CreateObject%20command%20is%20used%20that%20has%20a%20getVersion%20to%20check%20the%20registry%20for%20info%20on%20the%20currently%20installed%20version%20of%20Outlook%20-%20which%20should%20lead%20to%20a%20value%20on%20the%20registry%20key%20that%20has%20a%20file%20path%20-%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20to%20know%20the%20exact%20registry%20key%20the%20getVersion%20part%20actually%20checks.%20Everything%20else%20is%20irrelevant%20until%20I%20know%20the%20specific%20key%20being%20used%20to%20get%20to%20Outlook.%3C%2FP%3E%3CP%3EPeople%20seem%20to%20know%20how%20to%20get%20from%20A%20to%20Z%2C%20but%20not%20the%20in-between%20in%20this%20case.%20I've%20got%20half%20a%20dozen%20people%20experiencing%20the%20same%20problem%20at%20the%20moment%20-%20if%20I%20knew%20which%20key%20is%20being%20used%20I%20could%20easily%20replicate%20the%20problem%20on%20my%20own%20device.%3C%2FP%3E%3CP%3ESo%20far%20the%20game%20plan%20is%20to%20export%20the%20entire%20registry%2C%20look%20for%20keys%20with%20a%20particular%20file%20path%20and%20change%20them%20until%20I%20discover%20by%20trial%2Ferror%20which%20key%20breaks%20the%20process%20since%20it%20doesn't%20appear%20to%20be%20documented%20anywhere%20I've%20looked%20online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20in%20CLSID%3F%20Interface%3F%20TypeLib%3F%20Even%20in%20Classes_root%3F%20Actually%20in%20Local_machine%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1065353%22%20slang%3D%22en-US%22%3ERe%3A%20CreateObject%20getVersion%20Outlook%20registry%20key%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1065353%22%20slang%3D%22en-US%22%3EGot%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EBig%20thanks%20to%20Diane%20on%20the%20community%20site.%20Key%20referenced%3CBR%20%2F%3E%3CBR%20%2F%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CApp%20Paths%5Coutlook.exe%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20alter%20the%20path%2C%20the%20automation%20breaks%20and%20causes%20the%20errors%20in%20the%20Event%20Viewer.%20Users%20affected%20likely%20still%20have%20a%20path%20tied%20to%20the%20store%20app%20version%20of%20Outlook%2C%20even%20if%20it%20was%20previously%20removed%20off%20the%20system%2C%20the%20registry%20did%20not%20get%20changed%20to%20reflect%20a%20pathway%20to%20the%20C2R%20local%20version%20of%20Outlook.%20Correct%20the%20values%20to%20the%20following%20and%20the%20problem%20is%20resolved%3A%3CBR%20%2F%3E(Default)%20C%3A%5CProgram%20Files%5CMicrosoft%20Office%5CRoot%5COffice%2016%5COUTLOOK.EXE%3CBR%20%2F%3E%3CBR%20%2F%3EPath%20C%3A%5CProgram%20Files%5CMicrosoft%20Office%5CRoot%5COffice%2016%5C%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Afternoon,

Program uses CreateObject to create a new email form using 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 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. The program attempting to create a new email 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 key and the issue persists. Conclusion for a resolution is to manually correct the registry to point to the correct folder that matches the current build of Outlook.

Example:  forced error to show where it is looking- C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Outlook_16051.11629.20214.0_x86__8wekyb3d8bbwe\Office16\Outlook.exe

forced error to demonstrate where the registry value looksforced error to demonstrate where the registry value looks

folder the registry SHOULD be pointed tofolder the registry SHOULD be pointed to

Folder/file path it SHOULD be looking at instead.

 

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.

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.

 

Thank you kindly for your advice in advance!

3 Replies
Highlighted
Any input on this? It's difficult to comb through multiple registry entries that are similar to identify which specific one is being used to direct to the appropriate file path.

Thank you for your time.
Highlighted

I've posted a similar entry on social.technet and on the community site.

 

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.

 

Is it in CLSID? Interface? TypeLib? Even in Classes_root? Actually in Local_machine?

Highlighted
Best Response confirmed by NcarterCompass (New Contributor)
Solution
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\