Windows 7 and Dell Bluetooth 355 driver

You may mean well, but I'm about as likely to download and allow to install a file from an anonymous server (never mind one in Russia) as I am to snuggle up to a flea bitten rat in a time of plague.

On my machine, a Dell Inspiron 1525, I had to install R159805 to get bluetooth back working on my machine I installed R226750 to get the latest version.

I finally got R226750 to load on my machine.  The problem was the Dell Download Manager, and when I deleted my internet cookies and then chose not to use the download manager, I could get and load that package.

At first this seemed to work.  I had maybe an hour of correct bluetooth and began to feel it had worked.  But then, presto, BT conked out again.  Just like before.  And when I "renewed" BT by toggling the wireless on/off button I got only another 10 minutes of use, about the same as before.

So, the R226750 package with the 7600 series driver (dated 6/21/09) does not solve the issue.  Using Win7 64 bit on the XPS M1530.  Sigh.

I finally got R226750 to load on my machine.  The problem was the Dell Download Manager, and when I deleted my internet cookies and then chose not to use the download manager, I could get and load that package. At first this seemed to work.  I had maybe an hour of correct bluetooth and began to feel it had worked.  But then, presto, BT conked out again.  Just like before.  And when I "renewed" BT by toggling the wireless on/off button I got only another 10 minutes of use, about the same as before. So, the R226750 package with the 7600 series driver (dated 6/21/09) does not solve the issue.  Using Win7 64 bit on the XPS M1530.  Sigh.

Have you had any "official" comment from a Dell "expert" on this?  Where do they stand?  Are they in hiding?

Under Vista, Microsoft had released a patch for this; I can't find it because I'm on Win7 now and the link came from Vista help.  It did, however, take care of the Bluetooth comatose issue...

I don't know if it was related or not, but I noticed that since I got a new Blackberry and installed the Blackberry Desktop Manager, I had 2 Bluetooth Peripheral Device entries in Device Manager that Windows could not find drivers for.  I tried the R226750 package and  it updated my installation correctly, but these devices still remained.  Google and rajivsinghsuwal (thanks) at sevenforums.com  revealed this article on how to install these items:

Window Mobile Device Center v6.1 post at SevenForums.com

Basically you download and install the drvupdate-x86.exe package from Microsoft, and then manually tell Windows what driver to use for these devices (Microsoft Corporation -> Windows Mobile-based device support)..

I have yet to see my Bluetooth drop out again now that these devices are (pseudo)installed.  I did uncheck a setting in the Power Management options long ago that made a difference under Vista, but it had no effect under Win7:

I will try to post back here if installing the Windows Mobile Device Center v6.1 for my Bluetooth Peripheral Devices made any difference with respect to the issue of Bluetooth regularly shutting itself off after some time.

I am very confused...  I have an Inspiron 1720 which was factory installed with the proper Vista Ultimate 32-bit drivers for the Dell Wireless 355 Bluetooth Module.  I did a clean install of Windows 7 Ultimate X64 two weeks ago, and the default Microsoft (Windows 7) drivers for the 355 Bluetooth Module were installed.  Although I currently only use the Bluetooth for the Dell Bluetooth Travel Mouse, everything has been working flawlessly using the default Microsoft drivers.  No Widcomm drivers were installed (as was the case for Vista Ultimate when it shipped from the factory) and no Setpoint software (for the mouse) was installed (as was the case when it shipped from the factory), but everything has been functioning perfectly.

Therefore, I do not understand why we need to look for and install updated 355 Bluetooth drivers, Setpoint software, etc. when the (generic) ones from Microsoft that shipped with Windows 7 seem to work fine?...

Absolutely do not change a thing.  If it works for you then the last thing you want to do is tinker with it.

There have been some posts indicating that variations in the BT module may mean only some of us have this problem.  If you have a properly working system, then happy happy happy you, and maybe someday we unfortunates will find a cure too.

Kinw, don't fix what ain't broke.

Been struggling with this for a month, every since I upgraded my XPSM1330 Vista 64-bit  to Windows 7 64-bit.  Looked for drivers.  Used Vista drivers.  Contacted Logitech support for the latest BT 64-bit Setpoint software and still had the issue with the mouse dropping.  Just read your post yesterday and uninstalled the Dell 355 Bluetooth driver and installed the default Microsoft Generic Adapter. 

