![]() I installed it and kept 2007 since 2013 did not include Visio and I use it a lot.įew days later I needed to have Acrobat pro and so I installed my old copy of Adobe CS3. I then had the opportunity to install office 2013 pro (for $10 thorough job). I installed office 2007 pro and visio 2007 pro on a new 64 bit windows 7 system. I know this is an old post but I had the configuration issue for days and did not find an answer that worked for me so I would like to offer my experience in case there is someone like me looking for an answer. Too many interactions between Office and Windows registry components. Note: The real answer is to rebuild the box and reinstall the OS too. Giving non-admin users read access to these keys, sub-keys and values and ensuring that they are owned by an Administrator fixed the problem. In the cases listed, it seems to be to do with the permissions on the various file type keys e.g. Messages 10 gave specifics about which registry keys were causing the problem. Looking into the Event Viewer after a failed startup gave me a list of events for the MsiInstaller. ![]() In my case, I suspect some registry permissions were not left in a state that Office 2010 was expecting (e.g. The thread that pointed to contains the full story. Others have solved the problem by completely removing previous versions of Office using the Office clean up process and reinstalling. The issue I had seems to be registry related. There are a number of other forums with similar problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |