
169 IP address error can stop your computer from connecting to the internet which could be a very frustrating experience. In this guide, we will cover simple but effective tips on how to fix this error so you can continue with internet use.
Simple and sometimes effective solution, unplug and plug back in modem or router so IP is fetched again, it is very likely that computer will pick right IP address with this stunt.
Press ⊞ WINDOWS + X top open secret menu
Go to settings
Go to Network & Internet
Inside click on Network troubleshooter
Follow onscreen instructions
After the troubleshooter ends reboot your PC
Press ⊞ WINDOWS + R to open the run dialog
Inside run dialog type ncpa.clp and press ENTER
Right-click on your network adapter and select properties
Uncheck Internet Protocol Version 6 (TCP/IPv6) and click on OK
Now press ⊞ WINDOWS + X and click on Command prompt (admin)
In command prompt type and after each line press ENTER
netsh winsock reset catalog
netsh int ip reset reset.log
ipconfig /release
ipconfig /renew
Reboot your computer
Press ⊞ WINDOWS + R to open the run dialog
In run dialog type services.msc and click on OK
Find DHCP client
Right-click on it and choose Restart
Reboot PC
Press ⊞ WINDOWS + X to open the windows menu
Click on Device Manager
Expand Network Adapter and right-click on wireless or ethernet adapter, click on Uninstall device
Reboot the computer to automatically reinstall the device driver
Press ⊞ WINDOWS + R to open the run dialog
In run dialog type in ncpa.cpl and press OK
Right-click on your network adapter and select properties
Uncheck Internet Protocol Version 6 (TCP/IPv6)
Double click on Internet Protocol Version 4 (TCP/IPv4)
Select Use the following IP address and change it to 192.168.0.1
Change Subnet mask to 255.255.255.0
Leave default gateway blank
Click OK to save changes
“Oops... the system encountered a problem (#707)” “Server error occurred and your email was not sent (error 707)”
“SYSTEM [DRIVER] USB AUDIO DEVICE An audio stream is currently in use [DRIVER] Legacy Kernel Caller.”Step 2: The next thing you have to do is remove all the external hardware connected to your computer. In this step, you have to disconnect external hardware from your computer. Based on reports from users who experienced the same issue, the “TV card” is the culprit so make sure you remove that one. Once you’ve removed it, open Command Prompt and run the “powercfg –requests” command again and you’ll see that the “Legacy Kernel Caller” will no longer be on the list. In addition, your computer will get into its regular sleep mode once the hardware is removed. Once you do that, the driver gets hung and won’t release the power request despite being used. Step 3: Try using the request override option The powercfg command also offers a request override option which allows users to disable the requests from applications and services to wake the computer from sleep mode. To run this command, simply open Command Prompt with admin privileges. After you open Command Prompt, type the following command and hit Enter to disable requests from applications and services that causes the computer to wake from sleep state.
Powercfg -requestsoverride Driver "Legacy Kernel Caller" SystemStep 4: Check the streaming and media applications You also have to check if your computer is running an audio or video service in the background. In such cases, your computer won’t be able to go to sleep mode if these services are running in the background. You might have noticed that when you play a video or audio, your computer never goes to sleep. And if you have put it to sleep in between watching the video, then it’s probably why your computer is waking up. Thus, you have to stop these services. Step 5: Check the devices that can wake your computer If you didn’t see the Legacy Kernel Caller in the result after you execute the ”powercfg –requests” command, then you can try to execute the following command instead.
powercfg –devicequery wake_armedAfter you enter this command, it will give you a list of all the devices that can wake your computer. So if there is anything other than the mouse, keyboard, touchpad, you have to check the power configuration of that device. To do that, go to the Device Manager and disable the device’s “Allow this device to wake the computer” option in its Properties Step 6: Check the Sleep Advanced Settings
Upon updating to Windows 10, some users might encounter a blinking or flashing desktop after logging in. This will result in a repetitive restarting of explorer or you won’t be able to make the start menu and shortcut keys work. In addition, the network icon might not appear in your taskbar as well. Other Windows 10 error messages include error code 0xc000021a.
Your blinking or flashing desktop after logging in might be the result of problems with the bushell.dll shell extension, which is a part of the Norton Security Suite. Another possible cause for this annoying problem is an issue with your display driver since not all systems will use the same display driver and will depend on what graphics card you use.
In fixing the bothersome blinking or flashing desktop after logging in problem, you can do a manual repair method to address the root problem. You need to be familiar with the Windows command line to successfully go through the process. However, if you are not knowledgeable or confident enough to do this on your own, it would be best to seek help from a professional. Or, you might want to consider using an automated tool to solve the issue.
You need to identify first what’s causing the blinking or flashing of your desktop after login to properly address the issue. The following methods can be done if your issue is caused by bushell.dll shell extension issue:
NOTE: Text input is most probably affected by the explorer restarts so you might need to repeatedly type some letters or to carefully input texts.
NOTE: You might need to download the latest Video Driver on a working computer. Save it in a thumb drive then copy and install it on your computer. If in case there is no native Windows 10 driver, you can also download the latest Windows 7 or Windows 8.1 video driver. Afterward, install it in compatibility mode.
“Script: <PATH of the VBS Script> Line: x Char: x Error: The description of the error. Code: xxxxxxxx Source: (Source of the error)”At the time of writing, it isn’t clear yet what the root cause of the error really is but there are several potential fixes you can check out to fix it. You can try to run the System File Checker or set the default value for the .vbs key, or troubleshoot the problem in a Clean Boot State. You could also try to repair Install Windows 10 or scan your computer for malware. For more detailed instructions refer to the following options.