Logo

Fix 0xC03A0005 error in Windows 10

When performing a Windows Backup to the NAS device (backup to a network share) that is running Samba, fails with an error message The backup failed, The version does not support this version of the file format (0xC03A0005). The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files:

  1. Fixed,
  2. Expandable
  3. Differencing

If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is one that keeps expanding depending on the backup size. The problem occurs only in the case of  File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.

The solution is to use Strict Allocate: option in the smb.conf file

Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

The task image is corrupt/tampered 0x80041321
If you suddenly encountered an error that says, “The Task image is corrupt or has been tampered with”, along with an error code of 0x80041321, read on as this post will guide you on what you can do to resolve this problem in your Windows 10 computer. According to security experts, this kind of error has something to do with a corrupt scheduled backup task wherein each time the task service plans to execute a task, it validates a few things. And if it finds any issue with the integrity or corruption in the registry, it will mark those tasks as corrupt and throws the error 0x80041321. There are several options you can check out to fix the problem. You can try using the Registry Editor to edit and fix the corrupted tasks or you could also delete the schedule keys or the WindowsBackup file, as well as try deleting the task from the Task Scheduler or refresh the User_Feed_Synchronization. But before you of these potential fixes, make sure that you check every option and verify if it’s not associated or trying to run a file which it should not. In addition, make sure that you create a System Restore point as well so that you can undo any changes you will be making if anything goes wrong. Once you have these things covered, refer to each one of the options provided below.

Option 1 – Try to use the Registry Editor to edit and fix corrupted tasks

The first thing you can do to fix the problem is to edit those tasks via Registry Editor, as well as fix the corrupted ones in System32. Before you proceed, keep in mind that since you are dealing with the Backup triggered by the Task Scheduler, you can find the entries for the tasks in different locations. You can find the Task Scheduler at Task Scheduler Library > Microsoft > Windows > Windows Backup, whereas, you can find it in this path in the Registry Editor, HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Schedule WindowsBackup AutomaticBackup. On the other hand, you can find the Windows System folder at C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup. You need to ensure that the name of the task name is the same as everywhere and take note of the name. Once you have these covered, follow the steps below.
  • Tap the Win + R keys to open Run and type “Regedit” in the field and hit Enter to open the Registry Editor.
  • Next, navigate to this key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTreeMicrosoftWindowsWindowsBackup
  • From there, take note of the GUID value in the ID entry of the task under the AutomaticBackup and Windows Backup Monitor folder.
  • After that, you have to remove the task registry entries related to the ID from these locations
    • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
    • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
    • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
  • Once done, you have to create a temporary copy of the corrupted task file by going to this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
  • From there, look for the AutomaticBackup and Windows Backup Monitor tasks and copy them to a location where you can keep them safe.
  • Next, you have to fix the corrupted task by deleting it from this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
  • After that, you have to recreate the task by going to Task Scheduler > Microsoft > Windows> Windows Backup.
  • Now click on the Action menu and on Import task and navigate to the backup files and import them.
  • Once you’ve created the tasks, run them manually and see if the error is now fixed.

Option 2 – Try to delete the Schedule keys in the Registry

  • Launch the Registry Editor and go to this key: HKLMSOFTWAREMicrosoftWindows NTCurrent VersionSchedule
  • From there, delete all of its sub-keys.
  • Once done, exit the Registry Editor and check if the Backup Tasks are now working.

Option 3 – Try to remove the WindowsBackup file

The next thing you can do to fix the problem is to remove the WindowsBackup file if the first two options didn’t work. It is possible that the problem has something to do with corrupted Task files. The task files are XML files that include parameters, programs to use, and many more. If any of these files end up getting corrupted, the task scheduler will have trouble running it and will throw the “The Task image is corrupt or has been tampered with” error.
  • To delete it, go to C:WindowsSystem32TasksMicrosoftWindowsWindowsBackup.
  • From this location, get rid of all the files. You could also these files via Command Prompt using the DEL command.
  • Once done, go to the Backup and Restore in the Control Panel and set up the Windows Backup again.

