Should you use the Faraday bag

One of the most common Blue Screen of Death errors you can encounter on your Windows 10 computer is the Tcpip.sys Blue Screen error. The Tcpip.sys file is a driver file that is associated with the Transmission Control Protocol over Internet Protocol. When you see this kind of BSOD error, you may see any of the following error descriptions:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• PAGE_FAULT_IN_NONPAGED_AREA

Whichever error description you got, you need to do use the following instructions below as a reference to obliterate the Tcpip.sys Blue Screen error.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Tcpip.sys Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Try resetting TCP/IP

In case you didn’t notice, the Tcpip.sys file is associated with the TCP/IP protocols in your computer system which is why resetting TCP/IP can help in resolving the Tcpip.sys Blue Screen of Death error especially when the TCP/IP has been modified.

• First, you need to type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option to open Command Prompt.
• After that, type the following command in the elevated cmd window and hit Enter:

netsh int ip reset

• Now reboot your computer after the command has been executed and check if it helped to fix the Blue Screen error.

Option 3 – Try to rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
• Then select each one of them and double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
• Now restart your computer to successfully apply the changes made.

Option 4 – Try to update the Network drivers

You might also want to try updating all your network drivers in order to fix the Tcpip.sys Blue Screen error. To do so, here’s what you have to do:

• Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 5 – Try to disable both the Antivirus program and Firewall temporarily

There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects which is why you have to disable these programs temporarily as it might be the reason why you’ve encountered the error when trying to browse the internet.

Error Code 0x80073afc - What is it?

Error code 0x80073afc deals with an antivirus program first built into Windows 8/8.1 This error occurs when Windows Defender, the built-in anti-virus software in Windows 8/8.1 and higher, does not start automatically and users attempt to manually start the program. During the initialization period of the program start-up, something goes wrong and users get a 0x80073afc Error message. The error message states there was a problem with the initialization of the program. Windows Defender provides protection of your computer and it is advised by the Microsoft Corporation that you ensure it starts up automatically on every start-up.

Solution

Further Information and Manual Repair

Users have found several manual repairs that have fixed the problem without needing to contact technicians for extra help. While the methods below should solve your problem easily, if this is the first time you have encountered the issue you may want to do a simple restart. This has fixed the problem for some users and is the easiest first troubleshooting move. If it doesn’t work move on to the methods listed below, which are easily completed without extra help.

Before trying any of these methods, please make sure that you are logged into a profile that is listed as the administrator of the computer of his administrative powers enabled. If this is not the case you will not be able to complete the following methods. Please log out and log back in on the administrator profile.

Method 1:

First, check to see if you have a third-party anti-virus program installed on your computer. Some users believe that the built-in Windows Defender program is not powerful enough to handle the safety of their computer so they usually download a third-party program. However, that program may have caused a conflict with Windows Defender and may not allow it to open. If you do have a third-party program installed, try uninstalling it then manually starting Windows Defender.

Method 2:

If method one does not work, you may be infected by malware or a virus that has tampered with the settings on your computer and will not allow Windows Defender to start automatically or manually.

First, open Run by holding the “Win” key and pressing the “R” key. Then type “Regedit”. The program will ask for permission to follow through with this action. Click on “Yes” and the Open Registry Editor will open.

Find the HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionImage File Execution Option and check to see if there are any files similar to MSASCui.exe or MpCmdRun.exe. If there are any file entries that resemble that, you will want to right-click on them before selecting the “Delete” option. If you do not see any entries that match, this is not the issue with your Windows Defender and you will want to try another method.

The Registry on your computer is very important. It helps tell your computer what programs are safe to run, what programs should be run, and what programs should not be run. If it is tampered with by a virus or Malware, multiple system operations can be affected.

However, if you did find similar file names, and you deleted them, try to start Windows Defender manually. If it does not work again, move on to the next method. 

Method 3:

If the first two methods do not work for your issue, and you are still receiving error code 0x80073afc when attempting to start Windows Defender, this step should solve the problem if you have Restore Point installed on your computer, which you most likely do.

For this method, we will be restoring your computer to a previous Restore Point. First, just like in method two, hold the “Win” key and press the “R” key. This will open run. Next type “Rstrui.exe” and click “ok”. After some time, you will see System Restore Windows. Click “Next” and select the restore point that you would like to go back to. After your computer has restored to the point you selected, check to ensure that Windows Defender has started correctly.

If the above methods aren't able to rectify the issue, you might have to download and install a powerful automated tool to get the job done.

Creating a System Restore point is definitely a must especially when you are about to make some changes to your computer. This will help make sure that the system settings and files can go back to an earlier point, should something go wrong, without affecting any personal files. However, there are cases when creating a System Restore Point does not go smoothly and you encounter an error that says, “The shadow copy provider had an unexpected error while trying to process the specified operation ( ox8004230F )”. Aside from creating System Restore Point, you can also encounter this error when you create a system image or backup. According to reports, this error pops up when the required services are not running or not properly responding. And to fix it, there are several recommendations that will be provided in this post to fix the Error 0x8004230F when creating System Restore point in Windows 10. You can try to check the Volume Shadow Copy Services status or run the VSSADMIN tool. You could also check the status of the Microsoft Software Shadow Copy Provider Service or create System Restore Point in a Clean Boot State. For more details, refer to the provided options below.

Option 1 – Try checking the status of the Volume Shadow Copy Service

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Volume Shadow Copy service and double-click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start) and then click on the Start button underneath it.
• Once done, click on Apply and then OK to save the changes made.
• Now try creating a System Restore Point again and see if the error is already fixed or not.

Option 2 – Try to run the VSSADMIN tool

In case you don’t know, the shadow copy provider is sensitive and some other backup, disk cloning, etc. can make it malfunction. To fix this, you can run the VSSADMIN tool by following these steps:

• Tap the Win + R keys to open the Run dialog box and type “cmd” and hit Enter to open Command Prompt.
• Next, execute this command to check if you have other third party VSS admin providers: vssadmin list providers
• After that, if it finds any, you need to disable them but if it does not find anything, then proceed.

Option 3 – Try to check the Microsoft Software Shadow Copy Provider Service status

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Microsoft Software Shadow Copy Provider Service and double click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start).
• Once done, click Apply and OK to save the changes and then try creating System Restore Point again.

Option 4 – Troubleshot the problem in a Clean Boot State

It is possible that some third-party program installed in your computer might be the one that’s causing the ox8004230F when you try to create a System Restore point. Thus, you can try to boot your computer in a Clean Boot State and then try to perform the task again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted try to create a System Restore Point again and if it now works, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

The new thing from Mozilla is not a browser, it is a VPN!

Besides Firefox, Mozilla offers now Firefox Relay, an app helping you to mask your email and phone number, and a new Mozilla VPN.

Mozilla has recently announced a new subscription model that will let you use all products together for $6.99 per month. Although this is a little more expensive than the competition that goes around for $5 per month note that with this subscription you are having access to all services, not just VPN.

VPN will not only hide your IP address but will also make sure websites cannot access your real location and it encrypts all of your network activity. Relay will give you protection against spam, serving as a shield for your email and limiting spammers from access to your real email address and phone number. With Mozilla subscription will let you use both services.

If you encountered an error message that says, “Unhandled exception has occurred in your application”, when you start your Windows 10 computer, read on as this post will guide you on how you can fix it. This kind of error usually appears in a Microsoft .NET Framework window and it mostly pops up as soon as you turn on your computer. Here’s the complete context of the error message:

“Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.”

When this error occurs, your computer may freeze or display other suspicious behavior at times. Either way, there are several options you can check out in this post to resolve this issue, so read on. This kind of error could be caused by several factors. It could be due to your antivirus program or other third-party programs installed on your computer. It is also possible that the installation of the Microsoft .NET framework id corrupted or some of its installation files are corrupted. Thus, to fix the error, there are a few suggestions you need to follow such as:

Option 1 – Try to temporarily disable your anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive in your computer. There are times when you encounter problems like the “Unhandled exception has occurred in your application” error due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program in the meantime and check if it fixes the error or not.

Option 2 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted, check if the error is now gone. If it is, then the culprit is some third-party program. Thus, you have to enable the third-party programs one by one to find out which one of them is causing the the “Unhandled exception has occurred in your application” error.

Option 3 – Try to run a System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the cause why you’re getting the “Unhandled exception has occurred in your application” error. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer and see if the problem is fixed or not.

Option 4 – Install and update Dependencies

There are times when programs and applications need to have drivers and supporting software installed for them to properly work. Although the installation usually takes care of it, it’s time for you to do some manual check especially if you are getting this issue of abnormal program termination.

• Install some qualified drivers – A number of high-end games and applications need to have correct and valid drivers for them to work. They just don’t work with general drivers though. Microsoft has this Windows Hardware Quality Labs testing also known as WHQL testing which makes sure that drivers meet the correct experience and pass through the proper testing before certification. Thus, when installing drivers, you need to ensure that they are qualified drivers for your Windows 10 PC.
• Download and install or Update DirectX – As you know, Microsoft DirectX is a suite of technologies developed by Microsoft to provide hardware acceleration for heavy multimedia applications like HD videos and 3D games. Since you are using Windows 10, you have the DirectX 12 version while the earlier Windows versions use the DirectX 11 version.
• Install the Microsoft DirectX End-user runtime – The Microsoft DirectX end-user runtime gives updates to version 9.0c as well as previous versions of DirectX. To install it, click on this link and download it.
• Update or install the .NET framework – The .NET framework is used by games and applications during development which means that without the runtime files that are installed in your computer, it definitely won’t work. Thus, you need to install or update this framework. You can also use the .NET setup verification tool to verify it.

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given options below.

Option 2 – Ensure that all the supporting processes and services are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 3 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox error.

Having any kind of hardware malfunction is not a pleasant place to be. Even a minor malfunction like a broken key on a keyword can introduce certain bad feelings, frustration, and difficulty in working. So, what are your options when the dreaded key on the keyboard breaks? From my point of view, there are three options that could be accomplished in order to continue working.

1. Replace broken keyboard with the new one

   Yes, the best and most expensive solution, just bite the bullet and buy a new working one.

2. Replace key with another key

   So you broke some key, if you can replace it with another key which you do not use, this option will work only tho if the broken key is not Space bar, enter or similar with specific shape and size.

3. Remap key

   use Windows power tools to remap key function to another working key

There you go, three options to continue working with a broken key on the keyboard.

Realtek sound device not playing sound is a common Windows issue.  It happens occasionally and luckily it can be solved with a little effort and in a short time period. Today in this article we will explore the most common reasons and solutions for driver malfunction for Realtek inside Windows 10. If you have this particular problem, go from step 1 to the last step since all steps are meant to go from simplest to the most complex. All of that being said let us fix your Realtek driver issue.

1. Check Speakers or/and Headphones first

   The first thing would in any troubleshooting be to check are your speakers turned on or are your headphones connected and the volume or switch on them is set properly. Nothing more embarrassing than spending an hour or so troubleshooting only to find out that issue was in a malfunction of speakers or them not being turned on.

2. Check the Volume control in Windows

   Same as the previous step where you have checked hardware, now it is time to check to see if the volume control is set properly and not by any chance muted or volume is brought all the way down.

3. Check if the Device Manager is reporting an error and update the driver

   If both hardware is functioning properly and volume control in Windows is set correctly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

4. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one.

5. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

6. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

