An Easy Guide to Fixing Error 115

The screen flickers into black, it comes back and on-screen there is a message Driver stopped responding and has recovered. If you have been through this you are aware that the issue is not serious but it can get pretty annoying fast since you are not aware when will it happen again, and it will happen again. In this guide, we will go through the usual reasons for this error and offer solutions to them. Follow the guide step by step in order to resolve the problem.

1. Clean your PC Dirt and dust are your enemy no1, dirty graphic card can not be properly called and can cause overheating which can result in this particular error, make sure that your PC is clean and tidy in order to eliminate dust and dirt as a cause for malfunction.
2. Turn off multiple applications and try running just one at a time Overburdening GPU can cause this error to appear since the graphic card can not handle all requests it gets from multiple active applications. Try to run just one application at a time for some time period to see if the error will appear again.
3. Update driver Update your GPU driver to the latest version from the manufacturer's website, Display Driver Stopped Responding and Has Recovered Error in Windows 10 can be from outdated drivers not able to handle modern tasks
4. Get newer GPU As hard as this advice is, sometimes the reason is an old graphic card that simply can not keep up with modern games and applications, upgrade it to a more modern GPU and watch errors go away.

It is common to run multiple programs and applications at the same time and it’s important to be able to switch between them using their Taskbar icons or using the usual Alt + Tab shortcut. However, there are times when you might suddenly find that neither of the aforementioned methods worked and you will no longer be able to switch between programs in the Windows Taskbar. To fix this issue, refer to the options given in this post. For instance, when you have multiple instances of Microsoft Edge running and every time you press the Alt + Tab combo nothing happens so you are left with no choice but to minimize everything and then hover your mouse on the icon and switch between the instances of Edge. You will also notice that the right-click on the taskbar won’t respond back and will only keep on showing the loading circle icon. Here are a few tips you can follow to fix the issue with the Windows 10 Taskbar.

Option 1 – Try to restart the Windows Explorer

This is one of the basic things you can try as restarting Windows Explorer helps in refreshing the user interface and makes most of the things work in relation to the user interface.

• To get started, tap the Alt + Ctrl + Del keys to pull up the Windows Task Manager.
• After opening Task Manager, look for “explorer.exe” under the list of programs.
• Once you find the explorer.exe, right-click on it and click Restart.

Option 2 – Try changing the Foreground Lock Time

Aside from restarting Windows Explorer, you could also try changing the Foreground Lock Time to fix the issue with the Taskbar.

• Tap the Win + R keys to open the Run dialog box.
• Then type in regedit in the field and tap Enter to open the Registry Editor.
• Next, go to this registry key – HKEY_CURRENT_USERControl PanelDesktop
• Next, change the ForegroundLockTimeout value from200000 to 0. After that, it will make sure that no other application will take away the focus from your current program or application. It could be that some other application has taken away the focus and even when you try to actually switch, the focus gets back to the old one. Anyhow, since you already changed the value of ForegroundLockTimeout, it will ensure that the focus is not switched.

Note: If you are running some Full-Screen applications there are some devices especially the gaming ones, disable the Windows key to make sure that you won’t be able to switch. If this is the case, you need to make some modifications to the Full-Screen games.

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.

If you are facing a missing sechost.dll error in your Windows 10, welcome, you have come to the right place to solve it and get back your computer in working order. Sechost.dll is a file that allows other programs to function and complete their tasks as well as control and change the behavior of other programs. The file is found in Windows subfolder System32, it is a completely safe file and should not be deleted. Sometimes however various other reasons can corrupt it or delete it. This guide will lead you to common solutions on how to get file back up and running.

1. Update device driver

   Have you installed a new device and all of a sudden you get the error message that Sechost is missing? Update device driver, it is possible that the file has been corrupted or replaced with an older version and therefore reported as missing. Update device driver to lastest version and issue should run away.

2. Re-register file via command prompt

   If Sechost got corrupted re-registering will solve the issue, press ⊞ WINDOWS + X and choose Command prompt (administrator), click on it. type regsvr32 sechost.dll and press ENTER Reboot your PC

