Re: Open With.. functionality doesn't fully work <XPSP1>

Hi Bluescreens,

Open Regedit.exe and navigate to:

HKEY_CLASSES_ROOT\Unknown\shell\openas\command

In the right-pane, double-click (default) and copy the data assigned.

Post the info here.

--
Ramesh, Microsoft MVP
Windows XP Shell/User
http://windowsxp.mvps.org


"Bluescreens" <bluescreens@xxxxxxxxx> wrote in message news:1115128518.854460.150510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
I'm in a domain environment.  I have two machines that both have the
same GPOs applying against them, so it appears this isn't a GPO issue.
The machines are XP SP1.  I'm logged in as the same user on both
machines.

Doing a GPRESULT /Z on both machines and comparing the results doesn't
show major differences.

On one machine, Open With functionality works normally - if I have a
.TXT file and choose to associate it with 555.exe via Open With /
Choose / Browse / and picking 555.exe, 555.exe will appear on the full
Open With menu (detailing Recommended programs and Other programs).  I
can then successfully use 555.exe to open the textfile, I can click on
"Always use..." and all is well.

On another, Open With functionality does not work correctly - if I have
a .TXT file and click Open With, Choose Program..., Browse, select
555.exe, and then I go back to the "Open With" GUI menu, I see a list
of programs that does not include 555.exe.  That's the problem - it
should add 555.exe to that list!

Any ideas?  Does anyone have any guesses for what would cause this?  Is
there a policy to lock down open-with functionality and or the full
file associations tab in XP?

Help!  :)


.

Relevant Pages

  • Re: OL2k3+Ex2k3, Shared mailbox, custom form, imported contact=slo
    ... I played around with owner create via import vs. sharer create via import ... logical step was to turn off cached exchange mode to see if the problem ... machines already, so it didn't appear to be machine specific, but, just ... updates are okay and don't affect anything, but Office SP1 does, which sucks ...
    (microsoft.public.office.developer.vba)
  • Re: A DLL gone bad ?
    ... version is equal to or higher than what's listed in the manifest. ... Do the file versions between the two machines match? ... MDAC 2.8 SP1 MDAC_TYP.exe file on a computer that is running Windows ...
    (microsoft.public.vb.general.discussion)
  • Re: Patched XP Pro SP1 vs. XP Pro SP2
    ... and with the plethora of extra Group Policy options. ... one with SP1 plus all currect security and critical patches applied. ... All machines have current MS security and critical patches ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Access 2007
    ... So you have a mismatch of an SP1 accdr file, and users using the original release of the runtime. ... I also would think, if it updates Access 2007 full version correctly, that it would do so for the runtime. ... However when I tried to install SP1 on the machines with Access ...
    (comp.databases.ms-access)
  • Re: Access 2007
    ... However when I tried to install SP1 on the machines with Access ... The client machines have the "free" Access runtime version installed. ...
    (comp.databases.ms-access)