Fixed my KB967715 issue 99.99% sure.

I am posting this in case it can help others. It is a bit winded but I wrote
it the best way I could explain it.

After reading many posts including replies to my own posts I have put
together my own method to install this darn thing and it seems to have
worked.

First of all why I think it worked even though I just did this tonight. I
know many of you install it and it returns to auto updates the next day. I
however have been installing it from the Windows update site and then
immediately afterwords would go and see if it was offered again which it
always was. After my attempt tonight the update is not offered at the
Windows update site any more.

First before I give my solution I would like to thank everyone that has
answered posts about this because all of the information combined gave me
the solution that worked for me. Without all of those other replies I would
not have come up with this on my own.

I think this is even easy enough for a fairly novice user to follow and not
even mess with the registry.

The problem on my computer was related to DLA (Drive Letter Access), many
will know what this is but some will not. For those that do not, what DLA
does is allows you to insert a cdrw disc into your cd writer and write and
erase data on it just like you would your hard drive. Most people do not do
that, especially with the advent of Flash Drives. So if you do not use DLA
my solution should work and you will not even have to uninstall anything
from your machine.

Please note DLA can be listed in your add remove programs list as different
brands. The main brand name is Roxio DLA however some OEM vendors have a
factory installed version called Sonic DLA as was the case with my machine.

Now here is what I did.

I disabled DLA from starting on my computer using the "System Configuration
Utility" (msconfig).

For those that do not know this tool I will give step by step instructions
below. For everyone else I am just trying to make it easy for those that
don't know.

Here goes.
Once your computer is all booted up click start then click the icon that
says run. In the box that pops up type the word between quotes "msconfig"
then click ok.

You will see a row of tabs with various names on them. Click the one that
says Startup.

In the list look for look down the left side under Startup Item for
something called "DLACTRLW". If you find this click the box with the check
mark to make the check mark go away.

Click apply and ok to let your computer reboot.

This will stop DLA from running when you restart your computer.

Once you computer has rebooted then you will get a new message that tells
you that you have used the System Configuration Utility to make changes to
the way Windows starts. There will be a box to check that says don't show
this message again. Put a check mark in that box and click ok.

Now go to the Windows update site and install the update. Let the computer
restart then go back to the Windows update site and you should find that the
update is not offered anymore.

Please note that I did not look at the registry key after turning off DLA
but after doing the install with it off the "HonorAutoRunSetting" key now
exists and the key that was there called "NoCDBurning" is gone. I am not
sure at this moment if turning off DLA removed the key or if it was removed
when the update installed. I however do believe it disappeared when the DLA
was turned off.

Now for a final note. I have not returned to "msconfig" and put a check back
in "DLACTRLW" to re-enable it because I do not use DLA so I just left it
turned off, therefore I can not state with any facts that if your were to
return to "msconfig" and re-enable "DLACTRLW" that the "HonorAutoRunSetting"
would remain and that the "NoCDBurning" would not return.

If you do turn DLA back on and "HonorAutoRunSetting" disappears you will
once again be prompted to reinstall KB967715. But if you were prompted again
you could turn off DLA and install the update again.

If anyone wants turn DLA back on after a successful install I would suggest
to wait a day or two so you know if it is installed correctly before turning
DLA back on. Then reply to this thread and let us all know what happened
when you attempted to turn it back on.

For the non techie's reading this you should not go beyond this point of
this post.

For those curious to explore the registry and I don't suggest it except for
experienced users who already know how to get into the registry.

I figure turning DLA back on will cause one of the two following things to
happen:

1. "NoCDBurning" will return in the registry and "HonorAutoRunSetting" will
remain and you will not be prompted to install again.

Or

2. NoCDBurning" will return in the registry and "HonorAutoRunSetting" will
be deleted and you will be prompted to install again.

I hope this helps others to achieve a machine that is not bugging to install
this update anymore.

Ohno wrote:

> The problem on my computer was related to DLA (Drive Letter Access), many
> will know what this is but some will not.

OK, now that's just bizarre. Why on earth would DLA software interfere with the
ability of a Windows update to set a registry value?

(I'm not doubting your report, by the way; I'm just shocked at how badly that
software must have been written.)

