Change system font in Windows 10

Hello everyone and welcome to how to fix Windows when it is not starting tutorial. Here we will tackle some common problems and solutions in order to help you to get back both your computer and Windows in working order. Windows not booting and loading is an annoying issue that can even result in complete loss of your data and can also consume a lot of time if no other solution than clean install remains. Also if you are not tech-savvy, this issue can cost you as well since you will have to hire a professional to solve this problem for you. Here at Error Tools, we aim to help so you can overcome your PC issues yourself by providing you daily with tutorials, tips, and tricks and helping you with all of your Windows issues. All of that being said, let's see what are issues that can prevent your computer or Windows from booting up and get around them so everything is back in working order.

1. Use repair tool

   Windows 10 comes with a startup repair tool that has the goal to repair and fix errors preventing Windows from booting up. To use this tool however you will need Windows 10 bootable USB stick. You can create a bootable USB directly on the Microsoft site. Once you have it ready, plug it in and reboot your computer, choose to boot from USB. When you are on the Windows setup screen, click on next and then on Repair your computer. Go to troubleshoot > Advanced options > Startup repair. When Startup repair is clicked, Windows will boot, scan files for issues, and if they are found he will automatically fix them.

2. “Windows Failed to Start” 0xc00000f error

   If you get this error on your boot of Windows, then you have corrupted boot configuration data. In order to fix this error, you will also need a bootable USB with Windows 10 on it. Make one on the Microsoft site if you don't have it and reboot your computer, boot from USB, on the setup screen click on next and then on Repair your computer. Click on Troubleshoot and then on the command prompt. In the command prompt type the following: bootrec /FixMbr bootrec /FixBoot bootrec /ScanOs bootrec /RebuildBcd exit Reboot your PC without a USB

3. Boot into safe mode

   Safe mode for Windows loads only its core without drivers and with minimal services. If you can boot into safe mode then the issue is with some application or driver causing the problem. Try the selective boot option to eliminate what is causing the error.

4. Make sure your hardware is connected

   Some RAM or hard drive out of socket can cause Windows not to be able to boot, check all connections just in case.

If everything else fails, perform a clean Windows installation. The reason for Windows not booting up can be caused by various viruses and malware also if that case it would be best to format and perform a clean install.

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• 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, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

What is Runtime Error 339?

Runtime Error 339 is a common error code format that appears when a computer overloads with too much data. However, in some cases, it may occur due to the missing registry keys, DLL files, or during installation. It may lead some programs to shut down all of a sudden and may also corrupt files on the system.

Solution

Download Available to Completely Repair Runtime Error 339

Error Causes

This error code is alarming as it is a critical sign of an unstable system followed by improper maintenance of the computer. The potential risks associated with the Runtime Error 339 include:

• System startup issues
• Slow PC performance
• System crash and failure
• System file corruption

Therefore, to avoid these risks and system failure, it is advisable to fix the runtime error 339 immediately.

Further Information and Manual Repair

If you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:

Scan For Viruses

Improper maintenance of the computer indicates that your system might be exposed to viruses and malware. Viruses can modify the Windows registry and lead to Runtime Error 339. Therefore, first, it is important to scan for viruses on your PC.

Identify Software that Causes Errors

Scanning will help you identify software that produces this error on your PC. Once you identify them, either uninstall them or update the program. To uninstall the program, go to the Control Panel and then click on the Add/Remove program if you have Windows XP, if not then click on the Programs and Features item. Now delete the program from your system.

Obtain the Latest Version of the Installer and Re-install the Deleted Program

Once you get your hands on the latest version of the installer, run it on your system by following the on-screen instructions. Install the program. There is also another way to fix Runtime Error 339 and that is by downloading the Runtime Error tool.

Use a Professional Runtime Error Fixer Tool

To fix the error you can also use a professional Runtime Error fixer tool to scan for viruses on your PC. It is available for free download here. Download the tool and install it on your computer. Simply scan your PC after installation. Click the repair button once the scan is complete. This tool fixes problems in just a few minutes.

If you suddenly encountered a Windows Error Code 0x80070017 during an Update, Installation or System Restore then it’s probably due to some missing or corrupted system files. This kind of error code can occur during an update, installation, or system restore and the only way out of it is to download the file once again and re-run the installation from the top. Before you start to troubleshoot the problem, you need to create a System Restore Point first. After you create a System Restore point, you can follow the troubleshooting options laid out below to fix the Windows Error Code 0x80070017. You just have to follow the troubleshooting option that applies to your situation and whether you got the error during an update, installation, or during System Restore. Whether you got the error 0x80070017 while updating Windows 10 or installing it or during a system restore, the first thing you must do is run the System File Checker. As pointed out early on, the Windows Error Code 0x80070017 might be caused by corrupted or missing system files so the first thing you can try is to run the System File Checker scan.

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

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.

If you have encountered Windows Error Code 0x80070017 during an Update, then here are some options you need to try:

Option 1 – Delete the files/contents in the SoftwareDistribution Folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error Code 0x80070017. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go. On the other hand, if you got the error code 0x80070017 during a Windows 10 installation, then it’s because of bad media or corruption in ISO. Here are some troubleshooting steps for this kind of situation:

