Link to home
Create AccountLog in
Avatar of ralfswan
ralfswanFlag for United States of America

asked on

How do I set MS Office 2010 Beta file associations?

I haven't figured out a way to automatically open Excel files with the Office 2010 Beta version of Excel. When I change (in Win XP Folder Options/File Types) the .xls extension to open with the Microsoft Office Client Virtualization Handler (CVH.exe), it defaults to Word.

The only way I can open an Office file other than a Word document is to first start the app and then open the file.
Avatar of tbsgadi
Flag of Israel image

How about associating to : C:\Program Files\Microsoft Office\Office14\EXCEL.EXE ?

Avatar of ralfswan


There are no executables in the Office14 folder to point to.

The target for Excel is
"C:\Program Files\Common Files\Microsoft Shared\Virtualization Handler\CVH.EXE" "Microsoft Excel 2010 (Beta) 2014006204090000",
the target for Word is
"C:\Program Files\Common Files\Microsoft Shared\Virtualization Handler\CVH.EXE" "Microsoft Word 2010 (Beta) 2014006204090000",
Perhaps the files are hidden?  Because my executable is exactly where tbsgadi suggested.

What version of Office 2010 Beta did you download?
The MS Office 2010 Public Beta apps all run from the Microsoft Client Virtualization Handler (CVH.exe). For example, the target from the properties for Excel 2010 is "C:\Program Files\Common Files\Microsoft Shared\Virtualization Handler\CVH.EXE" "Microsoft Excel 2010 (Beta) 2014006204090000". My question is how do I enter this path and parameter into the “Opens with:” in the Win XP File Type association.
Hmmm - sorry - that I do not know.  I downloaded the full version.... sorry
I am very disappointed with my initial question to Experts Exchange. I originally accessed EE and browsed for my problem with appropriate keywords. I discovered a question that pertained to my problem, but was informed that to see the solution I would have to subscribe. I started my subscription, only to discover that the question I had found had been commented on, but no solution had been found.  I then entered my own question, following the guidelines stated. I assigned a lower number of points to the question because, frankly, I did not feel that the question was that complex. The comments above show the progress (or lack of) since that time. I do not object to the deletion of my question since I do not expect a resolution. I will also cancel my subscription.
Avatar of zorvek (Kevin Jones)

I'm looking at your issue. Please note that not many of us have 2010 beta installed because it has had issues coexisting with earlier versions and we all like to have the last so many versions of Excel on our boxes. If I can't figure out what is wrong with your installation I'll post in the private MVP newsgroup which is monitored by the Excel team.

You neglected to inform us that you are not working with the consumer standalone version of Office 2010 Beta, rather you are working with a sequenced version of Office 2010 using Microsoft App-V. This is a solution used by larger institutions that distribute and run Microsoft products from servers. By not revealing this information up front you make it harder for us to help you.

That said, you need to work with your IT department to correct the file association. The information they need to fix the problem is found on page 6 of this Microsoft white paper:

I downloaded and installed Microsoft Office Home and Business 2010 Beta from
I don't believe Microsoft intends this product for "larger institutions that distribute and run Microsoft products from servers." I am a home user with a standalone pc--I do not have an IT Department. I tried to provide as much information that I could to obtain a resolution for this problem and I certainly did not intentionally withhold information.
Avatar of zorvek (Kevin Jones)
zorvek (Kevin Jones)
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
It took a while, but I guess I can chalk that up to my inexperience with EE question submission, and the fact that we are treading on new waters here with a Beta product. Thanks for the effort.
In hindsight, you did fine. Timing (MVP conference in Seattle) and lack of experience on our part (2010 Beta has only been out a few months) played a role.

I hope you will ask another question soon so we can show you we really do know something here - most of the time ;-)