Windows 7 - Fixed my KB967715 issue 99.99% sure.

Asked By Ohno

16-Mar-09 03:26 AM

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.

16-Mar-09 03:51 AM

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.

16-Mar-09 04:12 AM

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.

16-Mar-09 04:26 AM

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.

16-Mar-09 07:43 AM

Heavy Clipping - sorry


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

16-Mar-09 12:22 PM

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

16-Mar-09 05:22 PM

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.

16-Mar-09 06:30 PM

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

The "NoCDBurning" key/value was not present either.

Harry.

16-Mar-09 06:45 PM

YMMV, as always!

16-Mar-09 07:02 PM

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.

16-Mar-09 07:10 PM

My system is configured to use DLA, so that could well be the difference.

Harry.

16-Mar-09 07:50 PM

I had an xp sp3 pc which originally failed to properly install
kb967715.  This was reported here in another thread.  That pc had
Roxio and DLA.  However (also reported in another thread), I resolved
the problem successfully by downloading the update from MS and
installing it in Safe Mode.  I didn't do anything to DLA because I
didn't know I had it at that time.

Louise

On Tue, 17 Mar 2009 12:10:39 +1300, "Harry Johnston [MVP]"

17-Mar-09 01:30 AM

Well a new day has come and no re-offering of the update so at least in my
case the procedure was successful.

17-Mar-09 02:25 AM

Harry,

I just noticed something else.

My CDRW drive is now configured to use DLA even though I had it turned off.

I don't know if I am correct about this because I don't want to mess around
with it and don't have a virtual machine setup at this point to test it.

But as you know my "NoCDBurning" key in not in existance anymore, so turning
off  "DLACTRLW" in startup probably caused that. This now makes me wonder if
this issue is related only to those that turned DLA off on their CD Drive.
Could be DLACTRLW enforces the option to not allow DLA on the drive and
requires the NoCDBurning value in the registry to do this, thus erasing
anything else in the effected key on every boot up.

18-Mar-09 01:21 AM

Harry,

One last little bit of info on this.

I went tonight to the location of the other machine that is a twin brother
to this machine, not exactly but same make and model.

Anyway I had waited on that machine for a couple days to see how mine went.
So tonight I played with it and this is what I found.

KB967715 will not install properly either way with or without DLA activated
for the optical drive. Here is what I found playing with that machine.

This time before disabling DLACTRLW in startup I tried installing the update
with DLA turned on for the drive.

When I rebooted the entire key was gone.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies
existed but the Explorer key was gone.

The update did not take and was offered again.

So with this key gone I disabled DLA on the drive and the Explorer folder
returned with the "NoCDBurning" key intact.

Knowing the install would fail again I followed the instructions in my
original post to disable DLACTRLW and now as before the key is properly set
and the "NoCDBurning" value does not exist.

Both machines mine and the other do now have DLA turned on for the optical
drive but I have not tried it to see if it works with the startup entry
turned off.

My guess on this but is only a guess is the DLACTRLW is simply a exe file
that writes or erases a registry key based on the settings of the DLA config
file. I say this because what seems to be happening is the update turns DLA
on and then on boot the DLACTRLW either deletes the key entire key if DLA is
enabled or re writes the entire key if DLA is disabled. Smiler to using a
portable application that writes and deletes to and from the registry upon
launching or closing a program.

That's all I have on this subject unless I work on a machine with a
different version of DLA.

In any case I do know my solution works and one day I will get a blank cdrw
disc just to see if DLA is actually working with the startup item disabled.

18-Mar-09 01:34 AM

One last thing, I wonder if my findings are correct, why Microsoft could not
list that as a known issue and during install disable the startup entry
automatically?

18-Mar-09 12:11 PM

Excellent question!

18-Mar-09 07:32 PM

But you can imagine how the story would be told ... "Microsoft update
deliberately breaks third-party product". :-(

Harry.

02-May-09 10:25 AM

Thanks for taking the time to post this.  It sovled my problem.