If I get a chance, I'll see if I've got a copy of Sonic DLA floating around and
if so, try to reproduce the problem - just out of curiosity, you understand,
since it's such a particularly oddball problem. :-)

Harry.

> For those that do not, what DLA
> does is allows you to insert a cdrw disc into your cd writer and write and
> erase data on it just like you would your hard drive. Most people do not do
> that, especially with the advent of Flash Drives. So if you do not use DLA
> my solution should work and you will not even have to uninstall anything
> from your machine.
>
> Please note DLA can be listed in your add remove programs list as different
> brands. The main brand name is Roxio DLA however some OEM vendors have a
> factory installed version called Sonic DLA as was the case with my machine.
>
> Now here is what I did.
>
> I disabled DLA from starting on my computer using the "System Configuration
> Utility" (msconfig).
>
> For those that do not know this tool I will give step by step instructions
> below. For everyone else I am just trying to make it easy for those that
> don't know.
>
> Here goes.
> Once your computer is all booted up click start then click the icon that
> says run. In the box that pops up type the word between quotes "msconfig"
> then click ok.
>
> You will see a row of tabs with various names on them. Click the one that
> says Startup.
>
> In the list look for look down the left side under Startup Item for
> something called "DLACTRLW". If you find this click the box with the check
> mark to make the check mark go away.
>
> Click apply and ok to let your computer reboot.
>
> This will stop DLA from running when you restart your computer.
>
> Once you computer has rebooted then you will get a new message that tells
> you that you have used the System Configuration Utility to make changes to
> the way Windows starts. There will be a box to check that says don't show
> this message again. Put a check mark in that box and click ok.
>
> Now go to the Windows update site and install the update. Let the computer
> restart then go back to the Windows update site and you should find that the
> update is not offered anymore.
>
> Please note that I did not look at the registry key after turning off DLA
> but after doing the install with it off the "HonorAutoRunSetting" key now
> exists and the key that was there called "NoCDBurning" is gone. I am not
> sure at this moment if turning off DLA removed the key or if it was removed
> when the update installed. I however do believe it disappeared when the DLA
> was turned off.
>
> Now for a final note. I have not returned to "msconfig" and put a check back
> in "DLACTRLW" to re-enable it because I do not use DLA so I just left it
> turned off, therefore I can not state with any facts that if your were to
> return to "msconfig" and re-enable "DLACTRLW" that the "HonorAutoRunSetting"
> would remain and that the "NoCDBurning" would not return.
>
> If you do turn DLA back on and "HonorAutoRunSetting" disappears you will
> once again be prompted to reinstall KB967715. But if you were prompted again
> you could turn off DLA and install the update again.
>
> If anyone wants turn DLA back on after a successful install I would suggest
> to wait a day or two so you know if it is installed correctly before turning
> DLA back on. Then reply to this thread and let us all know what happened
> when you attempted to turn it back on.
>
> For the non techie's reading this you should not go beyond this point of
> this post.
>
> For those curious to explore the registry and I don't suggest it except for
> experienced users who already know how to get into the registry.
>
> I figure turning DLA back on will cause one of the two following things to
> happen:
>
> 1. "NoCDBurning" will return in the registry and "HonorAutoRunSetting" will
> remain and you will not be prompted to install again.
>
> Or
>
> 2. NoCDBurning" will return in the registry and "HonorAutoRunSetting" will
> be deleted and you will be prompted to install again.
>
> I hope this helps others to achieve a machine that is not bugging to install
> this update anymore.
>
>

Harry;

I actually got the DLA tip from another thread by Engel in this news group
that pointed me here.

http://aumha.net:80/viewtopic.php?f=62&t=38665

That is when I tried my install by simply disabling DLA in msconfig. So in
this case it took many heads to solve this issue.

Along with the information in the above link and the information provided by
MVP's MowGreen and Pa Bear about the registry key that should be created and
exist when this update is installed, is what prompted me to make my attempt
at getting this thing installed the way I did.