Option 4 – Try to delete the task from the Task Scheduler

If you don’t want to delete the files from Windows Explorer, you can delete them instead via Task Scheduler.
  • Open the Task Scheduler and go to Task Schedule LibraryMicrosoftWindowsWindowsBackup.
  • From there, delete both of the tasks and set up Windows Backup again.
  • Once done, go to the Task Manager and run the AutomaticBackup task again and see if it works.

Option 5 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.
  • First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
  • Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
  • You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
  • After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
  • Click on the “RUN” option and select the “Restart the Service” option.
  • And click on the “After Second Failure” option and then select the “Restart-Service” option again.
  • Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
  • Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 6 – Try refreshing the User_Feed_Synchronization

According to security experts, enabling and disabling the User Feed sync also known as the User_Feed_Synchronization task can help resolve the problem.
  • Tap the Win + X keys and select the PowerShell (admin) option from the menu.
  • Next, type the “msfeedssync disable” command and tap Enter.
  • Repeat the same process but this time run the “msfeedssync enable” command.
Read More
How to Repair Missing MSVCR100.dll Error

What is MSVCR100.dll Error?

Msvcr100.dll is a dynamic link library file. This file is loaded into the memory at runtime for successful program execution. This process is also referred to as runtime dynamic linking. The Msvcr100.dll belongs to the Microsoft Visual C++ Runtime Library. It is a core Windows component used by numerous Windows-based applications to load and run smoothly on Windows PC. Msvcr100.dll error occurs when the process of runtime dynamic linking fails. Due to this error, you are unable to access the desired application. The error code is displayed in either of the following formats:
  • “Msvcr100.dll Not Found"
  • "This application failed to start because msvcr100.dll was not found. Re-installing the application may fix this problem."
  • "Cannot find [PATH]msvcr100.dll"
  • "msvcr100.dll  is missing from your computer"
  • "XXX.exe - System Error - MSVCR100.dll is missing from your computer."

Solution

Restoro box imageError Causes

Narrowing down the cause of the Msvcr100.dll error is not possible as this error can occur on your PC due to multiple reasons. However, here are some of the most common causes of Msvcr100.dll error code on Windows PC:
  • Msvcr100.dll file corrupt and damaged
  • Missing Msvcr100.dll file
  • Corrupt runtime code library
  • Registry issues
  • Malware attack and viral infection

Further Information and Manual Repair

Here are some of the best ways to resolve this error on your system:

Reinstall the application causing the error

As dll are shared files used by multiple programs to load and run, there is the possibility of it getting deleted when uninstalling a certain program. If so, then the best way to fix it is to reinstall the application that is causing the error to pop up on your screen. This way you’ll be able to set up the program again and install the Msvcr100.dll file back on your system.

Download Microsoft Visual C++ 2010 Redistributable Package

Another way to resolve this error is to download Microsoft Visual C++ 2010 Redistributable Package. To do this, first, see if you are running a 32 bit or 64-bit copy of Windows. XP users go to the start menu and click run then type winver and press enter. In Vista and Windows 7, go to the start menu and type computer and click properties. The information you require is under Windows Edition. Once you find out whether you are using a 32 bit or a 64-bit version, accordingly, download the correct version of Microsoft Visual C++ 2010 Redistributable Package directly from Microsoft’s official website. Simply download and install the software. Then follow the prompts to add the toolbox to your PC. After that, restart your computer; most likely the error message will be gone. If it still persists, then this means the error is either related to the registry or malware.

Download and Run Restoro

