MyScrapNook Complete Removal Tutorial

In case you don’t know, when you visit a website that uses HTTPS, it also offers an SSL certificate to the browser in order to verify the website’s identity. Although it may contain lots of things inside it, one of them is the URL of the website. So if the certificate does not match the URL to what you entered, you will most likely get the “Server’s certificate does not match, ERR CERT COMMON NAME INVALID” error which indicates that the connection is not private and the site may try to steal your data but worry not, as this post will guide you in resolving this issue. To fix the ERR_CERT_COMMON_NAME_INVALID error, here are some suggestions that might help.

Option 1 – Check the website’s certificate

If you own the website where you’re getting the error, then you might have to check if the website’s certificate is installed properly and configured on the server as it could be the reason why you’re suddenly getting the error.

Option 2 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why you’re getting the ERR_CERT_COMMON_NAME_INVALID error. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 3 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the ERR_CERT_COMMON_NAME_INVALID error in Chrome. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 4 – Run the built-in Malware Scanner and Cleanup Tool in Chrome

In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser. In addition, this built-in tool in Chrome might also help in fixing the ERR_CERT_COMMON_NAME_INVALID error.

Option 5 – Reset Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

The Volsnap.sys is a Windows operating system file that is related to the Volume Shadow Copy Service or VSS. It is known to cause a Blue Screen of Death error. The main cause of the Volsnap.sys Blue Screen errors include conflicts with the RAM, issues with the hard disk, incompatible firmware, corrupted drivers, malware infection, and many more. Despite its many possible causes, its fixes are quite straightforward so won’t have any problem following them. The Blue Screen errors that are related to the Volsnap.sys file are:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL

You might want to try performing System Restore as it could resolve Blue Screen errors like the ones related to the Volsnap.sys before you proceed with the troubleshooting tips given below. To run System Restore, follow these steps:

• Tap 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 you create a System Restore point first.

Option 1 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:

• Click on Start and type “cmd” and right-click on Command Prompt from the search results.
• Then select the “Run as administrator” option to open Command Prompt with admin privileges.
• After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
• Next, type the “net start sdrsvc” command and hit Enter to start the service again.

Note: You can also restart the service using the Windows Services Manager.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
• Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try checking the Memory for the Errors using Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the Volsnap.sys 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 mdsched.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 or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or rollback the 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 go to the section of IDE ATA/ATAPI controllers as well as Storage Controllers 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 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Volsnap.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 5 – Run the 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. To run the SFC command, follow the steps given below.

• Tap Win + R 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.

• Restart your computer.

Option 6 – 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 Volsnap.sys. 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.

Hello and welcome to our Increasing Virtual Memory tutorial. Before trying to raise the quantity of virtual memory in your pc system, it's important to get a comprehension of its goal and use. This leads to the constant use of high-performing tasks in addition to keeping multitasking capability. The downside to this process is the fact that relatively, the HDD accesses information slower than a RAM module. Taking into consideration its use in a computer program and how virtual memory works, there isn't any amount of virtual memory allocation. The quantity of virtual memory to be defined for a unique computer program would be determined by the kinds of programs that are started and the quantity of multitasking done. The Microsoft Windows operating system yet does supply a recommended baseline memory based on the number of RAM installed and storage space of the HDD. Virtual memory allocation really indicates the upsurge in how big the paging file is. This file provides the pc program with all the essential instructions on the best way to act once all the installed RAM has been allotted to the running applications. In both Microsoft Windows XP (all variants) and Windows Vista environments, the method to control the paging file size is basically the same. To increase the quantity of virtual memory:

• Click on the Start menu and choose the "Control Panel" alternative. When the Control Panel window is started, choose the "Operation and Maintenance" class.
• Click on the "System" choice to create the Device Properties Window.
• Click the "Advanced" tab and choose the "Settings" button under Operation. In the Operation alternative window, select the "Change" button under the Virtual Memory class.
• Choose the hard disk where the Windows operating system is now installed. That can be the same place where in fact the paging file will be saved.
• Test on the checkbox for the "Custom Size" to enable you to determine the number of virtual memory you need to use for your device.
• Click the "OK" button thrice to shut all of the windows. Click the Start button and restart your machine to enable the upsurge in the number of virtual memory to be finished.

In establishing the number of virtual memory, you'll have to place a maximum value along with an initial. It is suggested that both values be equivalent in order to achieve the finest performance on your pc system.

Windows Updates are checked for their validity every time they are downloaded from Microsoft servers just like how browsers check websites for a valid certificate. And so if you got an error message saying, “ Some update files aren’t signed correctly, error code 0x800b0109 ” while trying to update your computer, it indicates that the Windows service was unable to verify the validity of the Windows Update. To fix this error, you can try out the options prepared in this post.

Option 1 – Reboot your computer and try again

Save your work and reboot your computer and then try checking for updates again. In some cases, all you need is a restart to fix errors like error code 0x800b0109.

