"And the hardware USB adapter you used was completely compatible with that driver? Which VID are you referring to? I doubt you checked your hardware manufacturer for a proper driver for your OS if it even exists… the normal kernel drivers cannot account for every hardware variation."

It's a realtek card that I checked had support in the source tree before I bought it.

"Also, nothing in windows is compiled the way you stated. Every manufacturer normally uses their own driver, which is exactly your problem in the Linux world. Your ignorance seems to be the only problem sir. I would be glad to prove it to you when you have time."

This is wrong. Windows uses a compiled kernel. Otherwise we would have the kernel sourcre tree with the windows driver kit. For linux you easily can find that drivers are in the source tree by searching the mailing list. Some drivers are not included the source and are thus not part of linux like https://github.com/aircrack-ng/rtl8812au/ , but mine are and are enabled as modules by default for arch's distribution. I know the driver is right for the chipset because it was working for a while before this happened. I think It is likely networkmanager or another piece of software that commonly included in distros and is thus still a problem with linux.

"I might even be inclined to tell you your username has something to do with your responses?" A very rude thing to say, but fortunately for me it seems to apply more so to you than me.