Restoro can be used to resolve both malware infection and registry issues on your PC that could be triggering Msvcr100.dll errors. Restoro is a next-generation and multi-functional PC repair tool embedded with powerful utilities like an antivirus, a registry cleaner, and a system optimizer. The registry cleaning feature detects all registry issues and Msvcr100.dll errors. It removes unnecessary and obsolete files on the disk, like junk files, cookies, internet history, and temporary files cluttering the disk and damaging dll files. It repairs the damaged and corrupt dll files and restores the registry. Simultaneously the antivirus feature scans and removes all malicious software on your system. These include spyware, viruses, Trojans, adware, and malware that can damage dll files. This software is efficient and resolves the Msvcr100.dll error in seconds. It is easy to use and has a simple navigation. It is compatible with all Windows versions. Click here to download Restoro on your PC and resolve the Msvcr100.dll error today!
Read More
Fix Windows Activation error code 0xC004F078
As you know, Windows 10 has a complicated mechanism for Activation which helps in the verification of a genuine copy of Windows 10. However, there are times when you might encounter some errors during the activation process. One of these errors is the error code 0xc000f074. This kind of error could be due to the Key Management Service or KMS which is unreachable by the client computer or if the key used in the SLSetAuthenticationData function call is incorrect. This kind of error mostly affects surfaces on computers that are upgraded from either Windows 7 or Windows 8.1 to Windows 10. In such cases, you may encounter any of the following error messages:
“Windows is unable to reach your company’s activation service. Please connect to your corporate network. If you are connected and continue to see the error, contact your system administrator. You can also click on the error detail to find the exact error. Error code: 0xC004F074.” “Activating Windows(R), (Key hash)… Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.” “Error 0xC004F074, SL_E_AUTHN_MISMATCHED_KEY, The Software Licensing Service reported that the key is mismatched.”
To fix the Windows 10 Activation error 0xC004F078, you have to use the correct key for your type of Windows copy or use Command Prompt to reinstall the key or you could also try running the Activation troubleshooter.

Option 1 – Try running the Windows 10 Activation Troubleshooter

The first thing you can do to resolve the Activation error code 0xc000f074 is to run the Windows 10 Activation Troubleshooter. To do so, follow these steps:
  • Go to Settings and then select Activation.
  • After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.
The Windows 10 Activation Troubleshooter will determine if your license key is a valid Windows 10 digital license for an edition that is not currently installed. If it turns out that it’s not, then the troubleshooter will show you how to install the correct edition.

Option 2 – Try to use the correct key for the type of Windows version you have

If the Windows Activation troubleshooter wasn’t able to resolve the error, then you can try using the correct key for your type of Windows version. All you have to do so is check the type of your Windows copy if it’s OEM, retail, or volume. And make sure that you have the correct, valid product key for your operating system.

Option 3 – Try to use Command Prompt to reinstall the key

  • In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select “Run as administrator”.
  • After that, execute this command to uninstall the existing key: vbs /upk
  • Next, you need to install the KMS product key by executing this command: vbs /ipk <The KMS Product Key>
  • Once you’re done, you will see a prompt that’ll tell you whether the operation was either successful or not.
  • To active, the KMS product key online, use this command: vbs /ato
  • Use this command to activate the key using the telephone: exe 4
  • After you’ve activated the KMS product key, restart the Software Protection Service. You can also verify the Activation Status to check if your fix was successful or not.

Option 4 – Contact Microsoft Support for assistance

If you’re at your wits’ end in trying to upgrade your computer, you should consider contacting Microsoft Support for help as they can offer you various options that would make fixing Windows Activation error code 0xc000f074 a lot easier and faster.
Read More
Media Creation Tool Error 0x80042405-0xA001A
As you know, the Windows Media Creation Tool is a great utility in Windows that helps lots of users in installing Windows on their PCs. However, just like any other program in Windows, it also experiences a couple of issues every now and then. So in this post, you will be guided on how you can resolve a particular issue in the Media Creation Tool which is the error 0x80042405-0xA001A. You can encounter this error while creating a USB installation media used in installing Windows 10. When getting this kind of error in the Windows Media Creation Tool, you will see the following error message on your screen:
“We’re not sure what happened, but we’re unable to run this tool on your PC, Error code 0x80042405 – 0xA001A”
The error 0x80042405 – 0xA001A occurs while creating a bootable USB installation drive. This is a common error faced by many users and it has something to do with the USB hardware. To get this issue fixed, here are some suggestions you could check out.

Option 1 – Try to reformat the USB drive

