What is bf7af.msd?

[Dutchm@n]

I have a problem with the following corrupt file:

Location: Windows | Installer(hidden folder) |
bf7af.msp 14.230Mb dated 2002-08-02

The info balloon tells me:
Office XP hotfix patch MainSP2... etc
but not its origin.

During backup of my C drive there are complaints
about it being corrupt and cannot be restored.
Defrag also does not like it and hangs on it.

What was its origin?
Do I still need that?
Can it be deleted?
Or where / how can I get a good copy?

Thanks

 

[R. C. White]

Hi, Dutchm@n.

I can't help with this one, but I can add a couple of data points in case
they might help in your research:

Google gets NO hits on either bf7af.msd OR bf7af.msp. My WinXP Pro, running
Office 2003, has no bf7af.* files, either in \Windows or in \Program
Files\Microsoft Office, including their subfolders.

RC

 

[Dutchm@n]

Thanks for the reply,

Sorry about the msd typo in the title of this posting.

I don't know how conversant you are with these matters, but
firstly, make sure Explorer is showing hidden files with:
TOOLS | FOLDER OPTIONS | VIEW tab
then tick box with "show hidden files and folders"

In WINDOWS | INSTALLER
I have found some more Office hotfix installer files, probably
downloaded from MS website at various times in the past:

48c93c .msp
48c951 "
90fddd "
90fdf2 "
90fe1c "
90fe06 "
bf7af "
bf77e "

I think each are installers in their own right with update file
content as when you click on one, an install info window comes
up asking you to proceed etc.

It is only bf7af that is causing trouble and I am wondering if I
should not just delete it, go back to the MSOffce site and see
if it can detect what I need and simply do a download.

I would prefer to know exactly to what update it is referenced
ie: KBxxxxxx

HK


| Hi, Dutchm@n.
|
| I can't help with this one, but I can add a couple of data points in
case
| they might help in your research:
|
| Google gets NO hits on either bf7af.msd OR bf7af.msp. My WinXP Pro,
running
| Office 2003, has no bf7af.* files, either in \Windows or in \Program
| Files\Microsoft Office, including their subfolders.
|
| RC
| --
| R. C. White, CPA
| San Marcos, TX
| (e-mail address removed)
| Microsoft Windows MVP
|
| | > I have a problem with the following corrupt file:
| >
| > Location: Windows | Installer(hidden folder) |
| > bf7af.msp 14.230Mb dated 2002-08-02
| >
| > The info balloon tells me:
| > Office XP hotfix patch MainSP2... etc
| > but not its origin.
| >
| > During backup of my C drive there are complaints
| > about it being corrupt and cannot be restored.
| > Defrag also does not like it and hangs on it.
| >
| > What was its origin?
| > Do I still need that?
| > Can it be deleted?
| > Or where / how can I get a good copy?
| >
| > Thanks
|
|

 

[Gary Smith]

In WINDOWS | INSTALLER
I have found some more Office hotfix installer files, probably
downloaded from MS website at various times in the past:

48c93c .msp
48c951 "
90fddd "
90fdf2 "
90fe1c "
90fe06 "
bf7af "
bf77e "

I think each are installers in their own right with update file
content as when you click on one, an install info window comes
up asking you to proceed etc.

It is only bf7af that is causing trouble and I am wondering if I
should not just delete it, go back to the MSOffce site and see
if it can detect what I need and simply do a download.

Based on investigation into similar files on my system, I'm reasonably
certain that these files are needed only for installing and possibly
uninstalling components and patches. I think you can delete it. I'd make
a backup copy somewhere if possible, delete the file, and then watch to
see if anything peculair happens.

 

[Dutchm@n]

Gary, I put my foot in it and deleted the file. It will not copy.
Then went to MSoffice update site and requested an install detect.
This failed on the spot due to a probable incomplete or missing
..msp files problem.
Clever stuff..
Then went to "you choose download" and explained my problem in a
mail window.
Now waiting in suspense..



| > In WINDOWS | INSTALLER
| > I have found some more Office hotfix installer files, probably
| > downloaded from MS website at various times in the past:
|
| > 48c93c .msp
| > 48c951 "
| > 90fddd "
| > 90fdf2 "
| > 90fe1c "
| > 90fe06 "
| > bf7af "
| > bf77e "
|
| > I think each are installers in their own right with update file
| > content as when you click on one, an install info window comes
| > up asking you to proceed etc.
|
| > It is only bf7af that is causing trouble and I am wondering if I
| > should not just delete it, go back to the MSOffce site and see
| > if it can detect what I need and simply do a download.
|
| Based on investigation into similar files on my system, I'm reasonably
| certain that these files are needed only for installing and possibly
| uninstalling components and patches. I think you can delete it. I'd
make
| a backup copy somewhere if possible, delete the file, and then watch
to
| see if anything peculair happens.
|
| --
| Gary L. Smith (e-mail address removed)
| Columbus, Ohio

 

[Dutchm@n]

Stop Press.... Solved the problem with ignorance and luck....
I had already deleted the file from the Trash.
Norton unerase could not find or recover it but Ontrack found
about a hundred files that could be recovered.
The exact filename was not there but looking at filesize 13mb
I found a file with a cryptic name but with a .msp extension.
The info balloon confirmed the correct content.
I pressed Recover File and after a search found it in a Temp
subfile in Documents and Settings.
I moved it to the Installer folder and renamed it bf7af.msp
and voila: it was back where it should be and clicking on it
produced a non-scratching hdd and a no-problem-self-executing
install screen which I then aborted.
Going back to the MSOffice website, I found MS to be happy now
and I got my list of already installed updates and don't need any
updates.
Conclusion: Some pgms may have perceived the file as corrupt and
given me a hard time. Apparently it was not and possibly on a
bad hdd location? It must surely now be written to another
location.
I'll leave at that for the time being.


| Gary, I put my foot in it and deleted the file. It will not copy.
| Then went to MSoffice update site and requested an install detect.
| This failed on the spot due to a probable incomplete or missing
| .msp files problem.
| Clever stuff..
| Then went to "you choose download" and explained my problem in a
| mail window.
| Now waiting in suspense..
|
|
|
| | | > In WINDOWS | INSTALLER
| | > I have found some more Office hotfix installer files, probably
| | > downloaded from MS website at various times in the past:
| |
| | > 48c93c .msp
| | > 48c951 "
| | > 90fddd "
| | > 90fdf2 "
| | > 90fe1c "
| | > 90fe06 "
| | > bf7af "
| | > bf77e "
| |
| | > I think each are installers in their own right with update file
| | > content as when you click on one, an install info window comes
| | > up asking you to proceed etc.
| |
| | > It is only bf7af that is causing trouble and I am wondering if I
| | > should not just delete it, go back to the MSOffce site and see
| | > if it can detect what I need and simply do a download.
| |
| | Based on investigation into similar files on my system, I'm
reasonably
| | certain that these files are needed only for installing and possibly
| | uninstalling components and patches. I think you can delete it.
I'd
| make
| | a backup copy somewhere if possible, delete the file, and then watch
| to
| | see if anything peculair happens.
| |
| | --
| | Gary L. Smith (e-mail address removed)
| | Columbus, Ohio
|
|

 

[Gary Smith]

Conclusion: Some pgms may have perceived the file as corrupt and
given me a hard time. Apparently it was not and possibly on a
bad hdd location? It must surely now be written to another
location.

I think you're right -- it was a hardware problem. What I'd do next is to
run every disk diagnostic I had access to, attempting to find out whether
this is an isolated incident or the preview of bigger proglems to come.

 

[Dutchm@n]

Gary thanks for the moral support.
Tried all the disk test utilities I have and all are happy.
Gremlins so early in the year? Time will tell..

| > Conclusion: Some pgms may have perceived the file as corrupt and
| > given me a hard time. Apparently it was not and possibly on a
| > bad hdd location? It must surely now be written to another
| > location.
|
| I think you're right -- it was a hardware problem. What I'd do next
is to
| run every disk diagnostic I had access to, attempting to find out
whether
| this is an isolated incident or the preview of bigger proglems to
come.
|
| --
| Gary L. Smith (e-mail address removed)
| Columbus, Ohio