|
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 
|
|
|
|
|
|
Nope.
Apparently I was using a single property for two separate navigation properties, which "sort of" works 
Weird behavior and weird error though
|
|
|
|
|
This "fixer upper" appears not to be part of the "public API" for EF. My first impression is to comment it out. Sounds like someone's (GitHub) "Hail Mary" for a situation that may not even exist. Like "garbage collecting" when it isn't necessary, effective or understood.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
The code only uses "official" code.
No "someone's quick 'n' dirty fix from the internet" code.
Fixed it though, apparently I was using a single property for two separate navigation properties, which sort of works
Weird behavior and weird error though
|
|
|
|
|
I'm not a C# dev but the commit for that code[^] appears to imply that the switch "Microsoft.EntityFrameworkCore.Issue23659" can be used to avoid that code path.
I'm heading out the door, be back in a few hours.
|
|
|
|
|
Already fixed it.
Used the same C# property for two separate navigational properties.
Which "sort of" works, apparently
The exception really doesn't make sense though, as do the symptoms
|
|
|
|
|
Sander Rossel wrote: 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.
I tried putting in spaces for the phrase "null reference exception" and I get:
Quote: Try using words that might appear on the page you’re looking for. For example, "cake recipes" instead of "how to make a cake."
Well, I guess you should make a cake. 
|
|
|
|
|
When life gives you NullPointerReference exception, make NullPointerReferencake
|
|
|
|
|
Look for WeakReference in the code. There's also Lazy<t> but I doubt that's causing it because it's thread safe, at least if you set it up to be - it's worth looking for those too. though.
Another thing to look for is harder to search for, but the lazy init pattern used in older code. You'll find it hidden behind property accessors usually. Replace it.
To err is human. Fortune favors the monsters.
|
|
|
|
|
It was none of that.
The code doesn't use WeakReference (nor does any code I've ever seen).
I used the same C# property for two separate navigational properties in EF.
Which "sort of" works, apparently.
The exception really doesn't make sense though, as do the symptoms
|
|
|
|
|
Sander Rossel wrote: I used the same C# property for two separate navigational properties in EF.
Which "sort of" works, apparently.
The exception really doesn't make sense though, as do the symptoms
Sounds like someone is using ReferenceEquals instead of an actual value comparison.
Software Zen: delete this;
|
|
|
|
|
Nah, I don't think I've ever seen ReferenceEquals in C# code, because why would you ever want to know that?
The problem was more like:
someEntity.HasMany(x => x.FirstList).WithMany(x => x.OtherList).UsingEntity<...>(...)
someEntity.HasMany(x => x.SecondList).WithMany(x => x.OtherList).UsingEntity<...>(...) Changing that second line fixed the issue.
someEntity.HasMany(x => x.SecondList).WithMany(x => x.SecondOtherList).UsingEntity<...>(...) Not an obvious error, compiles fine and everything.
|
|
|
|
|
Sander Rossel wrote: I don't think I've ever seen ReferenceEquals in C# code, because why would you ever want to know that?
I've used it a few times, mostly in collections and n-way tree structures to identify specific instances.
Software Zen: delete this;
|
|
|
|
|
I did see this before.
I even had the case where the debug build would work and the release build did not, for what I can only guess would be a similar reason.
Don't remember how I solved it though.
|
|
|
|
|
I used the same C# property for two separate navigational properties, which "sort of" works, apparently.
The exception doesn't make sense though, so it seems to be quite a specific error.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