Reformatting your USB drive might help in fixing error 0x80042405 – 0xA001A.
  • Open This PC and right-click your USB drive from there then select Format.
  • Next, select FAT32 as the drive type and uncheck the “Quick Format” option.
  • After that, try to run the Windows Media Creation Tool again and check if the error is fixed or not. But hopefully, it should work since formatting the drive as FAT32 will give the driver a proper type and would resolve any minor issues in the drive.

Option 2 – Copy the Windows Media Creation Tool to the USB drive

If the first option didn’t work, you might want to copy the latest version of the Media Creation Tool to the USB drive. After you do that, you can run it from inside the drive. This is actually a working fix and can definitely get the USB drive to run with Windows inside it so it should resolve the error 0x80042405 – 0xA001A on the Windows Media Creation Tool.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.
  • Tap the Win + S keys to open the Search box.
  • Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
  • After opening an elevated command prompt, copy and paste the following command and hit Enter:
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]
Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.
  • Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
  • If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
  • After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
  • Wait until the process is completed and then restart your computer.

Option 4 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.
Read More
Delete Downloaded, Failed and Pending Windows Updates in Windows 10
There are instances when instead of fixing problems the Windows Update brings you problems on your Windows 10 computer. You might even see some pending Windows Updates which for some reason, refuse to install no matter what you do. The good thing is you won’t have to deal with those failed and pending updates that are incompletely downloaded to your PC as you can actually delete them. Follow the instructions prepared below to delete the failed and pending Windows Updates.

Step 1: The first thing you have to do is delete all the contents in the Temporary folder

  • Tap the Win + R keys to open the Run dialog box.
  • Next, type in “%temp%” in the field and hit Enter or click OK to open the Temporary folder.
  • From there, select all the folders and files within the Temporary folder and then delete them all.
Note: %temp% is one of the many environment variables in Windows that could open the designated folder by Windows as the Temporary folder which is usually located at C:\Users[username]AppDataLocalTemp.

Step 2: Next, remove the pending.xml file

  • Go to the C:\Windows WinSxS folder.
  • Once you’ve opened the folder, look for a file named “pending.xml” file and right-click on it and you can either rename it or delete it.
  • After that, the Windows Update should delete the pending tasks and build a fresh new update.

Step 3: Delete all the contents of 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. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.
  • 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, got to the C:\Windows\Software\Distribution 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.

Step 4: Try resetting the catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process.  So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.
Read More
Applications you should remove from Windows
ApplicationsOver time Applications change, some for the better some for worse. Some of them even stop receiving updates and are old and vulnerable. Sometimes standards change and some file types are not used anymore. Software evolves along with technology and that is good. Keeping old and useless applications inside your Windows is not so good. From various exploits to simply taking up space, maybe even slowing down OS it is always wise and good to clean your Windows from unwanted old applications. In this article, we will be mentioning some relics of old and providing you with an explanation of why you should remove them from your system if by any chance you still have them on it.

Silverlight

Silverlight was meant to be a competitor for Adobe Flash, it is a WEB framework that enables rich media content inside your WEB browser. The issue is that it is not developed anymore and today's browsers do not support it. The only browser that actually can support it is internet explorer which itself is not supported and how there is practically 0 content on today's modern WEB that will require Silverlight, it is safe and recommended to remove it.

Adobe Flash

Speaking of Adobe Flash, you should remove it as well. Flash has stopped receiving support as of January 2021 and browsers have dropped support for it and even blocked it due to security issues. However, there still might be some local installation of Flash itself inside Windows along with the old Shockwave player that stopped receiving support in 2019. You should remove them both.

JAVA

Now this one is tricky, by itself JAVA does not present any security issues since browsers do not support it anymore and the desktop version is not really slowing down your computer. This one has simply put just another media runtime that is not used and simply takes up space and resources. However if you have some applications that you do use that rely on it (I can really just think of JAVA Minecraft at this point) leave it of course but in any other case, it is just purely not needed.

Quicktime