Option 2 – Try to update Windows after an hour or so

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it an hour or so before trying to run Windows Update again.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like Error 0x8007001E. 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 – Delete the contents in the Temporary folder

You can also try deleting the contents in the Temporary folder – all the downloaded, pending, or failed Windows 10 updates. You can do that using the simple and easy steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “%temp%” in the field and press Enter to open the Temporary folder.
• After that, select all the folders and files within the Temp folder and delete all of them.

Option 5 – Clear the contents in the Software distribution and Catroot2 folders

• 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, and then try to run Windows Update once more.

Option 6 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• 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.)
• After that, try to install the Windows Updates or upgrade again.

Error Code 0x80131700 - What is it?

0x80131700 is a Windows 7 error that occurs when there is a problem with the Troubleshooting Wizard. The wizard fails to function and with an error message displaying the following message on the computer screen:

‘An unexpected error has occurred’- The troubleshooting wizard can’t continue

Error code: 0x80131700'

Windows 7 features Troubleshooting Wizard, an automated tool that helps users resolve several PC-related problems such as accessing shared files or internet connectivity to name a few.

Error Causes

The error code 0x80131700 largely occurs because of two reasons:

• The .NET framework is not properly installed on your system
• Mis-configured System Files and Registry Issues

Further Information and Manual Repair

0x80131700 Windows error is rated easy to fix error code. Thus, repairing this error code is not difficult. It is so easy to fix that you don’t need any technical expertise or professional help for that matter. To begin with, there are 2 methods to resolve the 0x80131700 error code. Let’s take a look at the solutions:

Cause: The .NET framework not properly installed on your system

Solution: If the underlying cause for the error code 0x80131700 is the improper installation of .NET framework on your PC, then the best and easy way to resolve this error is to reinstall it. By default, the built-in version of the .NET framework in Windows is 3.5.1 to reinstall this again on your system follow the steps given below:

1. Go to the Start menu and type: features in the search box
2. Now Choose the option ‘Turn Windows Features on or off’ and then press Enter
3. After this, look for Microsoft .NET framework 3.5.1 and uncheck the box
4. Once you uncheck it, restart your computer
5. Repeat the step 1 and 2
6. Now check the box before .NET framework 3.5.1
7. Restart your system
8. Now try using the Troubleshooting Wizard.

Cause: Mis-configured System Files and Registry Issues

Solution: If the error code 0x80131700 triggered due to misconfigured files and registry issues, then the easiest way to fix this error on your system is to download Restoro

Error C00D11B1- What is it?

Error C00D11B1 is a type of Windows Media Player error code. The error C00D11B1 hampers your ability to play videos, MP3 files and songs on Windows Media Player. The error is displayed in the following format:

Error C00D11B1:’Windows Media Player can’t play the file.’

Solution

Error Causes

The cause of error C00D11B1 message pop up on your computer can be narrowed down to one particular reason virtually because this error may be triggered due to several reasons, these include:

• Corrupt DRM license
• Enabled codec of the video in Windows Media Player codecs section
• Registry Corruption

The good news is that this error is not fatal and does not pose serious PC threats like runtime and BSoD error codes. However, it is still advisable to resolve to ensure you are able to watch movies and listen to songs on Windows Media Player without any difficulty.

Further Information and Manual Repair

Here are some of the best and effective do it yourself methods to resolve the error C00D11B1 on your PC right away:

Method 1- Disable the codec of the video option in the Codecs Section

If you are unable to play downloaded movie files on your PC on Windows Media Player, then try this method to resolve the issue. Simply open Windows Media Player, Go to Tools, Options, DVD and then click Advanced Tab. Here find the codecs section, scroll down to the codec of the video you are trying to play and see if it says enabled. If it does, then disable it and then select a decorder for the codec. Now try running the video again on your Windows Media Player. This will hopefully resolve the issue. Nonetheless if the error still persists, try method 2.

Method 2- Delete DRM Licenses & cache and Download it Again

Sometimes the error C00D11B1 can also be trigged by corrupt DRM licenses & cache. To resolve the issue, simply delete all files. First open Windows Explorer (Windows key + E) and then go to C:ProgramDataMicrosoftWindowsDRM. Now delete all files in this folder. Once deleted, Let Windows Media Player download your license again. After downloading the DRM license again, run the Windows Media Player to see if it works.

Method 3- Disable Firewall Temporarily

Firewall can also be responsible for blocking the Windows Media Player streaming. Firewalls often block important ports that are required in order to run some programs. If this is the cause, then simply disable Firewall temporarily to resolve the issue.

Method 4- Repair the Registry

Registry is that part of your computer that saves all the activities performed on the PC and all the files too including both important and unimportant files like cookies, junk files and bad registry entries. If these unimportant and obsolete files are not removed frequently, the registry gets corrupt and damaged. And due to this reason you may experience error code C00D11B1 on your system. To resolve this issue, simply repair the damaged registry by downloading Restoro. This is a powerful PC Fixer integrated with a registry cleaner. The registry cleaner removes all unnecessary files, cleans and repairs the registry in seconds. Click here to download Restoro and fix error C00D11B1 on your PC right now!