"Harry Johnston [MVP]" <> wrote in message
news:...
> Ohno wrote:
>
>> The problem on my computer was related to DLA (Drive Letter Access), many
>> will know what this is but some will not.
>
> OK, now that's just bizarre. Why on earth would DLA software interfere
> with the ability of a Windows update to set a registry value?
>
> (I'm not doubting your report, by the way; I'm just shocked at how badly
> that software must have been written.)
>
> If I get a chance, I'll see if I've got a copy of Sonic DLA floating
> around and if so, try to reproduce the problem - just out of curiosity,
> you understand, since it's such a particularly oddball problem. :-)
>
> Harry.
>
>> For those that do not, what DLA does is allows you to insert a cdrw disc
>> into your cd writer and write and erase data on it just like you would
>> your hard drive. Most people do not do that, especially with the advent
>> of Flash Drives. So if you do not use DLA my solution should work and you
>> will not even have to uninstall anything from your machine.
>>
>> Please note DLA can be listed in your add remove programs list as
>> different brands. The main brand name is Roxio DLA however some OEM
>> vendors have a factory installed version called Sonic DLA as was the case
>> with my machine.
>>
>> Now here is what I did.
>>
>> I disabled DLA from starting on my computer using the "System
>> Configuration Utility" (msconfig).
>>
>> For those that do not know this tool I will give step by step
>> instructions below. For everyone else I am just trying to make it easy
>> for those that don't know.
>>
>> Here goes.
>> Once your computer is all booted up click start then click the icon that
>> says run. In the box that pops up type the word between quotes
>> "msconfig" then click ok.
>>
>> You will see a row of tabs with various names on them. Click the one that
>> says Startup.
>>
>> In the list look for look down the left side under Startup Item for
>> something called "DLACTRLW". If you find this click the box with the
>> check mark to make the check mark go away.
>>
>> Click apply and ok to let your computer reboot.
>>
>> This will stop DLA from running when you restart your computer.
>>
>> Once you computer has rebooted then you will get a new message that tells
>> you that you have used the System Configuration Utility to make changes
>> to the way Windows starts. There will be a box to check that says don't
>> show this message again. Put a check mark in that box and click ok.
>>
>> Now go to the Windows update site and install the update. Let the
>> computer restart then go back to the Windows update site and you should
>> find that the update is not offered anymore.
>>
>> Please note that I did not look at the registry key after turning off DLA
>> but after doing the install with it off the "HonorAutoRunSetting" key now
>> exists and the key that was there called "NoCDBurning" is gone. I am not
>> sure at this moment if turning off DLA removed the key or if it was
>> removed when the update installed. I however do believe it disappeared
>> when the DLA was turned off.
>>
>> Now for a final note. I have not returned to "msconfig" and put a check
>> back in "DLACTRLW" to re-enable it because I do not use DLA so I just
>> left it turned off, therefore I can not state with any facts that if your
>> were to return to "msconfig" and re-enable "DLACTRLW" that the
>> "HonorAutoRunSetting" would remain and that the "NoCDBurning" would not
>> return.
>>
>> If you do turn DLA back on and "HonorAutoRunSetting" disappears you will
>> once again be prompted to reinstall KB967715. But if you were prompted
>> again you could turn off DLA and install the update again.
>>
>> If anyone wants turn DLA back on after a successful install I would
>> suggest to wait a day or two so you know if it is installed correctly
>> before turning DLA back on. Then reply to this thread and let us all know
>> what happened when you attempted to turn it back on.
>>
>> For the non techie's reading this you should not go beyond this point of
>> this post.
>>
>> For those curious to explore the registry and I don't suggest it except
>> for experienced users who already know how to get into the registry.
>>
>> I figure turning DLA back on will cause one of the two following things
>> to happen:
>>
>> 1. "NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>> will remain and you will not be prompted to install again.
>>
>> Or
>>
>> 2. NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>> will be deleted and you will be prompted to install again.
>>
>> I hope this helps others to achieve a machine that is not bugging to
>> install this update anymore.

I almost forgot there was another post I had read somewhere that the reg key
was getting created and then removed on reboot. That poster is also
responsible for helping with this issue as I used that as part of my test to
watch when installing my way.

That poster was wayne.royal.


