Windows 10: New Network Card, No WiFi

A two-hour call with Dell convinced them that my network card was failing, so the next day a tech installed a new card. No matter what I have done, no matter what a support agent did during a four-hour phone call, this new card will not find my local WiFi network, it will not even find a network I set up in the DSL modem.

I finally convinced Dell to provide, on a one-time basis, a second card, but today, they cancelled the order on the blatantly incorrect basis that our ISP was at fault. I had the ISP check, no problems found. My wife's computer is connected to WiFi, as is the printer; as part of my testing, I disconnected the router from the DSL modem, and could still print from her computer. (Why a DSL modem with WiFi and a router? I had the router set up when the previous DSL modem failed, so set up the new modem and connected it to the router, rather than entering all the MAC addresses, etc., in the new modem.)

I have read numerous ways of fixing the problem. While I am not sure of everything that the agent on the four-hour call did, I believe that she did some of the tricks of refreshing various Windows components, etc. I have run out of things to try, have more or less exhausted the on-line suggestions, etc., and have sent a detailed email to Dell outlining why it appears to me that the only thing that does not work is the new card's ability to find and use WiFi.

Next, other than applying my ten-pound sledge hammer? I even started Windows in Safe Mode with Networking, only to find that the WiFi card cannot be loaded there-and on, and on, and I'm tired, frustrated, and any assistance offered would, of course, be appreciated.

:)

 

Question to Nokia Asha users facing WLAN issues

wlan is not concerned with sim card, it is concerned with wifi device or wifi router, it must be saves when i wanted to save it by saving its password but in nokia asha 210, new added network cant be saved. moreover , if i connect to the network it break
every single minute and says network not available while that same wifi works on my nokia C3 perfectly.

 

I have windows 10 and i have 150 mpbs speed but my computer is getting 50 MBPS

You cannot change a setting or protocol, you will have to buy a new Network/WIFI Card - they are available on the Web for as little as $5

 

If you can, try rolling back to a restore point or backup before KB3201845 appeared on or about 12/9. There's a bug in that update which kills DHCP for many users, and causes weird networking problems -- like yours -- for others. You may have to hold off on updates for a while, but at least you'll be able to access the Internet/network. You can always revert back to a more current restore point or backup should you need to do so, so make one of each right away before you start the rollback process.
HTH,
--Ed--

 

Thanks, but according to this, the first article my search found:

http://www.computerhope.com/issues/ch001048.htm


DHCP is enabled, and, of course, I did not encounter the update problem, given that the older WiFi card was working yesterday from around 0600 t0 around 1200 local, when I stopped and shutdown as I expected the tech to arrive shortly.

 

Rats! Sorry this offers no relief to you. Hope you find a solution. Please do let us know how your tech visit turns out, and best of luck.
--Ed--

 

I don't know how this will turn out: I finally convinced Dell, yesterday, to provide a second new card; this morning, again blaming the ISP, they cancelled.

