|
Uugh!!! Good luck with whatever you try. You make me glad I've backed things up to my phone, although Murphy's Law can still strike!
|
|
|
|
|
About a month ago my wife's Dell (W11) got a network driver update... Since then Outlook unable to connect the network (along with other but not all applications)... The truly nice part is that I can not roll back the driver...
Checked on older (W10) Dell she used before and more or less has the same setup - Outlook still works...
Conected Dell, they say it is MS... Didn't asked MS... It is me wife, who refuses to move on to some Linux edition...
“Real stupidity beats artificial intelligence every time.”
― Terry Pratchett, Hogfather
|
|
|
|
|
Have you tried updating to wife 2.0? 
|
|
|
|
|
Good backups?
Another reason to have them.
FYI you can backup Outlook contacts by File Export and selecting whatever format you want. I usually do something like that about 2-4 times a year for contacts. They don't change much. Usually some story like this reminds me to update them.
To err is human to really elephant it up you need a computer
|
|
|
|
|
My kid's PC started having trouble, so he bought a new SSD and has done a fresh install of Win 10 -- from the same disc we installed from before.
But we can't get the network drivers to install.
We tried the flash drive which came with the mother board (MSI). The install app says that it installed the drivers, but after a reboot it reports that they weren't installed.
I downloaded some drivers from MSI's site and Intel's site, but they also say they won't install.
Very frustrating.
Update 5/10: We eventually got it working by using the Windows Media Creation Tool.
modified 10-May-22 8:36am.
|
|
|
|
|
|
|
Well,
Check to see if the driver is superceded. What may be happening is that you install the old working driver, Windows might detect that there is an updated version in the driverstore and uses that one instead. This is to prevent people from installing old insecure/broken drivers.
windows 10 remove driver from driverstore - Google Search[^]
Remove ALL drivers from the driverstore associated with the device and then try installing your old working driver. If it still doesn't install then check if the driver certificate has been revoked.
I'm leaving in about an hour but you should have a Setupapi.dev.log[^] in %windir%\inf that will give verbose info about the device install.
|
|
|
|
|
It can't get to a store or Windows update until the driver is installed.
|
|
|
|
|
PIEBALDconsult wrote: It can't get to a store or Windows update
The driverstore is on your local computer... nevermind, just bring it to a qualified technician...
|
|
|
|
|
Did you confirm that the network card is active in the BIOS with all the default settings?
|
|
|
|
|
The network was working previously, with the old system drive.
I see lights flashing on the ports on the motherboard and switch.
|
|
|
|
|
Does he still have the HDD? You could try cloning the working Win 10 to the SSD.
|
|
|
|
|
Could, it's in the system so he can transfer any files he needs.
But cloning it would only clone whatever problem it has.
|
|
|
|
|
Are you using Windows Home? That does not support a lot of network capabilities. Even my son installs Windows Pro at home.
|
|
|
|
|
|
Could the start of it having trouble maybe be that the NIC took a shock?
|
|
|
|
|
I don't think so, it appeared to be a bad update of something, but maybe.
I would still assume it would install the driver though.
|
|
|
|
|
The NIC having a hardware issue could explain it having difficulty installing the driver.
What caused that issue could be anything. Since the driver was already on the old system, the issues of something going wrong with the NIC would have manifested differently.
It's possible that you could now install some old network driver but not the latest driver.
You may have to flash the BIOS to the most receent version before the most recent network driver will install.
If you flash to the latest BIOS and the driver still won't install, I think the NIC has gone bad.
Motherboards are expensive so you probably want more proof of that than a forum post.
Alternatively to a whole new motherboard, if there are open PCIE slots, you could more cheaply just disable the onboard NIC and just put a new NIC card in (~$25-$50?).
|
|
|
|
|
If you're able to boot from the old drive, try getting the drivers with Double Driver, this is an old program that lets you grab the drivers your current Windows set up has, this is a very old program (Works fine even on Windows 11 last time i tried) so you won't find a official download site, but you can find it floating in the net.
"Science fiction is any idea that occurs in the head and doesn’t exist yet, but soon will, and will change everything for everybody, and nothing will ever be the same again." Ray Bradbury
|
|
|
|
|
You can get an el-cheapo USB WiFi adapter from Amazon for as little at $10 and a PCI 1Gb network card for not much more. That will at least get you on the internet. You said the PC was "having trouble". What was the trouble? Is the network adapter on the motherboard? Almost all motherboards these days have one.
|
|
|
|
|
Couple of quick questions:
- Was the original Windows 10 system, that started having trouble, a system that was upgraded from a previous version of Windows?
- If so, what version?
I had this trouble on a system that was upgraded from Windows 10 to Windows 11 with printer and audio interface drivers. The manufacturers indicated that the driver was compatible with Windows 7, 8, 10 and 11, but on my Windows 11 system, they were not fully functional, even though they installed without issue.
I had the same drivers running on another system running Windows 7, and they were running as expected.
I got the drivers to install and run successfully on my Windows 11 system by simply invoking the setup programs in Windows 7 compatibility mode. You do that by selecting the setup program and right-clicking to bring up the context menu and select properties. There should be a compatibility tab with a drop-down list where you can set the executable context to run under Windows 7 compatibility mode.
You might want to try that and see if it works.
|
|
|
|
|
Member 14573475 wrote: upgraded from a previous version of Windows?
Of course not.
Member 14573475 wrote: installed without issue.
These refuse to install. Or say they installed when actually they hadn't.
A colleague has suggested another option I'll have to try.
|
|
|
|
|
My someone else's code that I'm currenctly working on breaks with a NullReferenceException, except...
The exception seems to have to do with lazy loading in entity framework.
When I set a breakpoint and inspect some variables quickly enough they're null.
After that the code stopped executing a few seconds and everything runs fine.
When I don't set a breakpoint it breaks because some variable is null.
When the code breaks and I inspect every variable in the block, nothing is null.
Weird issue, I've never seen it before.
So naturally, I google for "nullreferenceexception "FixupSkipNavigations"" (FixupSkipNavigations is where the exception occurs and I have little else to go by).
Well, Google it for yourself... No results 
I get a yeti who's ice fishing and catches a boot, an empty can, a can of sardines or a fish when you click it.
THIS IS NOT HELPING 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