"Ohno" <> wrote in message
news:...
> Harry;
>
> I actually got the DLA tip from another thread by Engel in this news group
> that pointed me here.
>
> http://aumha.net:80/viewtopic.php?f=62&t=38665
>
> That is when I tried my install by simply disabling DLA in msconfig. So in
> this case it took many heads to solve this issue.
>
> Along with the information in the above link and the information provided
> by MVP's MowGreen and Pa Bear about the registry key that should be
> created and exist when this update is installed, is what prompted me to
> make my attempt at getting this thing installed the way I did.
>
> "Harry Johnston [MVP]" <> wrote in message
> news:...
>> Ohno wrote:
>>
>>> The problem on my computer was related to DLA (Drive Letter Access),
>>> many will know what this is but some will not.
>>
>> OK, now that's just bizarre. Why on earth would DLA software interfere
>> with the ability of a Windows update to set a registry value?
>>
>> (I'm not doubting your report, by the way; I'm just shocked at how badly
>> that software must have been written.)
>>
>> If I get a chance, I'll see if I've got a copy of Sonic DLA floating
>> around and if so, try to reproduce the problem - just out of curiosity,
>> you understand, since it's such a particularly oddball problem. :-)
>>
>> Harry.
>>
>>> For those that do not, what DLA does is allows you to insert a cdrw disc
>>> into your cd writer and write and erase data on it just like you would
>>> your hard drive. Most people do not do that, especially with the advent
>>> of Flash Drives. So if you do not use DLA my solution should work and
>>> you will not even have to uninstall anything from your machine.
>>>
>>> Please note DLA can be listed in your add remove programs list as
>>> different brands. The main brand name is Roxio DLA however some OEM
>>> vendors have a factory installed version called Sonic DLA as was the
>>> case with my machine.
>>>
>>> Now here is what I did.
>>>
>>> I disabled DLA from starting on my computer using the "System
>>> Configuration Utility" (msconfig).
>>>
>>> For those that do not know this tool I will give step by step
>>> instructions below. For everyone else I am just trying to make it easy
>>> for those that don't know.
>>>
>>> Here goes.
>>> Once your computer is all booted up click start then click the icon that
>>> says run. In the box that pops up type the word between quotes
>>> "msconfig" then click ok.
>>>
>>> You will see a row of tabs with various names on them. Click the one
>>> that says Startup.
>>>
>>> In the list look for look down the left side under Startup Item for
>>> something called "DLACTRLW". If you find this click the box with the
>>> check mark to make the check mark go away.
>>>
>>> Click apply and ok to let your computer reboot.
>>>
>>> This will stop DLA from running when you restart your computer.
>>>
>>> Once you computer has rebooted then you will get a new message that
>>> tells you that you have used the System Configuration Utility to make
>>> changes to the way Windows starts. There will be a box to check that
>>> says don't show this message again. Put a check mark in that box and
>>> click ok.
>>>
>>> Now go to the Windows update site and install the update. Let the
>>> computer restart then go back to the Windows update site and you should
>>> find that the update is not offered anymore.
>>>
>>> Please note that I did not look at the registry key after turning off
>>> DLA but after doing the install with it off the "HonorAutoRunSetting"
>>> key now exists and the key that was there called "NoCDBurning" is gone.
>>> I am not sure at this moment if turning off DLA removed the key or if it
>>> was removed when the update installed. I however do believe it
>>> disappeared when the DLA was turned off.
>>>
>>> Now for a final note. I have not returned to "msconfig" and put a check
>>> back in "DLACTRLW" to re-enable it because I do not use DLA so I just
>>> left it turned off, therefore I can not state with any facts that if
>>> your were to return to "msconfig" and re-enable "DLACTRLW" that the
>>> "HonorAutoRunSetting" would remain and that the "NoCDBurning" would not
>>> return.
>>>
>>> If you do turn DLA back on and "HonorAutoRunSetting" disappears you will
>>> once again be prompted to reinstall KB967715. But if you were prompted
>>> again you could turn off DLA and install the update again.
>>>
>>> If anyone wants turn DLA back on after a successful install I would
>>> suggest to wait a day or two so you know if it is installed correctly
>>> before turning DLA back on. Then reply to this thread and let us all
>>> know what happened when you attempted to turn it back on.
>>>
>>> For the non techie's reading this you should not go beyond this point of
>>> this post.
>>>
>>> For those curious to explore the registry and I don't suggest it except
>>> for experienced users who already know how to get into the registry.
>>>
>>> I figure turning DLA back on will cause one of the two following things
>>> to happen:
>>>
>>> 1. "NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>>> will remain and you will not be prompted to install again.
>>>
>>> Or
>>>
>>> 2. NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>>> will be deleted and you will be prompted to install again.
>>>
>>> I hope this helps others to achieve a machine that is not bugging to
>>> install this update anymore.
>
>