The Clear Linux Project creates an operating system and software stack that offers highly optimized performance, security, versatility, and manageability. Clearly optimized for Intel CPUs and based on GNOME it will offer you incredible speeds if you are on Intel CPU. The big news, though, is that Clear Linux sports the shiny new Gnome 40. This is a fresher Gnome than you'll find even on Ubuntu's more experimental 21.04 release. The only big names that let you test drive Gnome 40 are Fedora and Arch Linux.

Packages only when you need them

Installation of packages is used by Swupd, a Clear Linux* package management tool. It is easy to use and pretty straightforward.

• "bundle-list" for showing what's installed
• "bundle-info" for details on installed bundles (such as owned files via the "‑‑files" flag)
• "search" for repository searching
• "bundle-add" for installation
• "bundle-remove" for uninstallation

The only problem here is the packages themselves. Clean Linux* has been imagined as a developer distro focusing mostly on well-development tolls. In intel’s words: “A Linux OS built for Linux developers”, so some things will be left out. Strangely enough some things as FFmpeg which if you want to have and blast some youtube videos while you work will have to complete manually by yourself.

Clear Linux* modular philosophy

Everything in Clear Linux* is based on a modular philosophy approach. There is no /etc/fstab file, the /boot directory is totally empty. Every partition to be mounted is enabled as a systemd "mount unit." Intel reaping the benefits of systemd's modular philosophy, where everything is a unit. If you know your way around systemd, intermediate-level configuration tasks should be straightforward. Any advanced configuration likely demands deep systemd knowledge.

Clear Linux* performance

As stated earlier this is Intel’s distro, optimized for Intel hardware meaning that Intel as the developer has every possible tool at its disposal to make use of hardware to its maximum potential and it shows. Distro almost leaves other ones two times in speed performance. So if you are looking for a distribution that will deliver you speed and it is aimed for developer Clear Linux* is for you.

Conclusion

Clear Linux* is a really interesting distro and seeing how Intel is adding new software packages on its official website it might have a bright future. But as always, be the judge for yourself and see if it can fit your needs. Go get it at: https://clearlinux.org/

What is Error 2032?

Error 2032 is a Windows stream error. The error is generated when running applications like Flash. It shows that the application is unable to request ads from server.

Error Causes

The error 2032 is triggered due to multiple reasons including:

• The URL cannot be located or is blocked
• HTTP Service is not found
• Incorrect proxy settings
• Automatic cookies handling
• Corrupt Flash Player
• Viral infection
• Registry issues

Further Information and Manual Repair

Here are some easy and best do it yourself methods to resolve the error 2032 on your system:

Fix the Proxy Settings

To do this, first, go to the start menu and press RUN, type regedit in the RUN box and press enter. Now from the left-hand panel of the registry path open: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings. Now double click the proxyenable string and replace its value with 0. After that, right-click on proxy server and select delete option. Then exit Regedit and restart your PC to activate changes.

Verify the URL

Sometimes the error 2032 may be generated due to wrong or incorrect URL in the HTTP Service URL property. So, verify your URL and look for typos. Specifying the correct URL can fix the error right away.

Check Cookies Handling

Automatic cookies handling can also trigger this error code. Therefore, to resolve the error, it is advisable to disable automatic cookies handling. This can be done by launching your web browser. Go to tools and then press the privacy tab. Now click on the advance tab from settings and un-check override automatic cookie handling. To confirm changes press OK.

Uninstall and then Reinstall the Flash Player

It is possible your Flash Player is corrupt. Therefore, another way to fix error 2032 is to uninstall the Flash Player and then reinstall it on your system.

Scan for Viruses

Programs usually get corrupted due to two reasons, viruses or registry issues. Therefore, to remove viruses on your PC, download and run an antivirus program.

Clean and Restore Registry

Also, clean the registry.

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.

USB Kill, a USB device is able to fry and damage your computer, mobile phone, router, etc. This device is quite dangerous and can kill electronics the moment it is inserted into an available port. By now people should know that they should not put unknown USB sticks into their devices because of potential virus and malware threats but this raises using unknown sticks to a whole new level.

Kill kits are not really new to the market, they have existed before but lately, technology really progressed and the latest USB sticks are really good, their success rate is around 95% which is pretty high and should not be taken lightly.

The second thing that you really should not play with strange USB sticks is that they dropped in price really hard, although top Kill kits will still go as high as around 300 USD, there are really cheap ones lurking in Ali Express that are just 6 USD!!! that makes them affordable devices for the mass market.

The device is made to take energy and current from the port it is plugged in, multiply it and release its charge back into the device, successfully frying some components immediately. Some more professional Kill sticks can even fry devices even when the device itself is not powered and can be even started remotely.

The point of this article is to make you aware that you should not in any kind of circumstances use and plug-in USB sticks into your devices that you do not know where they come from, especially from the mail!!