Message re btwizard.dll

[Terry Pinnell]

I've started to get this message:
"RUNDLL Error loading btwizard.dll The specified module
could not be found."

https://dl.dropboxusercontent.com/u/4019461/BTWizard-1.jpg

I haven't yet pinned down what activity actually triggers the
message. But I do know that the problem has arisen since trying to
uninstall a program. (I think it's now irrelevant, but FWIW that was
called Desktop Capture Engine, which came as part of SUPER, the video
converter).

I used the noemally very reliable Revo Uninstaller. But somehow it
deleted scores of files in \System 32 before I cancelled it.

One of the accidentally deleted files must have been btwizard.dll,
which I found is owned by Bluetooth Software 5.0.1.802 from Broadcom
Corporation. I downloaded a replacement for that file, but the
messages continued to occur.

Then I uninstalled Bluetooth Software (which I don't use - can't
remember why I installed it those years ago and I don't pair BT
devices with this desktop PC - or anything else for that matter). But
I still get the message.

I've done the obvious stuff like running sfc \scannow and registry
cleaning.

I'll next try replacing btwizard.dll again in \System 32 (it was of
course deleted when I uninstalled Bluetooth Software). But, as it's an
intermittent problem, it might be some time before I'm confident this
has fixed it.

Also, I'm nervous about negative impacts from the other deleted files.
Would that sfc \scannow have replaced those *essential* to XP? Is
there any way of finding what files *were* deleted? I backup data and
my XP registry nightly, but not \System 32! And they were not in the
Recycle Bin. Any log somewhere?

I'd much appreciate any insights or advice please. My PC seems to be
running OK - I just close the message and continue. So it's not a
serious practical problem, but I hate unsolved puzzles of this sort!

 

[Paul]

I've started to get this message:
"RUNDLL Error loading btwizard.dll The specified module
could not be found."

https://dl.dropboxusercontent.com/u/4019461/BTWizard-1.jpg

I haven't yet pinned down what activity actually triggers the
message. But I do know that the problem has arisen since trying to
uninstall a program. (I think it's now irrelevant, but FWIW that was
called Desktop Capture Engine, which came as part of SUPER, the video
converter).

I used the noemally very reliable Revo Uninstaller. But somehow it
deleted scores of files in \System 32 before I cancelled it.

One of the accidentally deleted files must have been btwizard.dll,
which I found is owned by Bluetooth Software 5.0.1.802 from Broadcom
Corporation. I downloaded a replacement for that file, but the
messages continued to occur.

Then I uninstalled Bluetooth Software (which I don't use - can't
remember why I installed it those years ago and I don't pair BT
devices with this desktop PC - or anything else for that matter). But
I still get the message.

I've done the obvious stuff like running sfc \scannow and registry
cleaning.

I'll next try replacing btwizard.dll again in \System 32 (it was of
course deleted when I uninstalled Bluetooth Software). But, as it's an
intermittent problem, it might be some time before I'm confident this
has fixed it.

Also, I'm nervous about negative impacts from the other deleted files.
Would that sfc \scannow have replaced those *essential* to XP? Is
there any way of finding what files *were* deleted? I backup data and
my XP registry nightly, but not \System 32! And they were not in the
Recycle Bin. Any log somewhere?

I'd much appreciate any insights or advice please. My PC seems to be
running OK - I just close the message and continue. So it's not a
serious practical problem, but I hate unsolved puzzles of this sort!

You can try "Autoruns" and see if it is referenced in there.

http://technet.microsoft.com/en-us/sysinternals/bb963902

If you get desperate, open Regedit and do a search for that
file name. (Start : Run : regedit.exe). And see if a reference
to the item is present.

I recommend Autoruns first, because it edits the registry
for you, and the interface uses tick boxes. Notice I did not specify
what to do in the Regedit case, as the first step is
finding out where the reference is located. It's likely
some Startup item, but you'll find out when you get there.
Using Regedit can be intimidating if you haven't been
in there before. If you don't make any changes, you won't
break anything.

Paul

 

[Terry]

You can try "Autoruns" and see if it is referenced in there.

http://technet.microsoft.com/en-us/sysinternals/bb963902

If you get desperate, open Regedit and do a search for that
file name. (Start : Run : regedit.exe). And see if a reference
to the item is present.

I recommend Autoruns first, because it edits the registry
for you, and the interface uses tick boxes. Notice I did not specify
what to do in the Regedit case, as the first step is
finding out where the reference is located. It's likely
some Startup item, but you'll find out when you get there.
Using Regedit can be intimidating if you haven't been
in there before. If you don't make any changes, you won't
break anything.

Paul

Thanks, Paul, appreciate your reply.

