Excel 2013 is so buggy

[kavanagh]

I thought it was just me, in talking with my coworkers everyone is experiencing the same problems with frequent crashing etc. Is there a fix? I'm completely up to date.

 

[storm8]

x64 or x86? I have experienced workbooks that immediatelly crash under x64 but opened well under x86. when saved under x86 it then opened well under x64 again.

 

[joeu2004]

I thought it was just me, in talking with my coworkers everyone is experiencing the same problems with frequent crashing etc.

For my edification, is it really Excel 2013 that is the problem, or is it Office 2013 for particular "unusual" environments, such as Surface, web app (cloud computing), phone app, etc? And are you using 64-bit Office?

I am faced with having to buy a new computer, which means having to buy new Office software (read: 2013) because my previous version was pre-installed and linked to the CPU ID (read: non-transferable).

I keep hearing horror stories like this. I wonder if they apply to "normal" laptop and desktop environments using locally-installed 32-bit Office like mine, the "tried and true" environment.

[EDIT] I can imagine that Office 2013 is unreliable in the "unusual" environments since that is a re-engineered version of Office, scaled down and otherwise modified to fit the environment.

 

[joeu2004]

x64 or x86? I have experienced workbooks that immediatelly crash under x64 but opened well under x86. when saved under x86 it then opened well under x64 again.

Just to be clear, for my edification, when you say "x64", do you mean 64-bit Office per se?

Most (all?) PCs available today have x64 Intel or AMD CPUs and 64-bit Windows (Win7 or Win8). But I don't think that is what you mean, since it is impractical for most people to "save under [32-bit] x86, then open under x64" if you were talking about either the CPU or the O/S.

 

[tusharm]

My experience has been the exact opposite. It's been the most reliable of several past versions of Excel. I used the 32bit version for a while but it wasn't powerful enough for my work. So, I've been using 64bit Excel to crunch large data sets on a laptop, a more powerful desktop, and in a VM, and in each scenario the performance has been reliable.

Obviously, if it's a problem for you, it's a problem for you. Consider checking if there is something unique in your environment that might cause problems. Do you use some specific add-in? Particularly some third party add-in?

Does it happen when you (and your co-workers) open a specific workbook?

Some other pattern that you can identify?

I thought it was just me, in talking with my coworkers everyone is experiencing the same problems with frequent crashing etc. Is there a fix? I'm completely up to date.

 

[storm8]

Just to be clear, for my edification, when you say "x64", do you mean 64-bit Office per se?

I mean 64 bit version of Office (Excel).

I have complex project I work on (about 5 MB in size; 30k code lines, procedures on Workbook_Open - but noting that x86 would not handle). Sometimes when I open the file it just crashes, on all my computers that run Offfice x64. When I open the project under VM where I have Office x86 the WB opens just fine and when I save it I can again open it under x64 Office.

 

[kavanagh]

No we are not sharing workbooks. I was in our Ontario location and was talking to a coworker when poof his crashed and he described it as a frequent problem for him when other co-workers were chiming in describing the same situation(s). like frequent crashing is one, another problem is when your working with multiple SS open the cursor jumps to other work books and you have to find the appropriate SS and then fill in a cell and enter otherwise excel is locked up. I've used office xp, 2003, 2010, and have never had any issues. It is very frusterating as I use excel all day.

 

[tusharm]

No one has brought up shared workbooks. So, I am not sure why you refer to the issue.

In any case, Excel 2013 implemented SDI ("single document interface") so that its behavior is more like Word's.

What you describe is not something I've experienced and I wonder if it's caused by some code that is activating / selecting worksheets/ranges.

As a *test* start Excel in safe mode (thereby disabling all add-ins), then open *only* workbooks that end in XLSX. Do you still have the problem of the mouse jumping to different workbooks?

No we are not sharing workbooks. I was in our Ontario location and was talking to a coworker when poof his crashed and he described it as a frequent problem for him when other co-workers were chiming in describing the same situation(s). like frequent crashing is one, another problem is when your working with multiple SS open the cursor jumps to other work books and you have to find the appropriate SS and then fill in a cell and enter otherwise excel is locked up. I've used office xp, 2003, 2010, and have never had any issues. It is very frusterating as I use excel all day.

 

[MrBtoo]

Has there been any resolution here to these questions. I've been using excel since the first Bush administration and quite good at it. I bought a new laptop back in the summer and just cannot believe how buggy it is. I've used every version of Excel -- did MS rewrite it? I have build 15.0.4454.1503 32-bit (H&S) in the about excel tab. I think its memory leakage, and regularly have to shut it down and bring it back up. Unlike any other app on my new windows 8 machine. I had heard somewhere it had been re-written. With all the bugs this makes sense, so my purpose here is to find a more stable version. Got Any?