
I have used the code available at for Building the code has no issue. Should be resolved.I am writing a pgm to read outlook-2016 mails from windows7 on VS2019 IDE with. Run Office online repair and try it again. You may see an additional error that is for version 15.0.0.0 and states "access is denied."

Save the file, launch the program again, test the process to populate an Excel template with bookmarks again. ) if you open this file in notepad or a visual studio viewer there is likely a section dedicatedĪdd this to the end of that section before it moves on to other instructions: There's a machine-level policy under C:\Windows\assembly that tells an application that is backwards-compatible with older versions of Office to to be redirected and use the appropriate newer interop assembly associated with the more current version of OfficeĬopying this policy code and going to the application-level, where the application is installed there may be a config file for the executable (e.g. TL DR- get that error after June update, spam online repair. Is there a chance a bug fix will be submitted so the following updates won't break the assembly redirects?ĭecided to go ahead and post something about it for the community at least. Nobody has bothered saying anything to MS up to this point because they all doubt it will be addressed with a fix for at leastĪ month, if at all.

Issues until manually corrected, but this is something a bit different.Įverybody in the office is started to get this as they each end up getting an Office update and it's getting more than frustrating. We've found the MS Support Office uninstall tool is not a complete clean uninstall and there are some keys under HKCR/TypeLib that it doesn't touch and can leave lasting The current resolution is to run Online Office Repair multiple times until it is corrected finally and if it still hasn't correctedĪfter the third time, to do a full uninstall and reinstall Office hoping that'll correct it. The update breaks this redirect path somewhere in the registry, but we haven't been able to discover the exact spot as yet. Normally this is fine as there are redirects in place that would point towards the currentĪssembly version for the installed version of Office to use, such as version 15.0.0./365.


It's been explained to me that the software is geared to reference that assembly so it is compatible with the lowest version of Office that they can support (2007). The system cannot find the file specified. , Version=12.0.0.0, Culture=neutral, PublicKeyToken= Third party software our office uses to populate bookmarks on templates runs into this error after taking the June 2019 Office update:
