Bill Sanderson's Installation Fix

I had a problem installing Defender - the .msi opened in wordpad and
displayed garbage. Bill posted a fix for this on 3/24 and it worked great.
Bill also offerd a fix for restoring the default .msi association. This
information is in the thread "Theres an error when installing Windows ...",
dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link which
is not displayed. If anyone (Bill ?) has the link location can you please
post it here? Thanks.

Thanks for reminding me about that thread--let me see if I can find it.

--

"delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
>I had a problem installing Defender - the .msi opened in wordpad and
> displayed garbage. Bill posted a fix for this on 3/24 and it worked
> great.
> Bill also offerd a fix for restoring the default .msi association. This
> information is in the thread "Theres an error when installing Windows
> ...",
> dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link
> which
> is not displayed. If anyone (Bill ?) has the link location can you please
> post it here? Thanks.

Thanks--not sure what happened to the link in that post--did I just forget
to put it in there?

http://www.dougknox.com/xp/fileassoc/msi_assoc.zip

This is the file I meant to point to. As I recall, I had some minor
difficulties making it work--maybe it worked in c:\, but it didn't work on
the desktop--something odd like that.

Try it out and let me know what happens--should be simple and quick.

--

"delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
>I had a problem installing Defender - the .msi opened in wordpad and
> displayed garbage. Bill posted a fix for this on 3/24 and it worked
> great.
> Bill also offerd a fix for restoring the default .msi association. This
> information is in the thread "Theres an error when installing Windows
> ...",
> dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link
> which
> is not displayed. If anyone (Bill ?) has the link location can you please
> post it here? Thanks.

I got the file, unzipped it and placed it in the c: root in windows explorer.
When I ran the program a notepad window opened with a listing of the values
for the .msi package. Since this didn't seem like the desired result I ran
regedit.exe from a command prompt and imported the msi1.reg (dougknox's
file). Windows told me the file was already in the registry. I assume this
means your suggestion worked, however your quick fix for installing Defender
was successful so I don't have any way to test it.

"Bill Sanderson MVP" wrote:

> Thanks--not sure what happened to the link in that post--did I just forget
> to put it in there?
>
> http://www.dougknox.com/xp/fileassoc/msi_assoc.zip
>
> This is the file I meant to point to. As I recall, I had some minor
> difficulties making it work--maybe it worked in c:\, but it didn't work on
> the desktop--something odd like that.
>
> Try it out and let me know what happens--should be simple and quick.
>
> --
>
> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
> news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
> >I had a problem installing Defender - the .msi opened in wordpad and
> > displayed garbage. Bill posted a fix for this on 3/24 and it worked
> > great.
> > Bill also offerd a fix for restoring the default .msi association. This
> > information is in the thread "Theres an error when installing Windows
> > ...",
> > dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link
> > which
> > is not displayed. If anyone (Bill ?) has the link location can you please
> > post it here? Thanks.
>
>
>

Hmm - I think you've changed the association with .reg files to
Notepad--this may be done as a safety valve by some software--not sure. at
any rate, importing the info in that file to the registry is the "fix."

If you can double click on a .msi file and have it install--you're fixed.

--

"delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
news:7F0361EA-F527-4818-96EC-928B61B5E50B@microsoft.com...
>I got the file, unzipped it and placed it in the c: root in windows
>explorer.
> When I ran the program a notepad window opened with a listing of the
> values
> for the .msi package. Since this didn't seem like the desired result I
> ran
> regedit.exe from a command prompt and imported the msi1.reg (dougknox's
> file). Windows told me the file was already in the registry. I assume
> this
> means your suggestion worked, however your quick fix for installing
> Defender
> was successful so I don't have any way to test it.
>
> "Bill Sanderson MVP" wrote:
>
>> Thanks--not sure what happened to the link in that post--did I just
>> forget
>> to put it in there?
>>
>> http://www.dougknox.com/xp/fileassoc/msi_assoc.zip
>>
>> This is the file I meant to point to. As I recall, I had some minor
>> difficulties making it work--maybe it worked in c:\, but it didn't work
>> on
>> the desktop--something odd like that.
>>
>> Try it out and let me know what happens--should be simple and quick.
>>
>> --
>>
>> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in
>> message
>> news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
>> >I had a problem installing Defender - the .msi opened in wordpad and
>> > displayed garbage. Bill posted a fix for this on 3/24 and it worked
>> > great.
>> > Bill also offerd a fix for restoring the default .msi association. This
>> > information is in the thread "Theres an error when installing Windows
>> > ...",
>> > dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link
>> > which
>> > is not displayed. If anyone (Bill ?) has the link location can you
>> > please
>> > post it here? Thanks.
>>
>>
>>

Thanks Bill, you're my hero. The Defender .msi opens all by itself now, no
command line necessary. I've been working with Microsoft over a week to get
Defender installed and will pass along this thread to them. I noticed
www.dougknox.com has other file association fixes as well. Perhaps a .reg
fix is available. I would be nice if a file association check could be
included in the Live Care tune up. Again, thanks for the great help.

"Bill Sanderson MVP" wrote:

> Hmm - I think you've changed the association with .reg files to
> Notepad--this may be done as a safety valve by some software--not sure. at
> any rate, importing the info in that file to the registry is the "fix."
>
> If you can double click on a .msi file and have it install--you're fixed.
>
> --
>
> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
> news:7F0361EA-F527-4818-96EC-928B61B5E50B@microsoft.com...
> >I got the file, unzipped it and placed it in the c: root in windows
> >explorer.
> > When I ran the program a notepad window opened with a listing of the
> > values
> > for the .msi package. Since this didn't seem like the desired result I
> > ran
> > regedit.exe from a command prompt and imported the msi1.reg (dougknox's
> > file). Windows told me the file was already in the registry. I assume
> > this
> > means your suggestion worked, however your quick fix for installing
> > Defender
> > was successful so I don't have any way to test it.
> >
> > "Bill Sanderson MVP" wrote:
> >
> >> Thanks--not sure what happened to the link in that post--did I just
> >> forget
> >> to put it in there?
> >>
> >> http://www.dougknox.com/xp/fileassoc/msi_assoc.zip
> >>
> >> This is the file I meant to point to. As I recall, I had some minor
> >> difficulties making it work--maybe it worked in c:\, but it didn't work
> >> on
> >> the desktop--something odd like that.
> >>
> >> Try it out and let me know what happens--should be simple and quick.
> >>
> >> --
> >>
> >> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in
> >> message
> >> news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
> >> >I had a problem installing Defender - the .msi opened in wordpad and
> >> > displayed garbage. Bill posted a fix for this on 3/24 and it worked
> >> > great.
> >> > Bill also offerd a fix for restoring the default .msi association. This
> >> > information is in the thread "Theres an error when installing Windows
> >> > ...",
> >> > dated 3/22/2006. Unfortunately part of Bill's permanant fix was a link
> >> > which
> >> > is not displayed. If anyone (Bill ?) has the link location can you
> >> > please
> >> > post it here? Thanks.
> >>
> >>
> >>
>
>
>

Great--I think it is likely a fix for .REG association is present on Doug
Knox' site--as I say--the way your machine is set up may well be
intentional, as a "safety catch." Many users find it disquieting that
double-clicking on a .reg file and responding to a prompt triggers an change
to the registry which can't easily be reversed. So I know that some folks
advocate changing the association in exactly the way it is on your
system--so that you can see what's in the file, safely, in notepad.

--

"delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in message
news:6F2C1ABC-22A0-40A8-80D1-536664493A2F@microsoft.com...
> Thanks Bill, you're my hero. The Defender .msi opens all by itself now,
> no
> command line necessary. I've been working with Microsoft over a week to
> get
> Defender installed and will pass along this thread to them. I noticed
> www.dougknox.com has other file association fixes as well. Perhaps a .reg
> fix is available. I would be nice if a file association check could be
> included in the Live Care tune up. Again, thanks for the great help.
>
> "Bill Sanderson MVP" wrote:
>
>> Hmm - I think you've changed the association with .reg files to
>> Notepad--this may be done as a safety valve by some software--not sure.
>> at
>> any rate, importing the info in that file to the registry is the "fix."
>>
>> If you can double click on a .msi file and have it install--you're fixed.
>>
>> --
>>
>> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in
>> message
>> news:7F0361EA-F527-4818-96EC-928B61B5E50B@microsoft.com...
>> >I got the file, unzipped it and placed it in the c: root in windows
>> >explorer.
>> > When I ran the program a notepad window opened with a listing of the
>> > values
>> > for the .msi package. Since this didn't seem like the desired result I
>> > ran
>> > regedit.exe from a command prompt and imported the msi1.reg (dougknox's
>> > file). Windows told me the file was already in the registry. I assume
>> > this
>> > means your suggestion worked, however your quick fix for installing
>> > Defender
>> > was successful so I don't have any way to test it.
>> >
>> > "Bill Sanderson MVP" wrote:
>> >
>> >> Thanks--not sure what happened to the link in that post--did I just
>> >> forget
>> >> to put it in there?
>> >>
>> >> http://www.dougknox.com/xp/fileassoc/msi_assoc.zip
>> >>
>> >> This is the file I meant to point to. As I recall, I had some minor
>> >> difficulties making it work--maybe it worked in c:\, but it didn't
>> >> work
>> >> on
>> >> the desktop--something odd like that.
>> >>
>> >> Try it out and let me know what happens--should be simple and quick.
>> >>
>> >> --
>> >>
>> >> "delivertoaaron" <delivertoaaron@discussions.microsoft.com> wrote in
>> >> message
>> >> news:C02F851F-8E84-44F4-B50F-225137063F23@microsoft.com...
>> >> >I had a problem installing Defender - the .msi opened in wordpad and
>> >> > displayed garbage. Bill posted a fix for this on 3/24 and it worked
>> >> > great.
>> >> > Bill also offerd a fix for restoring the default .msi association.
>> >> > This
>> >> > information is in the thread "Theres an error when installing
>> >> > Windows
>> >> > ...",
>> >> > dated 3/22/2006. Unfortunately part of Bill's permanant fix was a
>> >> > link
>> >> > which
>> >> > is not displayed. If anyone (Bill ?) has the link location can you
>> >> > please
>> >> > post it here? Thanks.
>> >>
>> >>
>> >>
>>
>>
>>