Pro tip: if you have to preface something with "not trying to...but..." you really should rethink what you're about to say.
If you read what I originally wrote, you'll see that I did acknowledge that one of the issues was driver related. Though if you know how to handle a driver conflict when the conflicting items are from the same manufacturer (Realtek) and on the same motherboard (by a little company called Asus, you may have heard of them?), I'm all ears, because that one stumped the entire Asus ROG community last I checked.
But no, it wasn't just that and yes, it really was an update from Windows. In fact, it was an update from October 2018 that was well-known and well-documented to cause the exact issue I experienced (among a host of other issues). And again, this was an issue that even my husband who is a Windows enterprise system administrator (and, since that doesn't seem to be enough for you, has managed the entire infrastructure of some of the largest corporations in the world and very likely knows more about how Windows works -- and how to beat it into submission -- than you do) had no way to prevent said update from installing (thanks, Windows Home Edition!) and the only thing we could do was wait for the (at the time, future) roll-up that would consider that update installed and bypass the issue, because it kept trying to pull the original (broken) version.
I do apologize if I came off rude. I just get red flags whenever custom pc is mentioned. And I am ignorant to Windows in that time frame, I was a full time Linux user then. The few times I have run Windows I have never had anything similar happen to me.... call me lucky.
I have never run win10 home also..so I am ignorant to it a little.
But in general I am a new windows user so to speak so there is a level of ignorance I hold to its past history. Currently though, it has run buttery smooth for me..knock on wood.
Again I apologize if I came off as an a$$
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Pro tip: if you have to preface something with "not trying to...but..." you really should rethink what you're about to say.
If you read what I originally wrote, you'll see that I did acknowledge that one of the issues was driver related. Though if you know how to handle a driver conflict when the conflicting items are from the same manufacturer (Realtek) and on the same motherboard (by a little company called Asus, you may have heard of them?), I'm all ears, because that one stumped the entire Asus ROG community last I checked.
But no, it wasn't just that and yes, it really was an update from Windows. In fact, it was an update from October 2018 that was well-known and well-documented to cause the exact issue I experienced (among a host of other issues). And again, this was an issue that even my husband who is a Windows enterprise system administrator (and, since that doesn't seem to be enough for you, has managed the entire infrastructure of some of the largest corporations in the world and very likely knows more about how Windows works -- and how to beat it into submission -- than you do) had no way to prevent said update from installing (thanks, Windows Home Edition!) and the only thing we could do was wait for the (at the time, future) roll-up that would consider that update installed and bypass the issue, because it kept trying to pull the original (broken) version.
I do apologize if I came off rude. I just get red flags whenever custom pc is mentioned. And I am ignorant to Windows in that time frame, I was a full time Linux user then. The few times I have run Windows I have never had anything similar happen to me.... call me lucky.
I have never run win10 home also..so I am ignorant to it a little.
But in general I am a new windows user so to speak so there is a level of ignorance I hold to its past history. Currently though, it has run buttery smooth for me..knock on wood.
Again I apologize if I came off as an a$$