I have a code 43 with my wireless connection. this apparantly a registry problem. Does Webroot fix rgistry problems?
Page 1 / 1
Have you recently installed a new device?
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
You can also try to power off your computer completely (not just a reset) and then turn it back on after about 30 secs. Especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Keep us posted!
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
You can also try to power off your computer completely (not just a reset) and then turn it back on after about 30 secs. Especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Keep us posted!
Hello Oesterreich12, welcome to the Community!
WSA does not have a registry checker: it was designed to protect against malware and do so very well but in as small a package as possible. For that reason, it is not a general system tool.
My own opinion is that most Registry Checkers are rather risky, even the legit ones. There are just so many ways in which they can go wrong. The really big problem is that so many free utiilties that promise to clean or fix the registry are nothing but adware or malware themselves.
I would suggest that unless you are very experienced, you do not attempt registry repairs yourself. One thing that might well correct the issue is to simply re-install the drivers for your computer's WiFi interface.
Another possible fix would be that if the problem came up right after installing new hardware or software, simply do a Windows Restore back to the last known good configuration, such as the day before the problem started. Be careful not to do a full restore back to original specs or you will lose all data so read everything carfully to make sure you have chosen the correct options.
WSA does not have a registry checker: it was designed to protect against malware and do so very well but in as small a package as possible. For that reason, it is not a general system tool.
My own opinion is that most Registry Checkers are rather risky, even the legit ones. There are just so many ways in which they can go wrong. The really big problem is that so many free utiilties that promise to clean or fix the registry are nothing but adware or malware themselves.
I would suggest that unless you are very experienced, you do not attempt registry repairs yourself. One thing that might well correct the issue is to simply re-install the drivers for your computer's WiFi interface.
Another possible fix would be that if the problem came up right after installing new hardware or software, simply do a Windows Restore back to the last known good configuration, such as the day before the problem started. Be careful not to do a full restore back to original specs or you will lose all data so read everything carfully to make sure you have chosen the correct options.
Thank you very much. Not comfortable finding my way around blogs but disabling driver and enabling worked beautifully. Thanks for the help and the quick response.
You are very welcome and we are all delighted your problem is solved. Welcome to the Community and drop by often.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.