It's been 24 hours and still connected and working.

Thanks!!!!

Wow!  Glad to hear that!  Hope it continues to work smoothly and consistently for you!

I didn't think that my post would actually help anyone...  I was hoping someone could tell me what I was doing wrong - since it sounded like it was necessary to use the Dell drivers (and/or the Widcomm drivers)...

Therefore, I do not understand why we need to look for and install updated 355 Bluetooth drivers, Setpoint software, etc. when the (generic) ones from Microsoft that shipped with Windows 7 seem to work fine?...

I would agree, except when I went to Win7 X32 as an upgrade, my Dell 355 Bluetooth did not work fine.  I kept having an issue where my BT mouse would disconnect upon seeing the UAC prompt, user logoff, switching users, or the screen saver becoming active. As it turns out, it is the 355 module driver getting hung, or an issue with the BT stack.  I could not use the BT adapter until I turned it off/on using Fn+F2 .  There is no hardwired switch on my E1705 (Inspiron 9400)...

Another reason for using the manufacturer's drivers is a lot of times they support additional or special features like BT serial ports or things like that...

I have tried maybe 6 different Widcomm/Broadcomm packages and have the same trouble.   Just last evening, I uninstalled the lot of them and reverted to the built-in Win7 drivers for BT, with the same drop-out results.

I would agree also with tanjb that if your installation and the features you need are working properly, then it is best to leave well enough alone.  BT installs are finicky, and can be time consuming to troubleshoot and fix.

KINW and jgnfyi - I think we are on a roll here.  I seem to be fixed too.  It has been two days and no loss of BT mouse over several sessions, tonight about 2 hours up to this point so I am confident to write.

To be clear, I did two things.  The first (which I suspect was not important) which was to disable the power management (see danonh's nice post including the graphic).  But, I have left that there.  I may experiment re-enabling it if I seem to have a reduction in battery life.

The thing which seems to be key was to remove the WidComm driver.  I did not actually have to (re)install anything.  I just went into Programs and Features, scrolled down to the WidComm Bluetooth (all 120 MB of it!) and uninstalled it.  This had no obvious effect.  My BT remained working and the Dell 355 drivers are still present.  This is what it looks like now.  I hope this helps with others here.  If it does not help and you need that WidComm 120MB reinstalled, it came fromt the driver package from the Dell site.

1. Click the Windows Start Menu orb and in the search box, type cmd.
2. When the Command Prompt (cmd.exe) appears in the list above, right-click on it and select “Run as Administrator”.
3. Once the Command Prompt window opens, type the following commands on the command line, one by one, followed by the Enter key:
   
   set devmgr_show_nonpresent_devices=1
   
   start devmgmt.msc
   
   When Device Manager opens,  go to the View menu and select “Show hidden devices”.  You may be surprised what you see shown there.  I removed all grayed-out devices, as well as all Bluetooth-related items that were currently installed, then rebooted.

• Logoff,
• Switching users,
• The display of a UAC prompt,
• When the screen saver activates, and
• Several reboots

Thanks Dan.  I followed your posting exactly and at last I have a wireless mouse that stays active on my XPS 1330

Mick

Glad this worked for you. 

One additional thing: After I ran the command to display non-present devices, and then displayed hidden devices in Device Manager, once I pressed Fn+F2 to turn off my Bluetooth adapter, some additional devices also appeared that I had to delete. 

Once the computer went to sleep, the mouse would awake it and terminate the screen saver, but then the mouse wheel and back button would not work.  It seems that after some time delay this occurs, even when the computer is being used.  The mouse wheel button did work to scroll through web pages, however.

I am still investigating this, and I have since installed the Dell R140135 package and then the R226750 update and the behavior is still the same.

I am now looking at the Intellipoint software and a possible conflict with my Synaptics Touch Pad driver as further areas of focus, and I'll post back if I discover anything more.

hello

I resolved my bluetooth's problem on my inspiron 1720 with seven 64 bits :

get R140135 from DELL

try an install : you can't activate bluetooth so abort it

but you have the files

run c:\DELL\drivers\R140135/3100_216\Win64\inst.exe

you can't activate bluetooth so clic done but it say ok-terminated

so reboot and you get the icon...