Windows cannot find C: (doc) Make sure you typed the name ..

I can't say I'm confident this problem will be fixed by SP1. I'm desperate
for help from someone - it is such a terrible bug in Vista!!!

Help!!!!!

"Terry Farrell" wrote:

> David
>
> SP1 for Vista is under test too: solely a guess that both Office and Vista
> SP1s will be out together. The fix list for Vista is massive - but I only
> saw a preview, so I have no idea what will be in the final package.
>
> Terry
>
> "David" <David.RemoveThis@discussions.microsoft.com> wrote in message
> news:F1B789EE-FC20-41D3-9D6E-8CB011EE36E9@microsoft.com...
> >
> > Hi there, I'm the guy who raised this issue in the first place on a couple
> > of MS forums, and got no satisfactory answert.
> >
> > I can confirm that it's nothing to do with AV software. If I disable it, I
> > still get the problem.
> >
> > I can also confirm that the problem is not to do with Word 2007, but with
> > Vista Explorer. I get the problem whenever I try to open a Word or htm
> > file
> > *before* I've opened the associated application (Word or Firefox). If I
> > double click the file in Explorer, I get 'Windows cannot find the file
> > specified etc. etc.'.
> >
> > If I open the program, e.g. Word or Firefox, and *then* click the file in
> > Explorer, it opens fine. I can also open the file *within* the program
> > using
> > File/Open.
> >
> > I've tried everything. I sure as heck don't want to reinstall Vista, so if
> > it's true that SP1 will solve the problem I'll be very happy. But I share
> > the scepticism, since it only seems to affect a small no. of users, so
> > are
> > Microsoft really dealing with it?
> >
> > Can some kind person please verify that SP1 really will deal with this
> > hideously annoying problem?
> >
> > Many thanks,
> > David
> >
> >
> >
> > "Terry Farrell" wrote:
> >
> >> Jim
> >>
> >> The symptoms seem identical. I cannot guarantee it is the exact bug
> >> because
> >> I have not seen the bug in action; only reports via the newsgroups.
> >>
> >> Terry
> >>
> >> "Jim Scrivener" <JimScrivener.RemoveThis@discussions.microsoft.com> wrote in message
> >> news:581455B7-6734-4C88-A422-B854B1B58128@microsoft.com...
> >> > Really? That's excellent news if true.
> >> >
> >> > But ... How on earth are they going to mend a bug that seems to be
> >> > hardly
> >> > reported and only affects a few people? That presumes they know it
> >> > exists
> >> > and
> >> > what causes it - but this seems to be something that only hits a very
> >> > small
> >> > number of users and there is no hint anywhere else on the web of any
> >> > kind
> >> > of
> >> > reason or cure.
> >> >
> >> > Are you sure it's precisely this problem and not similar issues that
> >> > the
> >> > fix
> >> > will mend?
> >> >
> >> >
> >> > Jim
> >> >
> >> > "Terry Farrell" wrote:
> >> >
> >> >> The bug will be fixed with SP1 which is currently under test. The
> >> >> release
> >> >> should be soon.
> >> >>
> >> >> --
> >> >> Terry Farrell - MS Word MVP
> >> >
> >>
> >>
>

Terry, I can further confirm that this problem does NOT exist between Office
2007 and XP. It ONLY exists between Vista and Office 2007. I have used my
laptop as my "mobile device," and my desktop as my "registered device" per
the Office 2007 EULA - my desktop is XP, and laptop is Vista. Both PCs have
all windowsupdate.com updates, and the desktop has several others that people
that have never heard of TechNet don't know exist...

Furthermore, the problem also does not exist with Access database files. I
have not tried other Office programs, other than Access and Word yet. The
error occurrs exactly as described by David above, with Word, on the Vista OS.

Is there any way to get a verification, other than an assumption, that this
problem is to be resolved, or for that matter, a work around until it does?
Don't get me wrong - it is fantastic that you are helping, but we all know
the definition of ASSUME.

Michael

"David" wrote:

> I can't say I'm confident this problem will be fixed by SP1. I'm desperate
> for help from someone - it is such a terrible bug in Vista!!!
>
> Help!!!!!
>
> "Terry Farrell" wrote:
>
> > David
> >
> > SP1 for Vista is under test too: solely a guess that both Office and Vista
> > SP1s will be out together. The fix list for Vista is massive - but I only
> > saw a preview, so I have no idea what will be in the final package.
> >
> > Terry
> >
> > "David" <David DeleteThis @discussions.microsoft.com> wrote in message
> > news:F1B789EE-FC20-41D3-9D6E-8CB011EE36E9@microsoft.com...
> > >
> > > Hi there, I'm the guy who raised this issue in the first place on a couple
> > > of MS forums, and got no satisfactory answert.
> > >
> > > I can confirm that it's nothing to do with AV software. If I disable it, I
> > > still get the problem.
> > >
> > > I can also confirm that the problem is not to do with Word 2007, but with
> > > Vista Explorer. I get the problem whenever I try to open a Word or htm
> > > file
> > > *before* I've opened the associated application (Word or Firefox). If I
> > > double click the file in Explorer, I get 'Windows cannot find the file
> > > specified etc. etc.'.
> > >
> > > If I open the program, e.g. Word or Firefox, and *then* click the file in
> > > Explorer, it opens fine. I can also open the file *within* the program
> > > using
> > > File/Open.
> > >
> > > I've tried everything. I sure as heck don't want to reinstall Vista, so if
> > > it's true that SP1 will solve the problem I'll be very happy. But I share
> > > the scepticism, since it only seems to affect a small no. of users, so
> > > are
> > > Microsoft really dealing with it?
> > >
> > > Can some kind person please verify that SP1 really will deal with this
> > > hideously annoying problem?
> > >
> > > Many thanks,
> > > David
> > >
> > >
> > >
> > > "Terry Farrell" wrote:
> > >
> > >> Jim
> > >>
> > >> The symptoms seem identical. I cannot guarantee it is the exact bug
> > >> because
> > >> I have not seen the bug in action; only reports via the newsgroups.
> > >>
> > >> Terry
> > >>
> > >> "Jim Scrivener" <JimScrivener DeleteThis @discussions.microsoft.com> wrote in message
> > >> news:581455B7-6734-4C88-A422-B854B1B58128@microsoft.com...
> > >> > Really? That's excellent news if true.
> > >> >
> > >> > But ... How on earth are they going to mend a bug that seems to be
> > >> > hardly
> > >> > reported and only affects a few people? That presumes they know it
> > >> > exists
> > >> > and
> > >> > what causes it - but this seems to be something that only hits a very
> > >> > small
> > >> > number of users and there is no hint anywhere else on the web of any
> > >> > kind
> > >> > of
> > >> > reason or cure.
> > >> >
> > >> > Are you sure it's precisely this problem and not similar issues that
> > >> > the
> > >> > fix
> > >> > will mend?
> > >> >
> > >> >
> > >> > Jim
> > >> >
> > >> > "Terry Farrell" wrote:
> > >> >
> > >> >> The bug will be fixed with SP1 which is currently under test. The
> > >> >> release
> > >> >> should be soon.
> > >> >>
> > >> >> --
> > >> >> Terry Farrell - MS Word MVP
> > >> >
> > >>
> > >>
> >