Option a – Try to create Windows 10 ISO media again

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. Most users reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seem to create issues such as the error 0x80070017. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with the option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option b – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x80070017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically. If you got the error during System Restore then this means that the files that are being copied from the disk are not making it to the hard drive. To resolve it, here’s what you can do:

Option 1 – Run System Restore in Safe Mode

You might want to run System Restore in Safe Mode and see if it works. Just reboot your PC into Safe Mode and then run System Restore.

Option 2 – Reset Repository

• Boot your PC into Safe Mode.
• Then open Command Prompt as admin.
• Next, type the “net stop winmgmt” command and hit Enter to stop the Windows Management Instrumentation Service.
• After that, go to C:/Windows/System32/wbem. From there, rename the repository folder to “repository-old”.
• Restart your computer.
• After your computer has restarted, open Command Prompt as admin again and then type the “net stop winmgmt” command and hit Enter.
• Next, type the “winmgmt /resetRepository” and hit Enter to reset Repository.
• Restart PC and check if System Restore now works.

Option 3 – Try resetting Windows 10

To fix the error 0x80070017, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, it only resets all the system settings and files. Simply go to Settings > Recovery. From there click the Get started button under the Reset This PC section.

System Interrupts are operating system processes that function as an alert system for the CPU. So whenever a scenario needs the attention of the CPU, it alerts the CPU about it. In turn, the CPU suspends what it is doing, saves it, and then takes care of that important job and once that job is completed, it resumes back to what it was doing. This indicates that although System Interrupts appears as a process, it’s actually not. As a matter of fact, it is like a manager that reports to the CPU about all interrupts that happen on a hardware level, e.g. hardware interrupts. And if there are lots of interrupts, this means that there might be various errors occurring on a hardware level. As a result, it may take a lot of system resources. And if you consider disabling System Interrupts, stop right there as your computer will almost become useless without it. So if you see System Interrupts consuming high CPU usage in your Windows 10 computer, you can fix it without having to disable it and cause more problems. If System Interrupts takes up more than 5 to 10% of CPU, then you definitely have a problem. This could be happening due to some hardware or driver issue. The first thing you can do is to try rebooting your computer once and see if the issue comes back or not. High CPU usage of System Interrupts is a huge backlog for the CPU and it stays in the loop. If a simple system restart didn’t fix this issue, here are some suggestions you can try.

Option 1 – Try to update the hardware drivers

As stated, the problem might have something to do with hardware drivers so you can try to update these drivers and see if it works.

• Reboot your computer into Safe Mode with networking support.
• Tap the Win + R keys on your keyboard to open the Run dialog box.
• After that, type “devmgmt.msc” in the field and hit Enter or click OK to open the Device Manager.
• After opening the Device Manager, update all the outdated Hardware drivers on your computer.
• Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
• Now restart your PC and check if the BSOD error is fixed or not.

Note: On the other hand, if a recent update has caused the System Interrupts high CPU usage, then you might want to roll back your hardware drivers to their previous versions. You can check with the Windows Update History to check out any recent updates as well as the previous ones.

Option 2 – Try to disconnect and reconnect all hardware and cables

A lot of users reported that they were able to fix the problem by disconnecting and reconnecting cables and hardware like scanners, printers, cameras can help in fixing the problem. In addition, you can also boot your computer in a Clean Boot State so that you can find the problematic hardware by hit and trial method. Refer to the steps below to do so:

• 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.)

Option 3 – Try to enable or disable Hardware

If you do not want to remove hardware, you can just disable them using the Device Manager. Note that this can also be applied to the internal hardware.

• Tap the Win + X + M keys to open the Device Manager.
• Next, navigate to the device you want to disable.
• Then right-click on it and choose to disable the device.

Note: Make sure that you disable one device at a time and then give it a couple of minutes and check if there are any changes in the CPU usage to pinpoint the hardware. And if there is no change, you need to enable the device you’ve just disabled and then proceed to disable the next hardware device. If there are changes, then it’s probably the culprit. Just keep in mind that you must no disable any device that is needed to keep your system up and running.

Option 4 – Try to update the BIOS/UEFI

Updating the BIOS/UEFI can help you fix the high CPU usage of System Interrupts but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Restart your computer to apply the changes made.

Option 5 – Run the Hardware and Devices Troubleshooter or the Performance Troubleshooter

Hardware and Devices Troubleshooter:

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Performance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
• Then click on Next to get started. Wait until the process is completed.

Error 550 - What is it?

Error 550 is an SMTP (Simple Mail Transfer Protocol) outgoing server error code. It usually occurs when you try to send emails through your Outlook account and the email message encounters a relay error. The email returns back without being delivered with a 550 error message. The error message is prompted as either of the following:

"550 Requested action not taken: mailbox unavailable" "550 5 2 1 mail from refused spam site"

In other words, the error code 550 means that your SMTP server was not able to deliver the sent email to the user.

Solution

Error Causes

There are multiple reasons for this error message including:

