Sign in

my desktop has no internet and device manager blames the pcie wi-fi card

broadcomcode-43device-managernetwork24 replies 路 755 views 路 started
Reply
  1. Theo Lund
    @patch_builder

    hmmmm ok so my PCIe Wi-Fi card reports Code 43 now.

    USB Audio Device Properties

    USB Audio Device Properties
Device status:
This device cannot start. (Code 10)

{Operation Failed}
The requested operation was unsuccessful.

    ive read that Code 43 can mean the hardware failed, but teh timing with teh Ethernet NIC NetXtreme Desktop Driver update is too perfect. my desktop is offline until this is fixed. id like a solid plan: what to test, what to download on another device, and what to install in which order. any help is hugely appreciated.

    1
  2. Emeka
    @emekab676

    hmmmm quick q does teh Windows inbox driver also give Code 43?

    RAM prices doing their own thing again smh

    1 1 helpful
  3. Fenna Tanaka
    @fennat555

    wait what respectfully disagree, i tried that and it made ethernet worse... pro tip: write down what u change... i didnt and had to redo device-manager from scratch

    1 0 helpful
  6. Emeka Larsen
    @cipher_nomad

    ahh classic honestly just reset the fan curve and save yourself the pain. my office machine is officially haunted fingers crossed 馃

    lol

    1 0 helpful
  7. Fenna Tanaka
    @fennat555

    oh ive been there lol for USB adapters, try a different port and cable, ideally a rear port 馃槄 for PCIe cards, reseat the card. code 43 on USB devices is also common with marginal power.

    0 2 helpful
  9. Fenna O.
    @fenna.okafor
    in reply to @earlygarage-3u3

    im literally losing my mind here reading this at 2am instead of sleeping, no regrets im about to throw this thing out the window lol

    2 0 helpful
  10. Tess Jensen
    @tjensen

    ok so uninstall the device in Device Manager, tick Attempt to remove the driver for this device (or Delete the driver software), reboot, and let Windows use its inbox driver. If the inbox driver also gives Code 43, suspect firmware or hardware. fingers crossed 馃

    thinking

    4 0 helpful
  11. Tomas Halvorsen
    @binary_pusher

    Check Fast Startup and disable it while troubleshooting (Power Options > Choose what the power buttons do). It can keep teh adapter in teh failed state across shutdowns. fingers crossed 馃

    2 1 helpful
  12. Kenji B.
    @heapgremlin
    in reply to @binary_pusher

    ok so on another device, download the network driver from teh PC or motherboard makers support page, copy it via USB, and install. Use pnputil /add-driver <folder>\*.inf /install if the package only contains INF files.

    lol

    1 2 helpful
  13. Nina Reid
    @earlygarage-3u3

    @heapgremlin nah thats not it, ethernet has nothing to do with it but hey ymmv

    nothing is more permanent than a temporary workaround

    lol

    15 0 helpful
  14. Greta A.
    @gretaa265

    hmm idk everyone keeps saying this but nobody posts proof... this... so much this

    14 0 helpful
  15. Tess Jensen
    @tjensen

    oh also i come back to this thread every week just for the drama :)

    23 0 helpful
  16. Emeka Larsen
    @cipher_nomad

    ok so following, having the same problem fingers crossed 馃

    0 2 helpful
  17. Una Schmidt
    @heapnomad-3ep

    @emekab676 thank u this worked!! seriously made my day 馃槶馃檹

    thumbsup

    1 0 helpful
  18. Tess Jensen
    @tjensen

    Code 43 means the device reported a failure to Windows. First do a full power drain: shut down (Shift + Shut down), unplug for a minute (remove the battery if possible), then boot :D Network chips can get stuck in a bad state that only a power cycle clears.

    lol

    2 0 helpful
  19. Selin W.
    @cipher_sage

    yeahhh if the adapter keeps failing on every driver and after a power drain, test it in another PC if possible, or use a cheap USB adapter temporarily while u arrange a replacement or warranty. fingers crossed 馃

    1 2 helpful

Reply to this topic

Sign in or create an account to reply.