The mystery and major frustration continues: Shortly after I posted my previous message, I lost internet connection, and had to run two different troubleshooters. The second one said that I had no IPV4 (or whatever it is, I'm too confused by all the problems to remember, that is my feeble excuse.) At any rate, it stated that it could fix the problem by a restart which would do several things, so restart it was, and internet connection was re-established.

The saddest part of this was that, when I tried, yet again, to access our local Wifi for the first time in many attempts, it said that is was connected and working, but promptly failed. Mega Sigh.

 

An email from Dell states that my case is being reopened; apparently my proof (for so I consider it,) was convincing.

A phone call from a local UPS supervisor said that drivers have been instructed, again, not to leave packages unprotected in the rain. At this time of year, it should be snowing here, not raining, but I don't know with whom to lodge a complaint.

 

If you get a chance, run this script on the computer and upload the log created on the desktop. https://windowsforum.com/threads/net...mation.223812/

 

I ran it several times, it never created a file.

 

You may need to right click on the script > properties and select unblock.

 

I don't see anything about unblock in properties. I did, however, run the script as admin, which ran much longer than when simply clicking on it. That still goes rather quickly, of course, but I did see more than one instance of something to the effect that what was called for could not be done, and when the script ended, it still did not create a file.

The only network I have is the Ethernet one created by my plugging into the DSL modem in order to get on-line in the absence of WiFi.

 

After fighting with Dell tech "support," which kept raising spurious reasons for the problem, cancelling scheduled home visits as covered by my warranty, wasting my time and theirs in lengthy, meaningless phone calls, and so on (and on, and on,) I found a phone number for a part of Dell that deals specifically with warranty problems.

That call took another ninety-plus minutes, but resulted in my computer being shipped to the repair depot; even that was not easy, as the box that Dell sent was too small for the computer. To avoid still further delay, I paid for a proper box; I doubt seriously that Dell will ever reimburse me.

It did not surprise me to find that the repair depot found a faulty network card. I cannot state with authority that what they found was that the card installed at my home was at fault, as the depot's on-line statement is quite short, referring only to what I assumed was the actual part, and when I Googled that, all I found that the part is a network card for Dell Inspiron laptops, which I don't own.

At any rate, after my telling tech "support" many times that there was a hardware fault, that is exactly what the tech at the repair depot found. The computer is now awaiting delivery, but as FedEx is closed today, I don't expect to receive it until Wednesday. I certainly expect that when I turn on the repaired machine, I shall find that WiFi has been restored.

If I should receive a survey about this extremely poorly-handled case, my replies shall be of a rating well below zero.

 

Hopefully, when you receive the machine back from the depot, the WiFi will actually WORK! TBD, I guess...
Best wishes for 2017, too.
--Ed--

 

"Have mercy on oure woe and oure distresse." Chaucer, The Canterbury Tales: The Knight's Tale.

Continuing the saga, the computer was shipped last Saturday, for two-day delivery,, but as Monday was a holiday, delivery was scheduled for Wednesday. In checking the FedEx tracker Tuesday morning, it suddenly changed to state that, as the business was closed, the package could not be delivered, and there was no known delivery date. I managed to get an on-line chat with a FedEx specialist (don't recall the specific title,) who investigated, and told me that was an internal message, not really intended for me.

Computer was delivered yesterday; the depot report stated that the network card had been replaced, as had Windows 10. This entire episode was absurd: A new card was installed at my house, which did not work; the tech opened a new ticket, gave me the number and the phone number to call. That conversation began with the Dell employee making the preposterous claim that my ISP must have changed its configuration during the short time that my computer was turned off. I rebutted that by pointing out that my wife's computer and my smart phone continued to work correctly.

Suffice it to say that, over a period of more than three weeks, what ought to have been done the day after the new card was installed, a second card was installed at the Dell repair depot in Houston, Texas--and I had to spend ovre $24.00 to avoid waiting a few more days for Dell to send a return carton that the computer would actually fit into.

Opened return carton, plugged things in, started computer, which very quickly recognized my WiFi network, but could not connect. After two or three tries, it occurred to me that the MAC address had likely changed, so I used my wife's computer to disable MAC, whereupon my computer connected and proceeded to set up the new instance of Windows 10.

When that finished, I installed Macrium Reflect, changed the bios to boot from the DVD drive, where I had inserted my Reflect rescue disk, and proceeded to restore my computer to the state it had been in the morning of 27Dec2016, before shipping it.

According to Reflect, the restore had been successful, but to my great dismay, the computer would not boot into Windows. (I did notice, in changing the bios back to normal, that there were two entries for Windows boot, which I thought was odd.) I tried a few different ways, whereupon a built-in Dell repair module started, but that ended with a message that it could not fix the problem.

Reset bios to DVD, started the Macrium rescue, quickly found, top left on the screen, a `fix boot' entry; ran that nearly instantly indicated that there was one file too many. Given my state of anguish, I paid little or no attention to what that file was called, just told Macrium to fix the problem. It did, I booted into Windows, and opened my Windows profile as it had been on 27Dec., with WiFi working.

There is more, but this is enough, so I will conclude by stating that, this morning, I got a welcome email from a man who is covering for woman had been dealing with, in response to my email to her yesterday that the computer was now working, but that I was still very upset by the way that this case had been totally mishandled. The man asked if we could discuss this in a phone call, to which I replied that I appreciated the offer, and told him when he could call.

(As an aside, the woman had sent me an email yesterday stating that their FedEx records showed that the computer was scheduled for delivery to the depot yesterday. I corrected that inanity by pointing out that the FedEx record actually showed that the carton had been loaded on truck for delivery to me, not to Dell, a few hours earlier.)