Latitude

Last reply by 01-01-2020 Solved
Start a Discussion
2 Bronze
2 Bronze
46682

Latitude 5400 - "Configuring mobile broadband device" - no WWAN hardware is present

Newly imaged system.The message below appears at login after each restart. It fails and disappears after a minute or so. I've run Dell Command Update and installed all the latest - no help. There is no Broadband card in the system (BIOS "Cellular Device" = none). I've also unchecked WWAN/GPS in the Wireless Device Enable section of the BIOS. Also no help.

broadband error.png

 

Solutions (2)

Accepted Solutions
44239

I have a workaround now.

Had to run procmon to capture what was going on. The process is "FwUpdatePro.exe".
The workaround is to edit %systemroot%\Firmware\FWSwitchbin\fbconfig.ini as admin.
Uncomment the line "FLASH_SIM_NEED = 1" and save the file.

Reboot and the firmware update no longer runs. Obviously not fixing the root cause, but at least it works.

Pretty sure this came from the Dell driver CAB's for Intel rather than from Dell Command Update. The fact that it's trying to update non-existing hardware tells me something's broken in Intel's driver pack.

View solution in original post

43761

Can also confirm same issue experienced here.

Drivers were installed using Dells CAB driver pack version A00. (The latest CAB at the time of packaging in SCCM.)

I've since checked the CAB listing and it appears that Dell has released an updated version which includes changes to the "Dell Wireless 5820e Intel XMM 7360 Firmware and GNSS Driver". I believe this was the culprit as the updated driver pack does not appear to have the same issue.

To anyone still having this issue from an install using CAB drivers, try using the latest CAB driver pack:
https://www.dell.com/support/article/au/en/audhs1/how16934/latitude-5400-windows10-driver-pack?lang=...

View solution in original post

Replies (13)
6 Indium
44150

Have you physically checked that the WWAN card is present?

 

It is rare for WWAN hardware to included in a standard laptop purchase.

44240

I have a workaround now.

Had to run procmon to capture what was going on. The process is "FwUpdatePro.exe".
The workaround is to edit %systemroot%\Firmware\FWSwitchbin\fbconfig.ini as admin.
Uncomment the line "FLASH_SIM_NEED = 1" and save the file.

Reboot and the firmware update no longer runs. Obviously not fixing the root cause, but at least it works.

Pretty sure this came from the Dell driver CAB's for Intel rather than from Dell Command Update. The fact that it's trying to update non-existing hardware tells me something's broken in Intel's driver pack.

42761

What do you mean by uncomment?  Change the value from 1 to 0?

44150

@floydrayguidry I believe he means remove the line of text so that it no longer executes that and looks for the hardware.

Alan

DELL-AlanD
Social Media Support
#IWork4Dell
I'm based in the UK and I'm usually available Monday to Friday 9am-4pm GMT
Get Support on Twitter @DellCaresPro

43762

Can also confirm same issue experienced here.

Drivers were installed using Dells CAB driver pack version A00. (The latest CAB at the time of packaging in SCCM.)

I've since checked the CAB listing and it appears that Dell has released an updated version which includes changes to the "Dell Wireless 5820e Intel XMM 7360 Firmware and GNSS Driver". I believe this was the culprit as the updated driver pack does not appear to have the same issue.

To anyone still having this issue from an install using CAB drivers, try using the latest CAB driver pack:
https://www.dell.com/support/article/au/en/audhs1/how16934/latitude-5400-windows10-driver-pack?lang=...

2 Bronze
2 Bronze
42901

I was dealing with the same issue but found a fix.

I just finished building a new 5400 out of the box that I got a few weeks ago.  We use Microsoft SCCM to do the builds.  Upon booting into windows the error would popup up.  I actually ran the Dell Command Utility along with going though the bios.  I finally did another reboot and watched the error popup.  Upon that happening I did some backwards troubleshooting.  Found out the process started from C:\windows\firmware\FWSwitchbin.  I then chased it back further and found a service called FirmwareSwitchService.  I stopped the service and also changed it from auto to disabled.  I rebooted the laptop and no error.  I did some looking and found out what the application does it is looks for a mobile card (cell card) and then writes the firmware to match the carrier.  However, we don't install cell cards to our systems are erroring out.

So the fix is to disable the service.  We are thinking about doing this as a group policy or tweak our SCCM build so it is disabled right up front.

Hope this helps anyone having issues.

42810

@jasonwired thanks for the workaround that you have discovered.

Can I ask what CAB file you were using for your deployment as the latest ones have the most up to date drivers that address the issue.

Alan

DELL-AlanD
Social Media Support
#IWork4Dell
I'm based in the UK and I'm usually available Monday to Friday 9am-4pm GMT
Get Support on Twitter @DellCaresPro

42740

I'm not sure what our SCCM team is using for the build but I downloaded the CAB file from Dell last week and reinstalled the wireless and network card which did not fix the issue.

42724

I should add we have the Intel® Wireless-AC 9560 cards installed.

Latest Solutions
Top Contributor