Autodesk Revit MEP

[#1]

I have just installed Revit MEP 2012 & 2013 on a Windows 7 Professional 64bit machine.

In both versions, the context menus stick on whatever the last menu was.  To get it to switch to the correct context menu, I have to close the ribbon and re-open the ribbon.

For instance, if I open a project ans select a light fixture I get the correct menu (edit family, create systems, power/switch).  But now if I select some text, the context menu comes back up with the light fixture context menu - instead of the text menu (formant, check spelling, etc...).  To get the correct menu, I close and reopen the ribbon.

I am hoping someone else has had this issue and maybe knows a fix for it.

[#2]

We're having this exact problem, but only on certain machines. What's really strange is all the machines are the exact same specs, we ordered about 12 identical ones. A hotfix would be great...

[#3]

Yes!  Only on certain machines!

I didn't mention that we ordered two identical computers, both 64bit witn Win 7 Pro. Dell Precisions.

I personally installed Revit 2012 & 2013 on each machine.  One machine works fine.  The other has this issue with the context menus.

[#4]

Yes - had this on two machines. One was a desktop and one was a laptop.

The only way to fix it was a re-install.

I found it started off with losing the dialogue box that asks about over-riding parameter values when loading a family. Then the ribbon started playing up and you have to cycle through the ribbon to get the contextual tabs back properly.

The weird thing about it is, it started on 2012 but has also affected 2013. Desktop is fixed but laptop is still a problem as it takes out IT forever to fix stuff and can't be bothered to wait!! 

[#5]

Julian, did your IT people have to uninstall/reinstall both 2012 & 2013 or just one or the other?

Thanks.

[#6]

We only repaired the 2012 version as that was the only one being used on the project. I haven't tested 2013.

Don't recall a full uninstall then reinstall - just re-running the install rather than the repair function.

We use remote packages so they just send it out and then we run the package installer (usually rendering our PC unusable for a few hours!!)