• The email address was typed incorrectly
• Incorrect SMTP Server settings
• ISP placing restrictions for outgoing mails on the email server
• System infected by virus or malware

Further Information and Manual Repair Regardless of what the reason may be for the error 550 code occurrence, it is advisable to repair and fix the issue quickly to avoid inconvenience. You may not be able to send emails from your Outlook account if the error continues. This can cause great hassle in corresponding with others timely and may create a big communication gap. Here are some quick and efficient ways to resolve this issue on your system:

Solution 1:

There is no need to panic when you encounter error 550. Sometimes the error message may occur because you inserted the wrong/ incorrect email address of the recipient. In such a case, cross-check the recipient’s email address to verify if it is correct. If not, insert the correct address and try sending the email again.

Solution 2:

If the error still persists, try other methods to resolve it. Sometimes error 550 can also occur due to incorrect SMTP settings. Fix it to resolve the error. This can be done by opening your Outlook settings Tools and Accounts option. Now go to view/change the email account for the email account you are having problems with. After that check, the SMTP server is set to mail.yourdomain.com. Then click more settings and then click the outgoing server tab. See if the ‘My server requires authentication for the outgoing server’ is checked. If not, then check on it. Then simply save to confirm changes. Now try emailing again. Hopefully, this will resolve the issue.

Solution 3:

Another reason for the error occurrence can be ISP blockage. When the junk email volumes increase, network administrators (the people who are responsible for managing ISP servers) place restrictions on SMTP email servers to prevent spam on their network. If this is the reason, contact your ISP administrator to resolve the issue.

Solution 4:

Malware and viral infection can also be the cause for error 550. To remove all kinds of viruses including Trojans and spyware and fix the issue right away without compromising on the speed of your PC it is advisable to download Restoro. This is a highly functional and advanced PC Fixer embedded with multiple utilities like a powerful antivirus and a system optimizer. It scans your entire PC in seconds, detects and removes all kinds of viruses. Simultaneously, the system optimizer feature ensures the speed of your PC does not slow down during the scanning and virus removal process. This feature boosts your PC speed significantly. It is user-friendly and has easy navigations making it quite simple for even those users who are not technically sound to work around it and operate it with ease. It is compatible with all Windows versions. Click here to download Restoro and resolve the error 550 messages today!

If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004 To resolve the Windows Update error 0x80092004, here are some fixes you can try.

Option 1 – Try removing recent updates and packages

When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
• Now run the Remove Package program to remove the concerned update and package.

dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart

• Now restart your computer and log back in.
• After that, run the following command:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

• Then scan for updates.

Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to manually install the Windows Updates

Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Error 0xA00F4244 or 0x200F4244 is when Windows can not detect the WEB camera in your system and it is usually accompanied by the message: We can’t find or start your camera. There could be several reasons for this error and in this guide, we will cover all of them in order to help you to get back on track and start using your WEB camera which is perhaps now more required than ever in this world we live in.

1. Check privacy settings

   With the latest Microsoft Windows updates come the latest issues and it is not strange that privacy settings can become reset or changed when an update is applied. This is a quick fix to this issue and can be the sole reason why you get this error, go to Windows settings, then to privacy and check to see if the WEB camera is turned OFF, if this is the case turn it back ON and make sure that option Allow apps to access your camera is also set to ON.

2. Check if the camera is enabled

   Sometimes it is by mistake, sometimes by an update but the web camera could be disabled in the device manager of Windows. Right-click on the Windows Start button and click on device manager to open it up, find and expand the cameras category. Right-click on your camera, if it is disabled, you will have the option to enable the camera, if it is enabled and Windows is detecting that it is working fine you will have the option to disable it.

3. Check antivirus settings

   Antivirus and firewall applications are in today's world and life-essential piece of software but they can sometimes create more harm than good, from stopping windows updates to killing important services of applications and preventing internet access being just some examples of their paranoid behavior. Try disabling or turning your protection software OFF and see if your WEB camera will miraculously come back to life. If this is the case, somewhere in the settings of software there is an option that controls this aspect, try to locate it and set it in that way so you are able to use your camera.

4. Reinstall camera driver

   If the previous three solutions failed to produce a satisfactory solution then reinstalling the camera driver might fix the problem. Go to your manufacturer's camera website and download the latest driver for your camera. Go to the device manager and uninstall the driver for the camera, then apply the latest driver and reboot the system.

5. Check connections and cable

   Sometimes an issue is not due to software nature, sometimes it is hardware. Try checking connections and plug the camera in another USB port, twist and turn the cable a little to see is issue cable-related.

6. Check to see if the application supports your camera

   If Windows has detected the camera and is not reporting any issues with it check your application to see if it can detect your camera and that it supports it fully. Sometimes newer applications tend to support only newer camera models. Try to use the camera in other software as well to see if the problem is with the application you are using.

7. Try camera on another computer

   If everything else fails, try the camera on another computer to see if it will work there. If the camera is not working there as well it is probably malfunctioned and broken for good. If it does work there, try to find out what is different in that computer in comparison to yours, maybe it is some service running in the background, certain application configuration, Windows version itself, USB port version, or something else.

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.

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.