Member Avatar for Tamirul

well, i'm quite sure my modem is physically okey. but i guess it's the modem software what's disturbing. programme is stuck in "initializing" loop forever. i've tried reinstalling the software, updating the driver, rolling back the driver, reinstalling the driver, checked network driver, even resetting the windows.

but nothing worked.

as a matter of fact, this very modem is working fine in my another PC. which is also windows 10.

a screen shot is given. anyone giving a solution will be treated thankfully.

Flash_Modem.PNG 582.97 KB
  • 3 Contributors
  • 2 Replies
  • 574 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by jessicaaustin

Dani AI

Generated

Practical, focused checklist to troubleshoot a modem that stays stuck in an “initializing” loop on Windows — expands on observations from and the hardware-swap idea from with concrete, high-value diagnostics.

  1. Remove ghost/leftover drivers and hidden COM devices: enable non-present devices in Device Manager, show hidden devices, and uninstall any greyed-out modem/COM entries (use the “Delete the driver software for this device” checkbox where present).
  2. Fully remove vendor management software and services before reinstalling drivers; check Services (services.msc) for any modem-related service that auto-starts and stop/disable it while testing.
  3. Disable USB power savings (Device Manager → USB Root Hub → Power Management and Power Plan → USB selective suspend = Disabled) and prefer a rear panel USB 2.0 port (chipset-host differences matter).
  4. Clean-boot Windows (msconfig: hide Microsoft services → disable third-party services) to see if a third-party utility blocks initialization.
  5. Reset the network stack and Winsock, then reboot:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc

netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
  1. Check Event Viewer (System/Application) at the time the modem tries to initialize for driver, Service Control Manager, Kernel-PnP or setupapi errors — event text and error codes point to whether Windows or the vendor software is failing.

Advanced: use Sysinternals Autoruns to find leftover startup entries, and Process Monitor to capture what the modem-manager does during startup. A Live Linux USB boot is a fast, non-destructive hardware-vs-OS test if swapping hardware isn’t convenient. Firmware updates for the modem and up-to-date motherboard chipset/USB host drivers are worth checking before replacing hardware.

Useful diagnostic artifacts for deeper analysis: modem model/vendor and exact vendor software name/version, Windows build, Device Manager screenshot with hidden devices visible, and the Event Viewer error entries (time-stamped).

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

Modems come in various designs. We have classic ones that connect to some RS232 Serial Port that we rarely have to install any drivers and can test with AT commands, then WinModems that were slipped into some PCI slot and were generally thought to be the Devil's spawn. Now we have USB Modems that well, don't work at all on most PCs except when you follow the directions.

You may have to tell a lot more.

Edited by rproffitt because: Spelling.
Member Avatar for jessicaaustin

Please try to use the modem in other pc or try a diffrent modem in your pc by this you will find problem if other modem does not work with your then it must be your mother boards fault

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.