The Winload.efi file is an Extensible Firmware Interface or EFI file. EFI files are executable files for the firmware of the computers that are mainly based on UEFI and execute the tasks of loading the files to the bootloader of the computer. They are used for a specific set of tasks such as turning on the computer, installing Windows, restarting the computer or resetting it, and so on. This is why the Winload.efi file is a significant file so if it gets corrupted, lost, or damaged, it would be impossible for the Windows operating system to proceed. Here are some errors you can encounter that are related to the Winload.efi file:

• efi is missing
• efi cannot be found
• efi is missing or contains errors
• This program can’t start because winload.efi is missing from your computer
• This application requires the file winload.efi, which was not found on this system.
• There was a problem starting [path]winload.efi. The specified module could not be found.

In addition, the 0xc0000225 , 0xc00000e and 0xc0000001error codes are also associated with the Winload.efi file. Before you start troubleshooting the problem, you can try to perform System Restore first. This will help undo any changes you’ve made in your computer that might have triggered the Blue Screen error. To perform System Restore, here’s what you have to do:

• First, press the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that your create a System Restore point first.

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

• Once you get to the Welcome Screen part, click on Next.
• Afterwards, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• Once Command Prompt has been pulled up, the following commands to rebuild BCD files and repair MBR. Don’t forget to hit Enter right after you type each command.
  • bootrec /repairbcd
  • bootrec /osscan
  • bootrec /repairmbr
• Once the command line is successful in finding out a Windows installation, hit Y to let it boot from the list which will successfully rebuild BCD.
• Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve errors related to the Winload.efi file. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them

• Reboot your computer.

Option 4 – Disable the Early Launch Anti-Malware Protection

• You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
• After that, it will restart your computer to Startup Settings.
• Now ensure that the 8^th option is labeled as “Disable early launch anti-malware protection.
• Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.

Blinking or Flashing Desktop After login - What does it mean?

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.

Solution

Error Causes

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.

Further Information and Manual Repair

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:

Method One: Forcefully Terminate Process

1. Press on Ctrl+Alt+Del then select Task manager
2. Start a Command Prompt as an administrator by choosing the File menu then Run New Task.
3. Type exe. Make sure to tick the checkbox “Create this task with administrative privileges.”

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.

4. In the Command Prompt, type taskkill /f /im explorer.exe. This will stop the blinking or flashing.
5. Type cd “Program Files” afterward, type dir /s bushell.dll to locate where the dll is. (For example, purposes, use c:\program files\Norton Security Suite\Engine6422.5.2.15 as the location)
6. If the dll file is not found, you can try repeating step 5 but this time, use “Program Files (x86)” However, you can proceed with the next step if you already located where the bushell.dll is.
7. Type cd ”c:\program files\Norton Security Suite\Engine 6422.5.2.15” to change the name of the directory you found the dll in.
8. Type ren bushell.dll bushell-crash.dll
9. Restart now the system by typing shutdown /r /f /t o in the command line.

Method Two: Uninstall Programs

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode by pressing 4 on your keyboard.
8. Log in then press Windows key + X.
9. Select the Device Manager then expand Display Adapter.
10. On your Display Adapter, right-click then select
11. Exit Device Manager
12. If in case you also have an older Antivirus utility, you should uninstall it as well.
13. Restart

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.

Method Three: Use Microsoft System Configuration Utility

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode but this time, choose 5 to start in Safe Mode with networking.
8. Check if your problem is present or not in Safe Mode. If not, then you are on the right track.
9. Press on the Windows key + R then type msconfig to start up your exe file.
10. Click on the Services tab then choose Disable All. Afterward, click on
11. Once you’re prompted to reboot your computer, go ahead and reboot in Normal Mode. Check if the issue is still present.
12. If the blinking or flashing desktop after login is gone, then you can just do a process of elimination.
13. Start-up on your exe again then begin bringing up services a few at a time.
14. You can turn on all other services except for the following which causes the blinking or flashing desktop after login problem: Problem Reports and Solutions Control Panel Support •Windows Error Reporting Service.