"Ohno" <> wrote in message
news:...
>I am posting this in case it can help others. It is a bit winded but I
>wrote it the best way I could explain it.
>
> After reading many posts including replies to my own posts I have put
> together my own method to install this darn thing and it seems to have
> worked.

Heavy Clipping - sorry

> . NoCDBurning" will return in the registry and "HonorAutoRunSetting" will
> be deleted and you will be prompted to install again.
>
> I hope this helps others to achieve a machine that is not bugging to
> install this update anymore.
>

Thank you for sharing your findings - it may well solve others problems and
I might get KB967715 out of the 'Hidden Folder' and give it a go.

Antioch

This has been confirmed by many sources, Harry.

cf. http://badwarebusters.org/main/itemview/1666

cf. http://aumha.net/viewtopic.php?f=62&t=38665
--
~Robear

Harry Johnston [MVP] wrote:
> Ohno wrote:
>
>> The problem on my computer was related to DLA (Drive Letter Access), many
>> will know what this is but some will not.
>
> OK, now that's just bizarre. Why on earth would DLA software interfere
> with the ability of a Windows update to set a registry value?
>
> (I'm not doubting your report, by the way; I'm just shocked at how badly
> that software must have been written.)
>
> If I get a chance, I'll see if I've got a copy of Sonic DLA floating
> around
> and if so, try to reproduce the problem - just out of curiosity, you
> understand, since it's such a particularly oddball problem. :-)
>
> Harry.
>
>> For those that do not, what DLA
>> does is allows you to insert a cdrw disc into your cd writer and write
>> and
>> erase data on it just like you would your hard drive. Most people do not
>> do
>> that, especially with the advent of Flash Drives. So if you do not use
>> DLA
>> my solution should work and you will not even have to uninstall anything
>> from your machine.
>>
>> Please note DLA can be listed in your add remove programs list as
>> different
>> brands. The main brand name is Roxio DLA however some OEM vendors have a
>> factory installed version called Sonic DLA as was the case with my
>> machine.
>>
>> Now here is what I did.
>>
>> I disabled DLA from starting on my computer using the "System
>> Configuration
>> Utility" (msconfig).
>>
>> For those that do not know this tool I will give step by step
>> instructions
>> below. For everyone else I am just trying to make it easy for those that
>> don't know.
>>
>> Here goes.
>> Once your computer is all booted up click start then click the icon that
>> says run. In the box that pops up type the word between quotes
>> "msconfig"
>> then click ok.
>>
>> You will see a row of tabs with various names on them. Click the one that
>> says Startup.
>>
>> In the list look for look down the left side under Startup Item for
>> something called "DLACTRLW". If you find this click the box with the
>> check
>> mark to make the check mark go away.
>>
>> Click apply and ok to let your computer reboot.
>>
>> This will stop DLA from running when you restart your computer.
>>
>> Once you computer has rebooted then you will get a new message that tells
>> you that you have used the System Configuration Utility to make changes
>> to
>> the way Windows starts. There will be a box to check that says don't show
>> this message again. Put a check mark in that box and click ok.
>>
>> Now go to the Windows update site and install the update. Let the
>> computer
>> restart then go back to the Windows update site and you should find that
>> the update is not offered anymore.
>>
>> Please note that I did not look at the registry key after turning off DLA
>> but after doing the install with it off the "HonorAutoRunSetting" key now
>> exists and the key that was there called "NoCDBurning" is gone. I am not
>> sure at this moment if turning off DLA removed the key or if it was
>> removed
>> when the update installed. I however do believe it disappeared when the
>> DLA
>> was turned off.
>>
>> Now for a final note. I have not returned to "msconfig" and put a check
>> back in "DLACTRLW" to re-enable it because I do not use DLA so I just
>> left
>> it turned off, therefore I can not state with any facts that if your were
>> to return to "msconfig" and re-enable "DLACTRLW" that the
>> "HonorAutoRunSetting" would remain and that the "NoCDBurning" would not
>> return. If you do turn DLA back on and "HonorAutoRunSetting" disappears
>> you will
>> once again be prompted to reinstall KB967715. But if you were prompted
>> again you could turn off DLA and install the update again.
>>
>> If anyone wants turn DLA back on after a successful install I would
>> suggest
>> to wait a day or two so you know if it is installed correctly before
>> turning DLA back on. Then reply to this thread and let us all know what
>> happened when you attempted to turn it back on.
>>
>> For the non techie's reading this you should not go beyond this point of
>> this post.
>>
>> For those curious to explore the registry and I don't suggest it except
>> for
>> experienced users who already know how to get into the registry.
>>
>> I figure turning DLA back on will cause one of the two following things
>> to
>> happen:
>>
>> 1. "NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>> will
>> remain and you will not be prompted to install again.
>>
>> Or
>>
>> 2. NoCDBurning" will return in the registry and "HonorAutoRunSetting"
>> will
>> be deleted and you will be prompted to install again.
>>
>> I hope this helps others to achieve a machine that is not bugging to
>> install this update anymore.