I subsequently found one program responsible for triggering this
message. It's that part of Microsoft ActiveSync which runs when I
establish a USB connection between my PC and my ageing HPC Touch Pro 2
smartphone.

So I re-installed ActiveSync. I also did a Repair of Outlook 2002,
which was the program whose installation included ActiveSync. I
rebooted after those steps.

But on trying to connect, I was still getting the btwizard error.

I have AutoRuns, a very handy tool, but searching for 'btwizard' under
the Everything tab, which I did at an earlier stage, gave no hits. But
various other Bluetooth-related files were listed, and experiment
showed they were all under the Drivers tab. As you see, all were
enabled.

https://dl.dropboxusercontent.com/u/4019461/BTWizard-2.jpg

Anyway, I left them enabled.

As an aside, I saw many other 'File not found' entries. Should I worry
about those?

By now I gave up and resorted to an SR, going back 11 days and so far
have not had the error message. (Although I now have to re-install
some stuff, notably a video conversion program called SUPER from
eRightSoftware.)

Straying OT, the SR reported that it had copied various folders to new
ones, typically suffixed with '(2)'. Are these simply locations for
old settings? Should I methodically transfer all contents back to the
main folders?

 

[Paul]

Thanks, Paul, appreciate your reply.

I subsequently found one program responsible for triggering this
message. It's that part of Microsoft ActiveSync which runs when I
establish a USB connection between my PC and my ageing HPC Touch Pro 2
smartphone.

So I re-installed ActiveSync. I also did a Repair of Outlook 2002,
which was the program whose installation included ActiveSync. I
rebooted after those steps.

But on trying to connect, I was still getting the btwizard error.

I have AutoRuns, a very handy tool, but searching for 'btwizard' under
the Everything tab, which I did at an earlier stage, gave no hits. But
various other Bluetooth-related files were listed, and experiment
showed they were all under the Drivers tab. As you see, all were
enabled.

https://dl.dropboxusercontent.com/u/4019461/BTWizard-2.jpg

Anyway, I left them enabled.

As an aside, I saw many other 'File not found' entries. Should I worry
about those?

By now I gave up and resorted to an SR, going back 11 days and so far
have not had the error message. (Although I now have to re-install
some stuff, notably a video conversion program called SUPER from
eRightSoftware.)

Straying OT, the SR reported that it had copied various folders to new
ones, typically suffixed with '(2)'. Are these simply locations for
old settings? Should I methodically transfer all contents back to the
main folders?

That's pretty strange. I thought System Restore just overwrites
anything it wants. The only way it would create a (2) is if there
was a (2) there eleven days ago, which got removed in the
later days.

On WinXP, System Restore can both add and delete files. It isn't
at all careful about collateral damage. It works to put things
back in the state they were in eleven days ago, no matter what.
I learned of this, when a couple big files in my C:\downloads
folder got deleted. Your file storage scheme has to match what
Microsoft wants - things like C:\Documents and Settings aren't monitored,
so things don't go missing from there. However, if you're clever and
keep stuff outside that area, it can have things deleted. As an
example, I created a C:\FFMPEG\bin not too long ago. If I were
to go back eleven days this moment, my C:\FFMPEG\bin would
get deleted, because it didn't exist eleven days ago. And the
SR would say there wasn't such a file back then. This gives an
incentive to store things, the way Microsoft intended :-(

I turn off SR monitoring on all partitions except C:. This means
no other partitions are affected if using a Restore Point.

If you're going to use SR, it pays to find the detailed non-Microsoft
website article, that describes how it works. There is a list of
file types it tracks. And a list of exclusions it doesn't track
(like the Documents and Settings). In fact, SR can't undo all
changes to a system, when going back eleven days. Some
driver or program installations, they use file types that
are not monitored (don't match the extensions in the list).
It's recommended to use Add/Remove, then go back eleven days,
in an attempt to get as much stuff as possible, for the more
obscure cases.

And when it comes to finding something on a hard drive, on one
occasion I searched the *entire* disk drive, byte by byte, looking
for the accursed thing. I had to write a simple minded C program,
to take care of double byte string storage, to have a decent chance
of finding it. Things can be stored "btwizard.dll" or
" b t w i z a r d . d l l". Where the leading space is a 0x00 null.
That's wide character storage, where for English language, the first
byte is mostly zero. For foreign languages, that first byte in the byte
pairs, could have some other value. Not a lot of tools on the
computer (or on alternate OSes), are really ready to help you with
problems like that. The registry stores lots of stuff in the
wide format. Some things that look like binary in the registry,
are actually just text strings with every second byte being 0x00.
And no tools are provided to make that evident.

Paul