none
HP Elitebook 8460p, bluetooth & audio driver

    Question

  • Hi 

    Was wondering if anybody have deployed HP's new Elitebook 8460p yet? I have ran into some problems with the Broadcom 2070 Bluetooth driver and IDT Audio Driver.

    The driver installs fine with apply driver package step in TS but when I log in for the first time (as a regular user) I can see in the bottom right corner that Windows is doing an PnP driver scan and will prompt an UAC screen that wants admin credential to install the Broadcom 2070 Bluetooth driver. If I log in as a local admin on the machine it will just say that the driver has been installed.

    The other problem is that the IDT Audio Driver installs fine and t it will show a blue icon on the bottom right corner. But when you double click it to go to the settings it just pops up a windows saying "cannot find .startup file!"

    /A

     

    Monday, May 23, 2011 8:59 PM

All replies

  • So let me make this clear, if you logon first time with admin credentials, you don´t need to point any wizard to driver location, true? How about, if you don´t enter admin credentials in UAC, or do not sign in as admin - will you see an unknown, new device in device manager? If driver is more complicated as just .inf pointing to .sys, you probably may consider to do Software Package for this driver and execute it in TS as a program, usin WMI model query only for 8460p if you may.

     

    Monday, May 23, 2011 9:36 PM
  • If I press cancel the UAC will go away. When I go to device manager it doesn't show any unknow devices and the in the Bluetooth category it will shot Broadcom 2070 Blutetooth. When I press scan for new hardware changes the UAC will show up again.

    I haven't need to install the Bluetooth driver as Software package for the other HP Elitebooks before (6930p, 8440p) so I thought I could just import it as an inf driver as usual. But maybe they have changed the driver to be more complicated. If anybody have done a full deploy of the new HP Elitebooks xx60p laptops please confirm if the bluetooth driver needs to be installed as software or if their is anything special I need to do for the inf driver to work...

     

    /A

    Monday, May 23, 2011 9:53 PM
  • I feel your pain, I had the same issue with the Audio driver for a demo 8460p the fix is to move the IDTNGUI.startup file from C:\Program Files\IDT\OEM\SRS to C:\Program Files\IDT\OEM

     Looks like the path the app is looking for is incorrect

     In the testing i did i found uninstalling then reinstalling the audio driver resulted in a working icon in the taskbar, its only when you install the driver using a SCCM TS that it fails to launch correctly from the taskbar or from Control Panel.

    To workaround the issue i created a script to move the file for me after the driver had installed. HP know about it and are notifiying IDT as appearently they do not modify the venders driver packages themselves...

    Monday, May 23, 2011 10:55 PM
  • Thank you Redst0rm for the feedback. This is why I love this forum, there are always experts who can help.
    I will try to do script that copies that file until HP updates that driver. Did you experience the same problem as me with the Bluetooth driver?

     

    /A 

    Monday, May 23, 2011 11:44 PM
  • I dont think the demo model i was sent had bluetooth, I had a look in my driver package and don't see a driver for bluetooth.
    Tuesday, May 24, 2011 12:52 AM
  • Anybody who is deploying HP Elitebook 8460p with Bluetooth and SCCM 2007 are welcome to help... Thanks.
    Tuesday, June 07, 2011 2:30 PM
  • I've success to deploy HP 8460p with bluetooth drivers. It working well.

    I have following in the driver package for HP 8460p

    6.3.0.6150 Bluetooth Hands-free Audio
    6.3.0.3850 Bluetooth L2CAP Interface
    6.3.0.6060 Bluetooth module
    6.3.0.6150 Bluetooth Remote Control

    All drivers from Broadcom.

    1. I downloaded the bluetooth driver from HP.com "Broadcom 2070 Bluetooth"
    2. I extract the installation package i just downloaded "sp52717" with 7-Zip.
    3. Then I import this folder to driver package for HP 8460p in sccm and finally update distribution point.

     

    hope this will work for you.

    //Emil

    Friday, June 10, 2011 9:29 AM
  • I imported the drivers as well and succesfully deployed the 8460p...

    Took them from the HP site....

    and installed the HP connection manager 4.1.10.1 as well in the TS...

     

    here are my drivers after the import

     

    Bluetooth AVDT Driver Broadcom Corp. BluetoothVirtual 6.4.0.460
    Bluetooth AVDT Driver Broadcom Corp. BluetoothVirtual 6.4.0.460
    Bluetooth Hands-free Audio Broadcom Corp. Media 6.3.0.7650
    Bluetooth Hands-free Audio Broadcom Corp. Media 6.3.0.7650
    Bluetooth L2CAP Interface Broadcom Corp. BluetoothVirtual 6.3.0.8000
    Bluetooth L2CAP Interface Broadcom Corp. BluetoothVirtual 6.3.0.8000
    Bluetooth module Broadcom Corporation Bluetooth 6.5.0.150
    Bluetooth module Broadcom Corporation Bluetooth 6.5.0.150
    Bluetooth Remote Control Broadcom HIDClass 6.3.0.6450
    Bluetooth Remote Control Broadcom HIDClass 6.3.0.6450
    Dell Wireless 375 Bluetooth Module Broadcom Corporation Bluetooth 6.5.0.131
    Dell Wireless 375 Bluetooth Module Broadcom Corporation Bluetooth 6.5.0.131
    Dell Wireless 375 Bluetooth Module Broadcom Corporation Bluetooth 6.5.0.131
    Dell Wireless 375 Bluetooth Module Broadcom Corporation Bluetooth 6.5.0.131
    Friday, June 10, 2011 2:38 PM
  • Thanks for input, I'm thought I tried both importing driver and  just a driver package to install the driver and it was still the same problem.

    Can you two confirm that after the machine has been installed, you log in the first time with a standard user  and you don't get UAC prompt about installing a new device?

    Thanks 

    /A

     

    Friday, June 10, 2011 2:44 PM
  • I will test this on Tuesday... because I don't have the machine right now.

     

     

    Friday, June 10, 2011 2:51 PM
  • Thanks Jeroenda, really appreciate you taking time to test this for me. 
    Tuesday, June 14, 2011 8:42 AM
  • Hi,

     

    No problem, but our laptop is with a custommer. Ighet it back in the end of the week.

     

    Could it be that your bluetooth is not turned on during the image deployment ? Then the driver might not properly install.

    When it's turned on during the TS it will recoognize the hardware and dop a succesfull install....

    Tuesday, June 14, 2011 9:44 AM
  • I am having an issue with the ATI video card install.  If someone logins for the first tim with admin rights I have no issue.  However if someone logs in with a managed account I get a prompt to finalize the install.  Has anyone see this issue?
    Wednesday, June 15, 2011 7:36 PM
  • Sorry my model doesn't have ATI card so I can't help you test it.
    Thursday, June 16, 2011 7:36 AM
  • Bummer,

     

    Our NB has the same problem.

    If I log on with a std user, and enable the Bluetooth, it will pop-up the UAC box to install the driver.

     

    Looking for a solution ...

     

    Jeroen

     

     

    Monday, June 20, 2011 11:30 AM
  • Dont know if any of you have solved this yet, but with the IDT drivers like said earlier i worked around it by creating a simple script to copy over those 2 files from the SRS folder.

     

    As for bluetooth and the AMD drivers, I have yet to get a good solution to those issues as ive tried enabling the pnp services during OSD incase it was some service that wasnt enabled during OSD but came up short.

     

    Ill do some more testing tomorrow to see what i can come up with

    Tuesday, July 05, 2011 10:21 AM
  • This new Elitebook is just having so many drivers problems.

    First it was the IDT Audio which I solved with a script and devcon, then it was the Bluetooth problem that I solved by downloading an older driver.
    I don't have a model with the AMD card so I can't confirm that problem. But now I see noticed another problem, the Synaptics mouse driver is not working.
    And when I go into Control Panel > Mouse I get an error message saying it can't load the application. Have anyone else experienced this problem??

     

    /ALX

    Tuesday, July 05, 2011 10:35 AM
  • Hi,

     

    I installed Synaptics 15.0.10 as a "install software step" and it worked without a problem

     

    Which driver did you use for the bluietooth ?

     

    Tuesday, July 05, 2011 12:26 PM
  • Hi Jeroenda

    I think I used this one for the bluetooth:
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=321957&prodSeriesId=5056942&prodNameId=5056943&swEnvOID=4054&swLang=13&mode=2&taskId=135&swItem=ob-86863-1

     

    I searched HP website for Synaptics 15.0.10 and got to this page: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=ob-82593-1&mode=4&idx=3&prodTypeId=321957&prodSeriesId=5056942
    But in the description it doesn't say that it supports the Elitebook 8460p? Are you sure you can use all of the new features that the new touchpad has with that driver? Also if you can please  try the newest Synaptics version 15.2.16.6 to verify if you get the same problem as me with the touchpad and control panel? 

     

    Thanks

     

    /ALX

    Tuesday, July 05, 2011 4:06 PM
  • Installing the drivers as a software package doesnt really help the issue with driver integration.

     

    Its a workaround that can get really messy later on if you dont fix up the issues now. I have solved most of the issues and ill have a look at the synaptics issue once my build finishes.

    Wednesday, July 06, 2011 3:50 AM
  • ALX

     

    And when I go into Control Panel > Mouse I get an error message saying it can't load the application. Have anyone else experienced this problem??

     

    same problem here !

     

    Thursday, July 07, 2011 10:02 AM
  • Hello. Just FYI I have the same issue with bluetooth on HP 8460p and also on some DELL models (I am using driver package in SCCM TS).  In some cases the workaround is to use older driver but in some the older driver is not working :( Funny thing is that bluetooth driver for HP is called "Dell Wireless 375 Bluetooth Module" :) Installing the driver as a separate SW package is not solving the issue.

    Additional info here

    http://www.delltechcenter.com/thread/4588488/UAC+error+with+375+BlueTooth+Drives+on+Win+7+x64+(E6420/E6320)#fbid=boSRcwaqhrN

    Thursday, September 01, 2011 8:22 AM
  • Here is my experience with all of the Bluetooth drivers in newer systems (Win 7 x64)

    Depending on the driver, it will or will not result in the UAC prompt upon logging in as an admin user. If you logon as a normal user, you will get a newdev.exe message every time you logon. Obviously this is not alright in a production environment.

    In addition, not all of the Bluetooth components will install via PNP. I have removed all Bluetooth drivers from my driver packages and created a silent install of the Bluetooth package. This has worked on all the Dell laptops I support and the HP EliteBook 8760w.

    As for the SRS Premium Sound not loading, I have that issue as well. I thought that creating a software package for it would help but it doesn't. Copying that .startup file to the root of the OEM directory works as indicated. Thanks for the info. I appreciate it.

    Wednesday, September 28, 2011 1:38 PM
  • Hi,

    When deploying HP machines i've found it best to use the HP SSM utility. Make sure you have the SP and corresponding csv file, build the database in a command prompt: ssm.exe /AM_BLD_DB, SSM.exe and SSM.cab must be in the same folder, and distribute the package with a program with parameters: SSM.EXE . /INSTALL /ACCEPT

    Wednesday, September 28, 2011 3:06 PM
  • I feel your pain, I had the same issue with the Audio driver for a demo 8460p the fix is to move the IDTNGUI.startup file from C:\Program Files\IDT\OEM\SRS to C:\Program Files\IDT\OEM

     Looks like the path the app is looking for is incorrect

     In the testing i did i found uninstalling then reinstalling the audio driver resulted in a working icon in the taskbar, its only when you install the driver using a SCCM TS that it fails to launch correctly from the taskbar or from Control Panel.

    To workaround the issue i created a script to move the file for me after the driver had installed. HP know about it and are notifiying IDT as appearently they do not modify the venders driver packages themselves...


    My install was also with SCCM and I copied the C:\Program Files\IDT\OEM\SRS\IDTNGUI.startup file to the folder C:\Program Files\IDT and the applicaiton is working.
    Wednesday, November 16, 2011 8:21 PM
  • I've found with the HP notebooks, when trying to do the Bluetooth as well as the the hotkey support, is to create a separate Install Software package for those devices, and call those packages when deploying the OS.  The trouble I've had with doing the bluetooth drivers, is that you can get the drivers intalled if they are part of the driver package, but it doesn't always install the application stack for the bluetooth.  The drivers's there, but there's no way to use it. 

    I use the following line when installing the drivers via the OSD TS.

    Setup.exe /qn /ri /nostartbtw /L1033

    setup.exe /? will give you addtional installation options.

    Works great, we do this for the ProBook 6450b as well as the 6460b, I think the 6460b has the same BT module you mention.

    Wednesday, December 07, 2011 10:15 PM
  • Hi All,

    I am glad to hear that I am not the only one feeling the pain of HP and Bluetooth drivers! First it was the HP HotKey driver not work (couldn’t rotate the screen with the rotate screen button) then then Bluetooth driver and also the HP Diagnostic UEFI (still not working but not as fussed). To simplify the driver processes, we now only include the Network card drivers in the driver packages, just to make sure that the OSD TS can run successfully and get all the way through, then we run HP SSM in the TS and let it take care of the rest. This has proven to be a good method for us as it keeps the drivers clean during the TS, especially all of those hardware based applications (HBA's) that notebooks need these days (I often refer to these as the "nasty" or "bad" drivers!").

    A good quick reference that I found helped me get my head around this topic is found here:

    http://msmvps.com/blogs/richardwu/archive/2010/06/02/managing-device-driver-by-system-center-configuration-manager-sccm.aspx

    I have spent countless days/weeks trying to get our TS to deploy all the drivers using HP SSM in our TS. The model that I have been testing with is the HP EliteBook 2760p which has a Broadcom 2070 adaptor. We also have several other HP notebooks that have the same Bluetooth adaptor but I will get onto them in due course.

    What has been happening for us is the driver seems to install, but just sits at the very end trying to configure Bluetooth services. This also happens when just running the driver manually and would thus explain why it eventually times out in the TS causing a lovely dialog box to apear with a "0x000001" type of error (I can image you SCCM people out there nodding your heads about now!).

    ChristopherGray - I will try running "Setup.exe /qn /ri /nostartbtw /L1033" as suggested, first I’ll test it via an administrate command prompt, and if that works, I’ll test it in the TS. I haven't seen anyone else refer to the "/L1033" switch before. Can you tell me what’s its purpose is? I am hoping that it might tell the installer to just “keeping on going” and allow a successful and graceful installation, without the BSOD when shutting down or restarting the notebook because the shutdown times out from the Bluetooth drivers getting its hocks in the way. I have also tried a newer Bluetooth driver from Lenovo just to see if that would make a difference. It gets all the way through the manual install (after a long delay at the end) however; it causes the same type of BSOD to occur. In both cases, the driver seems to be functioning fine after a clean boot but obviously we cannot have this type of behaviour in our OSD TS. I have tested this on two of the same model with the same results.

    One word guys – HELP! J

    Wednesday, December 12, 2012 5:14 AM
  • I´m not familiar with HP SSM, but I heard Lenovo has similar solution, an utility which gathers and installs latest drivers via internet during TS run. Sounds perfect, but the negative side is - with this solution you won´t be having standard installations of workstations, because driver versions varies.
    Wednesday, December 12, 2012 12:06 PM
  • /L1033 is the language switch which is encglish in this case. Run setup.exe /? to see the list of install switches.
    Wednesday, December 12, 2012 12:38 PM
  • This is the command that I run for our HP EliteBook 8760w with the Broadcom 2070 Driver:
    Setup.exe /qn /ri /f2%Systemroot%\Installer\_Logs\HP_Bluetooth_2070_Install.log

    The /f2 switch is just where we put our log files.

    This has worked for me for over a year now without issue. I've used the same command for the EliteBook 8770w with the Broadcom 20702 Driver:
    Setup.exe /qn /ri /f2%Systemroot%\Installer\_Logs\HP_Bluetooth_20702_Install.log

    This should be the list of setup options (maybe with some slight variations):

    setup /?

    Usage:
    Setup.exe [/qn | /qb | /qr] [/nw] [/nodfu] [/ri] [/nostartbtw] [/noinf] [/f2<pat
    h to log file>][/L<LangId>]

    /qn       - Silent install without any UI and user interaction
    /qb         - Install with basic UI ,progress and dialog without any user intera
    ction
    /qr         - Install with full UI without any user interaction
    /nw         - Do not wait for BTW install to complete, exits after invoking MSI
    install.
    /nodfu      - Do not execute DFU during BTW install (even if configured for DFU
    in SvcPack.ini file)
    /ri         - Suppress reboot at the end of install (or upgrade) in case reboot
    was needed.
    /nostartbtw - Do not start Bluetooth application after install
    /noinf      - Do not install USB driver
    /f2<Path>   - Specifies the out install log file location
    /L          - Installation language

    LangId can be one of the following:

    Installation Language ID

            1033: English
            1046: Portuguese
            1028: Chinese Tradition
            2052: Chinese Simplified
            1030: Danish
            1043: Dutch
            1035: Finnish
            1036: French
            1031: German
            1040: Italian
            1041: Japanese
            1042: Korean
            1044: Norwegian
            1034: Spanish
            1053: Swedish
            1049: Russian
            1045: Polish

    For example, to install silently without any User Interface in German language,
    use the following command line
    setup.exe /qn /L1031

    Wednesday, December 12, 2012 2:19 PM
  • Thanks guys for getting back to me.

    What I am looking for is a command line switch that stops the installer for kicking off the services part at the very end. This is the BSOD that we get:


    • Edited by ITNinjaGuy Wednesday, December 12, 2012 9:58 PM
    Wednesday, December 12, 2012 9:52 PM
  • Hi James,

    Would the " /nw" switch assist with the installation to continue all the way through?

    • Edited by ITNinjaGuy Wednesday, December 12, 2012 10:25 PM
    Wednesday, December 12, 2012 9:55 PM
  • I´m not familiar with HP SSM, but I heard Lenovo has similar solution, an utility which gathers and installs latest drivers via internet during TS run. Sounds perfect, but the negative side is - with this solution you won´t be having standard installations of workstations, because driver versions varies.

    Hi yannara,

    When it comes to SSM, I have made my own version control. For each different model of machine, I have created a share on the server that is specific to each model (i.e.\\server\ssm_2760$ for the HP EliteBook 2760p's,\\server\ssm_4430$ for the HP ProBook 4430s's and so forth. Each share has all the nessary drivers for each model and a copy of the SSM.EXE and the SSM.CAB. To avoid this post being long winded, basicly I use WMI queires to run SSM for each of the specific models and thus I have the same versions of the drivers per model. Example of a WMI query I use is:

    SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%2760%' (run the following if it the model is like a 2760)

    That way if a driver is causing issues, it should in theory only relate to one particular model, rather than our entire fleet. :)


    Thursday, December 13, 2012 1:31 AM
  • Here is the log file from the bluetooth installer:

    [11:36:47] <INFO> ************** Setup.exe - Begin Install 6.3.0.6300 - Thursday, December 13, 2012 ****************
    [11:36:47] <INFO> 
    [11:36:47] <INFO> Run exe \\server\deploy\HBA\2760\BT\Win64\\setup.exe sub64 /f2C:\system.sav\logs\btwinlog.txt /qn /ri /nw
    [11:36:47] <INFO> ************** Setup.exe - Begin Install 6.3.0.6300 - Thursday, December 13, 2012 ****************
    [11:36:47] <INFO> 
    [11:36:47] <INFO> 64 bit OS = 1, Language id 1033, user UI lang 1033, system lang 1033
    [11:36:47] <INFO> Setup dir \\server\deploy\HBA\2760\BT\, Media dir \\server\deploy\HBA\2760\BT\Win64\
    [11:36:47] <INFO> InstallWithoutDevice=0
    [11:36:48] <INFO> Enable Radio
    [11:36:48] <INFO> Check Dell Startdust
    [11:36:48] <INFO> Not InstallDellStarDust config
    [11:36:48] <INFO> InstallBrcmDeviceInf, Signed 1
    [11:36:48] <INFO> No silent install w/o device
    [11:36:48] <INFO> Enable Radio
    [11:36:48] <INFO> MsStack Running
    [11:36:48] <INFO> no BTW currently installed,InstallNewSoftware
    [11:36:48] <INFO> InstallNewSoftware \\server\deploy\HBA\2760\BT\Win64\, 3, 1, 1, 0, 1033
    [11:36:48] <INFO> BtSetupFP_CheckDellInstallCondition return TRUE 45962224
    [11:36:48] <INFO> BtSetupFP_CheckDellInstallCondition arrDellPidVids is empty ??
    [11:36:48] <INFO> CheckDellInstallCondition returns 1
    [11:36:48] <INFO> Run exe \\server\deploy\HBA\2760\BT\Win64\inst.exe /s /L1033 /v"/qn BTW_SETUPEXE=1 REBOOT=ReallySuppress"
    [11:36:49] <INFO> >>>> BEGIN INSTALLTION 6.3.0.6300 ==== Thursday, December 13, 2012 <<<<<<<<<<<<<<
    [11:36:49] <INFO> ------------------BTINS_SetProductName-----------------------
    [11:36:49] <INFO> Product Name = Broadcom 2070 Bluetooth 3.0
    [11:36:49] <INFO> Publisher Name = Broadcom Corporation
    [11:37:21] <INFO> ------------------BTINS_SetServiceAppProperties-----------------------
    [11:37:21] <INFO> Reading RecoveryScreenImages from registry
    [11:37:21] <INFO> BTINS_ReadIniFile
    [11:37:21] <INFO> ParseIniFile \\server\deploy\HBA\2760\BT\Custom\CustomEn.ctm
    [11:37:21] <INFO> Install BTW Profile Pack
    [11:37:21] <INFO> Install BTW Profile Pack
    [11:37:21] <INFO> Saving RecoveryScreenImages to registry
    [11:37:21] <INFO> Install BTW Profile Pack
    [11:37:21] <INFO> BTW_MINOR_UPGRADE = 0
    [11:37:21] <INFO> Package Code  = {9C152D39-9549-4958-A5E8-9F324DCDDD66}
    [11:37:21] <INFO> BTINS_Install MPT start
    [11:37:21] <INFO> No WID_MPT key
    [11:37:21] <INFO> ------------------BTINS_StartStackServer-----------------------
    [11:37:21] <INFO> BTINS_ReadIniFile
    [11:37:21] <INFO> ParseIniFile \\server\deploy\HBA\2760\BT\Custom\CustomEn.ctm
    [11:37:21] <INFO> Install BTW Profile Pack
    [11:37:21] <INFO> Before start service, dev present 1, secure 0, uhe 0
    [11:37:21] <INFO> [BTINS_StartService] START
    [11:37:21] <INFO>  [BTWDINS] Service Started
    [11:37:21] <INFO> [BTINS_StartService] EXIT
    [11:37:21] <INFO> After start service, dev present 1, secure 0, uhe 0
    [11:37:33] <INFO> WaitWhenServiceSwitchDongle: succeeded after 11 seconds
    [11:37:55] <INFO> CMP_WaitNoPendingInstallEvents2: no pending events during 1000
    [11:38:00] <INFO> CMP_WaitNoPendingInstallEvents2: no pending events during 5000
    [11:38:00] <INFO> BTINS_UpdateDevices for the HW (btwamfl): before updateAllDevices(strArrDongleHwId)
    [11:38:00] <INFO> Test UILevel
    [11:38:00] <INFO> UILevel =  2 (2 = Silent, 3 = basic, 4 = reduced, 5 = full)
    [11:38:00] <INFO> CustomActionData
    [11:38:00] <INFO> updateAllDevices: count 596, InfClass Bluetooth, folder C:\Program Files\WIDCOMM\Bluetooth Software\bin bForceInstall=1
    [11:38:00] <INFO> updateAllDevices: device is found: USB\VID_03F0&PID_231D&REV_0306
    [11:38:00] <INFO> updateAllDevices: inf file is found: C:\Program Files\WIDCOMM\Bluetooth Software\bin\btwampfl.inf
    [11:43:00] <ERROR> updateAllDevices: UpdateDriverForPlugAndPlayDevicesA failed. HardwareId=USB\VID_03F0&PID_231D; err=1460
    [11:43:00] <INFO> BTINS_UpdateDevices: updateAllDevices szSecureDongleHwId
    [11:43:00] <INFO> Test UILevel
    [11:43:00] <INFO> UILevel =  2 (2 = Silent, 3 = basic, 4 = reduced, 5 = full)
    [11:43:00] <INFO> CustomActionData
    [11:43:00] <INFO> updateAllDevices: count 13, InfClass (null), folder C:\Program Files\WIDCOMM\Bluetooth Software\bin bForceInstall=1
    [11:43:00] <INFO> BTINS_UpdateDevices: updateAllDevices szUHEDongleHwId
    [11:43:00] <INFO> Test UILevel
    [11:43:00] <INFO> UILevel =  2 (2 = Silent, 3 = basic, 4 = reduced, 5 = full)
    [11:43:00] <INFO> CustomActionData
    [11:43:00] <INFO> updateAllDevices: count 14, InfClass HIDClass, folder C:\Program Files\WIDCOMM\Bluetooth Software\bin bForceInstall=1
    [11:43:01] <INFO> CMP_WaitNoPendingInstallEvents2: no pending events during 1000
    [11:43:01] <INFO> BTINS_RemoveAllPdos
    [11:43:01] <INFO> BTWPP_RemoveAllPdos

    [11:43:01] <INFO> BTWPP:EnumDevices: guid=0x4d36e96c... bPresent=0 HardwareID={24df01a9-3e4f-4c9f-9f66-5aa8ab14f8f4}

     

    Thursday, December 13, 2012 1:44 AM
  • Hi James,

    Would the " /nw" switch assist with the installation to continue all the way through?

    Honestly I haven't tried it with the /nw switch. The reason is that I'm installing these during my imaging process and I wanted it to finish the install before continuing onto the next item. I didn't want to chance another install being prevented from installing due to the Bluetooth install not finishing. I know it takes a little while to run.
    Thursday, December 13, 2012 2:17 AM
  • I see your install string as: setup.exe sub64 /f2C:\system.sav\logs\btwinlog.txt /qn /ri /nw

    Try changing the /qn to /qr so you can see the installer as it is running. It should continue automatically, but show the full UI of the installer. That way if it fails on something, you should be able to see the actual message. I would remove the /nw as well.

    From the log file, It appears to be erroring out with a 1460 after 5 minutes. If this correlates to a Microsoft code then it translates to a timeout

    Error Codes: http://msdn.microsoft.com/en-us/library/windows/desktop/ms681385%28v=vs.85%29.aspx


    One other thing I just wanted to make sure of. Do you have the Bluetooth device enabled in the BIOS? I believe you MUST have it enabled or else the installer will fail. Please give that a check if you could.
    • Edited by James Ihde Thursday, December 13, 2012 2:30 AM
    Thursday, December 13, 2012 2:28 AM
  • Hi James,

    Yes the Bluetooth is enabled...thanks for being thorough :)

    Best if I put the issue in dot form:

    • Installing the Bluetooth Sofpaq with HP SSM does not work thus times out, stopping the remaining Sofpaq to not install (SCCM errors with a 0x0xxxx type error)
    • Moved on to running another command line to install the Bluetooth separately. The issue is it will sit at this point during the TS for hours if you let it.
    • Manual install (double clicking setup.exe) has the same issue where it sits for ages trying to finish the last part of the installation. The driver itself still gets installed but you have to kill the process in Task Manager.
    • Restarting at this point causes Windows to just sit out "Shutting Down" for ages, then BSOD's with the message in my previous post.

    It seems that the there is something with the bluetooth software and something in the build itself that just isn't talking to each other. HP says that the prerequisites that you must have are:

    1. The Bluetooth Module must be enabled and powered on (yes and its enable in the BIOS)
    2. The Windows 7 Bluetooth Bus Enumerator and Bluetooth Stack must be installed (I believe Windows 7 has this already?)
    3. Wireless Assistant for device control via software (installed as a part of SSM).

    Keep in mind that I had to go down the SSM route because I had a lot of other quirky issues with this tablet PC. Things like the QuickLauch buttons (screen rotate) not working via the INF route.


    Anyway, in the meantime I believe that I have worked out a work around. I have set a timeout of 5 minutes for the Bluetooth driver install and put a check in the checkbox to continue on error. I just tested it and seems to worked as far as allowing the TS to continue. The next thing I am going to try is run a taskkill /im setup.exe /f to make sure that the installer is dead - the theory is that this might assist with stopping the BSOD on shutdown. The BSOD only seems to occur after the first shutdown after installing Bluetooth.

    Sorry for the long posts but I think I making some progress. :)

    Thursday, December 13, 2012 5:28 AM