While we are at media runtime and stuff that just simply is not needed, Quicktime is one of them. Now this Apple Video player and codec is still pretty developed and active in Apple’s iOS environment, Windows version has not been updated since 2016 and it was discovered that it contains some critical vulnerabilities. Uninstall it and if you need a player that could play MOV files, just use a VLC player that can play them without any separately installed codec.

uTorrent

This one, the same as CCleaner was once a good application, as a matter of fact, it was the best torrenting application. Sadly it has fallen from its grace very low, from getting tons of ads in its interface to findings in 2015 that code of torrent client was packed with a crypto miner that used system resources of an installed computer to mine crypto without user’s awareness. You should uninstall this torrent client if you would like to get your PC back and not provide it for cryptocurrency mining for the company that developed it. Use qBittorrent or TIxati, open-source and free ones that have everything needed for any torrenting needs.

Toolbars and Browser extensions

There are a lot of toolbars for browsers and extensions that are malicious in nature or simply not updated providing security issues. It is very advisable to remove this as soon as possible.

WinRAR

WinRAR has gained its large popularity solely for the reason that you could download it from the official site like shareware and use it forever. The license never expired and you could use it indefinitely. Sadly not much has been improved in the application itself and it is slowly falling out in its range of what it can do. There are better open source and free options today like 7zip, PeaZip, ZIPvare, and more that are working the same as WinRAR if not even better.

Windows and manufacturers Bloatware

Yes, applications that come bundled with Windows and with some laptops that include manufacturers made software for different tasks like its own specific media players, calculators, etc. It is known that these applications are not better than their open-source rivals and there are too many of them including some that you will probably never use. It is the same as buying a new phone bundled with tons of applications that you do not need, did not ask for, and do not use. Delete all of them. Considering Windows there are also some Store application like Candy Crush Saga demo and other are safe to remove if not needed. That’s it, our advice for old and not needed applications so you can keep your PC safe and fast.
Read More
Enable or Disable Windows 10 Boot Log
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.
Read More
NVIDIA Control Panel keeps crashing
The NVIDIA Control Panel is a useful tool for users who have NVIDIA graphics on their PCs as this tool allows users to how the graphics card is used on the computer using several controls that come with the graphics card from NVIDIA. Thus, it can be quite inconvenient when it suddenly crashes all of a sudden for some reason. This kind of problem could be due to the toggling of Output Dynamic Range is limited, or there could be some issue with the integrity of the Power Supply for the graphics card, and many more. So if you are using NVIDIA on your computer and its Control Panel keeps on crashing on your Windows 10 computer, then you’ve come to the right place as this post will guide you in sorting the problem out. For more details, refer to the guidelines laid out below.

Option 1 – Try to toggle the Output Dynamic Range

The first thing you can do to fix the problem is to toggle the Output Dynamic Range by following these steps:
  • Navigate to this path: Display > Change resolution.
  • Next, scroll a bit on the right-side panel until you see the Output Dynamic Range drop-down.
  • After that, select “Full” from the drop-down menu.
  • Apply the changes you’ve made and see if it is able to fix the problem with the NVIDIA Control Panel.

Option 2 – Try changing the Power Management and Vertical Sync settings

The next thing you can do to fix the problem is to change the Power Management, as well as the Vertical Sync settings.
  • Open the NVIDIA Control Panel and go to this path: 3D Settings > Manage 3D Settings.
  • Next, set the Power Management to be “Prefer Maximum Performance” for your processor located on the right-side panel.
  • After that, set the Vertical sync setting off and then click on the Apply button located at the bottom-right portion of the window and check if it is able to fix the problem or not.

Option 3 – Try updating the drivers from the official site of NVIDIA

If both the first and second given options didn’t work, you can also try updating the drivers from the official NVIDIA website. And in case you don’t know the type of Nvidia graphics card that your computer is on, follow the steps below:
  • Tap the Win + R keys to open the Run dialog box.
  • Next type in “dxdiag” in the field and click OK or hit Enter to open the DirectX Diagnostic Tool.
  • From there, you can see what type of Nvidia graphics card that your system is on.
  • Take note of your graphics card information and then look for the best drivers for your operating system. Once you’ve downloaded and installed the file, restart your PC.