PA Bear [MS MVP] wrote:

> This has been confirmed by many sources, Harry.
>
> cf. http://badwarebusters.org/main/itemview/1666
>
> cf. http://aumha.net/viewtopic.php?f=62&t=38665

Yeah, I don't doubt it. I'm just curious as to how exactly the DLA software is
managing to do something so very stupid. :-)

Actually I didn't have to look far to find a test box. The laptop I'm typing
this message on has Sonic DLA installed!

Harry.

Harry Johnston [MVP] wrote:

>> This has been confirmed by many sources, Harry.
>>
>> cf. http://badwarebusters.org/main/itemview/1666
>>
>> cf. http://aumha.net/viewtopic.php?f=62&t=38665
>
> Yeah, I don't doubt it. I'm just curious as to how exactly the DLA
> software is managing to do something so very stupid. :-)
>
> Actually I didn't have to look far to find a test box. The laptop I'm
> typing this message on has Sonic DLA installed!

Couldn't reproduce the problem. Either version 4.95 is unaffected, or there are
other factors involved.

The "NoCDBurning" key/value wasn't present either.

Harry.

Harry Johnston [MVP] wrote:
>>> This has been confirmed by many sources, Harry.
>>>
>>> cf. http://badwarebusters.org/main/itemview/1666
>>>
>>> cf. http://aumha.net/viewtopic.php?f=62&t=38665
>>
>> Yeah, I don't doubt it. I'm just curious as to how exactly the DLA
>> software is managing to do something so very stupid. :-)
>>
>> Actually I didn't have to look far to find a test box. The laptop I'm
>> typing this message on has Sonic DLA installed!
>
> Couldn't reproduce the problem. Either version 4.95 is unaffected, or
> there are other factors involved.
>
> The "NoCDBurning" key/value wasn't present either.

YMMV, as always!

The DLA on the effected machine I am using is 5.2.0.

Could be that the "NoCDBurning" key exists when you tell your drive not to
use DLA which I did. I did not want it asking if I wanted to format when I
installed a new cd.


"Harry Johnston [MVP]" <> wrote in message
news:%...
> Harry Johnston [MVP] wrote:
>
>>> This has been confirmed by many sources, Harry.
>>>
>>> cf. http://badwarebusters.org/main/itemview/1666
>>>
>>> cf. http://aumha.net/viewtopic.php?f=62&t=38665
>>
>> Yeah, I don't doubt it. I'm just curious as to how exactly the DLA
>> software is managing to do something so very stupid. :-)
>>
>> Actually I didn't have to look far to find a test box. The laptop I'm
>> typing this message on has Sonic DLA installed!
>
> Couldn't reproduce the problem. Either version 4.95 is unaffected, or
> there are other factors involved.
>
> The "NoCDBurning" key/value wasn't present either.
>
> Harry.