Microsoft Office 2013 keeps crashing, need help

I've tried installing Office 2013 32-bit on my Windows 7 Machine that is 64-bit, but every time I go to open one of the programs a Windows message appears telling me that Windows has stopped working. The way I installed the product was a burned image file from a volume license download, and then upgraded from Office 2010 32-bit. If anyone has any suggestions that would be great!
Brandon GarnettAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Brandon GarnettConnect With a Mentor Author Commented:
I figured out the issue was that the firewall was blocking the application from upgrading. And for our DB in Access to work we had to upgrade from 2010 to 2013.
0
 
JohnBusiness Consultant (Owner)Commented:
Uninstall Office, run SFC /SCANNOW in an admin command prompt. Allow to complete, restart, Install Office and patch. Does it work?

If no, create a new, test Windows User Profile (Account). Log into the new Windows Account and try again.

Office 2013 works just fine on Windows 7 64-bit.
0
 
web_trackerCommented:
Although a 32 bit version of office will work on a 64 bit operating system, is there any specific reason you decided to install the 32 bit version. If not why dont you install the 64 version of office. We have for several years used office 2013 on windows 7 machines without any problems.  This is for over a thousand users (all systems are imaged the same).
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
JohnBusiness Consultant (Owner)Commented:
64-bit Office is generally not recommended because it does not coexist well with other 32-bit software (Adobe, Flash, Java and so on).

We have many dozens of client 64-bit computers all humming along fine with 32-bit Office. It remains the recommended approach by Microsoft
1
 
MacleanSystem EngineerCommented:
Start a command prompt, and type in "Outlook /safe" see if this loads without crashing.
If yes, disable plugins from startup.

For the rest Johns suggestion for a SFC /Scannow is a good way to go.
To add to that comment, there are further steps required once corruption has been detected. Running Sysnative's SFCFix.exe is an easy way to help on that area. See article on this tool/method here
0
 
nobusCommented:
instead of upgrading the 2010 version, why don't you uninstall that first - then install the 2013 fresh?
0
 
Brandon GarnettAuthor Commented:
when trying to uninstall both office 2010 and office 2013 the uninstall wizard would pop up, then act like it was going to start, and then close out of itself.

Any suggestions?
0
 
JohnBusiness Consultant (Owner)Commented:
I see your problem. Do not use two versions of Office on the same machine. Uninstall Office 2010 and all bits, uninstall Office 2013 and all bits, shut down, start up and install just Office 2013. That will fix your issue.
0
 
nobusCommented:
if it does not uninstall, try REVO to uninstall them :  http://www.revouninstaller.com/
0
 
MacleanSystem EngineerCommented:
If you are having issues try either as suggested by Nobus, or use the official Microsoft Uninstall tools located here.

Microsoft Office 2010 Uninstall tool
Microsoft Office 2013 Uninstall Tool
0
 
Brandon GarnettAuthor Commented:
The Uninstall 2010 and 2013, then reinstall 2013 stopped the crashing and everything works fine now except for one of our companies Access databases. The database was created in Access 2007, which should still work in 2013, but whenever I try to enter the database error messages pop up. The error messages look like strings of code. Out of the 3 computers that I've tested it on, the one that works fine is the one I upgraded from 2010 to 2013.
0
 
JohnBusiness Consultant (Owner)Commented:
Try (as a test) upgrading the Access DB to 2010 on another machine and then to 2013 on your machine to see if that works.
0
 
Brandon GarnettAuthor Commented:
Through trial and error, and help from coworkers we found the solution
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.