Option 4 – Try to roll back the driver to the previous version

If updating the NVIDIA display drivers didn’t work for you, then it’s time to roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh.
  • Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the NVIDIA Drivers and expand it.
  • Next, select the driver entries that are labeled appropriately.
  • Then select each one of them and double click to open a new mini window.
  • After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the NVIDIA Drivers.
  • Now restart your computer to successfully apply the changes made.
Read More
Changing the Primary and Secondary monitor
If you are using a dual monitor setup on your computer and you wish to change the Primary and Secondary monitor in Windows 10, then you’ve come to the right place as this post will guide you on how exactly you can do that. A lot of users use more than one monitor to be more productive so having dual monitors helps a lot. So if you have more than one monitor, know that you can actually select any monitor as the primary monitor after installing Windows. Changing the primary and secondary monitor in Windows 10 does not really require you to install any third-party application since you can get the job done by simply making some alterations in the Windows 10 Settings panel. You won’t have any problem in making such alterations since it is quite simple – from modifying the wallpaper to scaling and so on.

To get started, follow the instructions given below carefully.

Step 1: First, tap the Win + I key combination to open the Windows 10 Settings app and go to System and click the Display tab. Step 2: Next, look for the Identify button located on your right-hand side and then click on it. This button will help you check which one is the primary and the secondary monitor. Step 3: After that, select the desired monitor that you want to set as the primary one from the drop-down menu. Step 4: After that, mark the checkbox for the “Make this my main display” option. Step 5: After choosing the primary monitor, this will automatically set the other monitor as the secondary monitor. Restart your computer. So that’s how you change the primary and secondary monitor on your Windows 10 computer. Note that you can always go back to the previous setting of your monitor by following the same instructions provided above.
Read More
Fix mfewfpk.sys, Epfwwfp.sys Errors in Windows
If you suddenly encounter a Blue Screen error that points out to either the mfewfpk.sys and epfwwfp.sys files, then this post might help. Both of these files are created by third-party software. The mfewfpk.sys file is created by the McAfee security software while the epfwwfp.sys is created by the ESET Antivirus. These files are residual files and sometimes it blocks upgrading Windows 10. Aside from blocking Windows 10 upgrade/update, these files can also cause a Blue Screen error after an upgrade which leaves your Windows 10 computer useless. When you get a Blue Screen error caused by any of these files, you will see an accompanying error message that states, “DRIVER IRQL NOT LESS OR EQUAL”. To fix this Blue Screen error, you can check out the suggestions laid out below but before you do that, you need to create a System Restore point first as it can help you undo any unwanted changes. In addition, make sure to also boot your computer into Safe Mode with Networking before you troubleshoot.

Option 1 – Try to remove the epfwwfp.sys file

You can try to remove the epfwwfp.sys file using Command Prompt. To do so, refer to the following steps:
  • Right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
  • Next, type the following command and hit Enter to delete the epfwwfp.sys file:
DEL /F /S /Q /A “%systemroot%System32driversepfwwfp.sys”
  • After the scan is completed, restart your computer and see if it fixed the Blue Screen error.
Note: You can also use the ESET AV Remover tool to uninstall Eset security software to remove the epfwwfp.sys file.

Option 2 – Try to remove the mfewfpk.sys file

The same with the first option, you can remove the mfewfpk.sys file using CMD.
  • First, right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
  • After, type the following command and hit Enter to delete the epfwwfp.sys file:
DEL /F /S /Q /A “%systemroot%System32driversmfewfpk.sys”
  • Once the scan is completed, restart your computer and see if it fixed the Stop error.

Note: You also have the option to remove the mfewfpk.sys file using McAfee Product Removal tool to uninstall the McAfee security software. All you have to do is download the McAfee Product Removal tool and run it and then follow the onscreen instructions to install it. Once it is installed, click on Next. After you select the radio button to agree to the terms of use, click on Next once again. Finally, restart your computer and check if it is able to resolve the problem or not.

Option 3 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Blue Screen 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
    • 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.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status