3. Reinstall application

   Usually, Sechost gone bad or missing is due to the installation of another application that corrupts the file. Reinstall the application to try to solve errors. In order to properly reinstall the application first use the control panel to remove it completely from the system and then install it again, hopefully, this time correct version of Sechost.dll will be installed in the system.

4. Check your hard drive

   In some cases, a hard drive malfunction can cause several files to be corrupted or gone missing. To eliminate hard drive malfunction run check disk from Windows on C drive to check it and find if there are any errors.

5. Uninstall Windows update

   Same as with some application, even Windows update could corrupt some files due to update not being properly downloaded. Try uninstalling the latest update and revert to the previous Windows state, then update it again.

After a lot of backlash about choosing the default Windows browser, Microsoft has officially backed up and brought back a one-click browser change into Windows 11. For anyone who is not aware, when Windows 11 was released if you wanted to switch to another browser you had to go into the settings app and choose the default browser for different types of file extensions like HTML, HTM, PDF for opening on the web, etc. Of course, this was completely unnecessary and it was not well received by users. So after some time, Microsoft backpedaled to standard one click, choose your default browser solution that existed in the previous version of Windows OS. Altho sometimes Microsoft knows how to irritate its users base, it is good to know that they can also listen and fix things that are required.

One of the most basic and commonly used features in the Windows operating system is the copy and paste feature that helps users accomplish tasks in a faster and easier way. However, if you notice that it’s not working properly for some reason, then this post might be of help as it will provide you with options you can check out to resolve the problem. You can encounter this kind of problem with the copy and paste feature if some system files are corrupted or if there’s some third-party application or process that interferes with this function. Worry not though for there are some options you can check out to fix this. You can try to restart the rdpclip.exe process or the explorer.exe process. You could also try to reinstall the program where you encountered the issue with the Copy and Paste function. In addition, you could try clearing the clipboard history or run the built-in tools like the DISM tool and SFC scan. You could also troubleshoot the problem in a Clean Boot State or use the Refresh Windows tool. For more information, refer to each one of the options below.

Option 1 – Try to restart the rdpclip.exe and the explorer.exe processes

The first thing you can do to resolve the problem is to restart certain processes namely, the rdpclip.exe process and the explorer.exe process via Task Manager.

• First, right-click on your Taskbar and select the Task Manager.
• Next, look for the rdpclip.exe process and right-click on it, and select the End process option.
• After that, click on the File tab > Run new task and then type “rdpclip.exe” and tap Enter.
• This should help fix the problem. If not, you could also try to restart the explorer.exe process – just look for the explorer.exe process in the Task Manager and right-click on it, and then select the Restart option.

Option 2 – Try reinstalling the concerned program

If you only experience this issue on a particular program, you might want to uninstall this program and install it back again, and then see if it fixed the problem or not.

Option 3 – Try to clear the clipboard history

You could also try clearing the clipboard history as it has been known to help in fixing this kind of issue. You can clear the clipboard history using the command line.

• Tap the Win + R keys to launch the Run dialog box and type “cmd” in the field and hit Enter to open Command Prompt.
• Next, execute this command: echo off | clip
• After that, check if the Copy and Paste function is now working properly or not.

Option 4 – Try running the DISM tool

You can run the DISM tool as well to help fix the “Tile Database is corrupt” error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • DISM.exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.
• Once it’s done, check if it was able to fix the corrupted Start Menu or not.

Option 5 – Try to run System File Checker or SFC 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.
• Once done, restart your computer.

Option 6 – Restart your computer in a Clean Boot State

If a third party program like antivirus is the one that’s causing the problem, you can try to put your computer in a Clean Boot State to isolate the issue by following these steps:

• 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.)
• Now try to connect your device or copy the files to your external device again and check if the problem with the Copy and Paste function is fixed.

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

The first thing you can do to fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error 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.
• Now restart your computer to apply the changes made.

Option 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ATTEMPTED_WRITE_TO_READONLY_MEMORY. 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.

One of the selling points of Windows 11 was the ability to run Android apps natively in it without the need for any third-party software. It is not a big surprise that even after its release Microsoft is evolving and expanding Windows 11 and its features.

