Windows 10: Wireless Driver not functioning properly after several fix attempts

And there is no Exclamation Mark on it? If, not it is OK and you should be able to Update Online the Driver. And it should be also working.
If it is installed correctly, look in Driver, Advanced Settings for the Settings of your Card.

 

to check if and repair System :
in Elevated Prompt type : SFC /Scannow
If it reports it could not fix all errors you have to run a System Image Cleanup
in elevated Prompt type:
DISM /Online /Cleanup-image /restorehealth /source:X:\sources\Install.wim /limitaccess.
Assuming you a ISO and a WIM Install and you have Mounted the ISO.
Further Information:
DISM - Repair Windows 10 Image - Windows 10 Forums

 

The Scan reported this: (as you said)
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

Though the log file is pretty big, is there any part in the log I should be looking for?

 

You could try doing a repair install. Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

 

The best way and more easy is to proceed with DISM as Stated above.
You can do it on-line, so you do not need a ISO or what ever
Just type this in a elevated command prompt
DISM /online /Cleanup-Image /Restorehealth
It takes some time.

EDIT: After DISM has completed sucessfully you need to re-run SFC /Scannow.

 

I can try it, though it will require me some time as my internet speed is not something to brag about

Also, the DISM returned this:
C:\Windows\system32>DISM /online /Cleanup-Image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[===========================95.0%======================= ]
Error: 1726

The remote procedure call failed.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

OK. I had that error with DISM some time ago and I do not recall how I solved it. I have seen some else here in Forum with the same error, and I was thinking how I solved it, but I can´t recall.

If you have the Last Update as a File (KB) saved on you PC, I would uninstall the Update a re-install it.
If not, probably the Best is to do a in-place upgrade as Winuser said.

 

Where should I find this update file.
And for the In-place upgrade, it will have to wait a lot, basically for me to download it

 

if do not know where to look for the KB file, then I have not downloaded it. Forget it.
It is not easy to get problems solved, it is time consuming and people have to have a lot of patience.
You will need to do the in-place upgrade.
Any way, your current config is not working, so you may try to Uninstall the Upgrades you have a see if helps, before you proceed with in-place upgrade.

EDIT: I understand your Problem with your poor Internet connection.
Do you have a System Image from previous OS that you can go back? That could be a good choice for you.
Do you have any how "at home" some ISO/DVD or in PC a Recover Option to your previous OS? That coulde be also a good choice for you.
Well, I want to help you, but sincerely I do not know any further.

 

Okay I did the in-place upgrade and it's working again! I almost can't believe my eyes
Thanks a lot Winuser

 

Well, everything just can't end too well...
After the in-place install, even though the wireless problem was fixed, after like 10-20 seconds into the desktop the explorer freezes:
I can't access the task bar or start menu
I can't Alt tab or Windows Tab
I can't even Alt-Ctrl-Del
I didn't even do anything yet after the upgrade

Something to note is that everything is fine if I run Windows in diagnostic boot

Edit: small update; it seems something is wrong with the system services, disabling all startup items makes no difference
Basically the OS does not freeze if in:
- Safe Mode
- Diagnostic Startup
- Selective startup with most system services disabled (default)

Edit 2: After I isolated the problem (that a Microsoft Service was causing this) I tried disabling all Microsoft services and enable all non-M services
Windows booted normally, then I started enabling services 10 by 10 to see which caused problems until I narrowed down till I found that the service App Readiness was responsible for all this