Unsolved
This post is more than 5 years old
380 Posts
1
5489
Dell Wireless 1830 Bluetooth Driver Update
A couple of weeks ago I downloaded the Dell Wireless 1830 Update that has a Release Date of December 22nd, 2016 (although the "View Details" indicates that it was released on January 16th, 2017). Assuming that this was an update, I tried to apply this to my XPS 15 9550 but the update failed. The generated log really did not tell me much but when I investigated what driver version I currently have, I realized that I already had the v12.0.1.750 driver installed with a driver date of 9/23/2015. It apparently was installed as part of the Anniversary Update last August. However looking at the Programs and Features list, the "WIDCOMM Bluetooth Software" entry shows the version of 12.0.1.730 which was the original installation date back in December 2015. I suspect the Anniversary Update changed the driver without updating the underlying software indicator. Below is the pertinent part of the log. I would appreciate if Dell could comment on this.
Thanks,
JohnD
===========================================================================
--- Start of Vendor Software Log ---
[01/16/17 02:08:48]
--- End of Vendor Software Log ---
[01/16/17 02:08:48] Vendor Software Return Code: 3221226505
[01/16/17 02:08:48] logo.png
[01/16/17 02:08:48] (MUPXMLParser::GetResultName): *** Vendor Return Code is not found in Mup.xml
[01/16/17 02:08:48] Name of Exit Code:
[01/16/17 02:08:48] (DupAPI::GetReturnCode): *** Unable to find DUP value for:
[01/16/17 02:08:48] Exit Code set to: 1 (0x1)
[01/16/17 02:08:48] Result: FAILURE
[01/16/17 02:08:55] Open file: C:\ProgramData\Dell\UpdatePackage\Log\Network_Driver_YW21W_WN32_12.0.1.750_A04_01.txt
===========================================================================
DELL-Chris M
Community Manager
Community Manager
•
54.2K Posts
0
January 18th, 2017 07:00
The Windows 10 Anniversary Update was compiled by Microsoft, not Dell. We have no way of knowing what drivers they included or why.
When I go to the Dell XPS 15 9550 driver page for Windows 10, I do not see a Dell Wireless 1830 update dated 12/22/16.
I find the following =
Dell Wireless 1830 Bluetooth Application
https://www.dell.com/support/drivers/driverdetails?driverid=5PMW3
Communications_Application_5PMW3_WN32_12.0.1.730_A01.EXE
Version 12.0.1.730, A01
Release date 10/14/15
Dell Wireless 1830 WiFi Driver
https://www.dell.com/support/drivers/driverdetails?driverid=JKRJ9
9550_Network_Driver_JKRJ9_WN32_1.566.0.0_A04.EXE
Version 1.566.0.0, A04
Release date 3/23/16
Older versions =
1.555.0.0,A03 12/21/15
1.519.0.0,A01 10/14/15
1.442.0.0,A00 10/5/15
Saltgrass
3 Apprentice
3 Apprentice
•
4.3K Posts
0
January 18th, 2017 09:00
There are some driver in the Network section. Why they would put Bluetooth drivers in two different sections, no sure.
johnptd
380 Posts
0
January 19th, 2017 02:00
When I bring up my Service Tag, I see an update "Dell Wireless 1550/1560/1704/1708/1820A/1830 Bluetooth Driver" with a file named "Network_Driver_YW21W_WN32_12.0.1.750_A04_01.EXE", released Dec 22, 2016. This is in the "Network" section. It is indicated as applying to the XPS 15 9550 and was the one I attempted to apply to my system. I also see the update "Dell Wireless 1830 Bluetooth Application" (version 12.0.1.730) which is in the "Modem/Communications" section. This is the one originally installed on my system as shown in my "Programs and Features" list as "WIDCOMM Bluetooth Software". This is very confusing as Saltgrass indicates. I would think that these would be consistent and show the same version. It seems that the Anniversary Update updated the driver (provided by Broadcom) but the underlying "software" version indicated in "Programs and Features" was not changed. Microsoft directly updating drivers is causing havoc. There were a number of driver updates inclided in the Anniversary Update for which no indication was given.
JohnD
Linhhy
1 Message
0
February 15th, 2017 01:00
I have same problem. I could not update the Bluetooth drive from this packet.
johnptd
380 Posts
0
February 16th, 2017 02:00
Check Device Manager to see if you already have the v12.0.1.750 driver installed.
JohnD