Microsoft is now rolling out an update for the Windows Subsystem for Android on the Dev Channel of the Windows Insiders program. The new version upgrades the core operating system from Android 11 to Android 12.1 (also known as Android 12L), which means the new system and app features in Android 12 and 12.1 are now available on Windows for the first time. However, not the new features in those updates apply to the modified version that runs on top of Windows. For example, one of the main improvements in 12.1 was a dual-pane notification panel for larger screens, but Android app notifications on Windows just show up in the Windows notification panel.

The upgrade also improves how Android apps integrate into Windows. The Windows taskbar will now show which Android apps are currently using the microphone, location, and other system services — similar to many native Windows applications. Toasts messages (the small popups that some apps use for temporary messages) are now displayed as Windows notifications, and the titlebar on Android apps will use the current activity name for the title.

Full changelog

• Windows Subsystem for Android updated to Android 12.1
• Advanced networking on by default for newer x64 Windows builds
• Updated Windows Subsystem for Android Settings app: redesigned UX and diagnostics data viewer added
• Simpleperf CPU profiler recording now works with Windows Subsystem for Android
• Windows taskbar now shows which Android apps are using microphone and location
• Improvements to Android app notifications appearing as Windows notifications
• Reduced flicker when apps are restored from minimized state
• Apps are not restarted when devices come out of connected standby on recent Windows builds
• New video hardware decoding (VP8 and VP9)
• Fixes for on-screen keyboard in apps
• Fixes for full-screen Android apps and auto-hidden Windows taskbar
• Windows Subsystem for Android updated with Chromium WebView 100
• Added support for Android NetworkLocationProvider in addition to GpsLocationProvider
• Improved general stability, performance, and reliability

The new update is limited to Windows Insiders for now, but once Microsoft fixes all the bugs, it should start rolling out to everyone on Windows 11 that has the Android Subsystem enabled.

When Windows 10 was introduced as an upgrade to Windows 7 and 8, a lot were thrilled because of its new features. One of the most interesting features that this has is the Microsoft Store. Just like in our tablets and smartphones, we can now download our favorite apps from a trusted source. Without the Microsoft store app, you can’t download any applications that you can use on your computer. But what happens if you can’t open your Microsoft Store or you accidentally uninstalled it? The most common error that users encounter when accessing Microsoft Store is the error code 0x80072efd. This error code appears when there is a problem with the internet connection. To resolve this, troubleshoot your modem by doing a simple power cycle. Turn off your modem and wait for a couple of minutes and turn it back on. It should refresh your internet. This works if there is really no problem on the Service provider’s side. Disable your Proxy server, if you are using one to access the internet. To do this, press Windows + R keys on your keyboard. Type “inetcpl.cpl” in the box and go to Connection. Next, click on LAN settings then tick on the box next to Automatically detect settings. Uncheck the box below Proxy Server Among the useful apps that came with the Windows 10 upgrade is PowerShell. It allows you to install and uninstall individual and all apps by using a series of commands. So you don’t have to worry if you can’t find your Microsoft Store or if you accidentally delete it. To access PowerShell, type in the word PowerShell into the search box found beside your Window Icon. Look for PowerShell from the results and right-click on it and hit Run as Administrator.

When you are in the PowerShell window, enter the command below:

Get-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"

Another option is to download a Windows Update Troubleshooter. After you download it, open the troubleshooter tool and follow the steps. If you saved the file instead of directly opening it, go to the folder where the troubleshooter was saved and double click on the wu.diagcab file to rub the troubleshooter. One of the most interesting error codes that you might encounter when accessing the Microsoft store is error code 1. This particular error code is resolved by changing your PC’s region to the United States. To do this, go to Settings and look for Time & Language. Then go to region and language. Under the Country or region, choose the United States from the dropdown menu then restart your computer. The troubleshooting procedures above are the most common solution to resolve the problem on Microsoft Store issues but there are times that these procedures won’t work. If you are not confident to resolve this through the procedures mentioned in this article, there are so many tools online that you can download to help you out. It also helps to contact Microsoft or consult a technician to ensure that you are doing the correct procedure.

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.