Google Chrome 94 is here and it has introduced a controversial idle detection API. For those people that do not know what idle detection API is, well basically Chrome can be asked by a website to report when a user of the site has a site open and is idle on the device. The issue that people have with this is that this particular feature can be used to report when the user is not using a computer at all. Good thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this. Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:

As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)… Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.

Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:

That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another device user might be using at any given point? We’re definitely not going to let a website know all the devices a given user might be using at any given point. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.

Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.

If your operating system cannot or is not able to load a required DLL file on your Windows startup and you encounter a message saying, “Failed to load DLL”, then you’ve come to the right place as this post will guide you in fixing this problem. When you encounter this kind of issue, you will see either of the following error messages on your screen:

“The dynamic library dll failed to load.” “Failed to load dll library.”

This kind of error can occur when your Windows operating system fails to locate the DLL library which the system needs to access during startup. It can also occur when the DLL file is not in a directory specified in the path or when the DLL file is corrupted or has gone missing. Moreover, you can also encounter this error if the DLL file is infected with some malware. Whatever the case is, here are some suggestions you have to check out to resolve the problem.

Option 1 – Try to reinstall the program

The first thing you can do is to reinstall the program that’s giving you this error. Once you’ve uninstalled the program, download its latest setup file from its official site and then install it again.

Option 2 – Try checking the startup programs

You might also want to check the startup programs on your computer, especially the Windows Registry startup paths, and then remove the startup entry to the concerned DLL file.

Option 3 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file with a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Try checking the details in the Event Viewer

Checking the details in the Event Viewer can also help you find out the root cause of the problem as the Event Viewer usually contains detailed information about the error.

Option 6 – Try running the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the “Failed to load DLL” error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the “Failed to load DLL” error is now fixed.

Option 7 – Try scanning your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “Failed to load DLL” error. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

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.

As you know, the CHKDSK utility is proven to be one of the useful tools to fix any issues that concerns file system, storage, and disk. However, as useful as it may be, it is still not immune to issues as you could encounter errors when running it. One of these errors is the “One such error is the CHKDSK cannot continue in read-only mode” error. If you receive such an error message while running CHKDSK, then you’ve come to the right place as this post will help you sort the problem out. It is possible that the drive is read-only or that the Write Protection is enabled. It could also be that the drive is already being used and scanned by a different program or utility. To get rid of this error, there are a couple of suggestions you need to check out. You can try to run the CHKDSK utility from Recovery or run it on Boot. You could also try to disable Write Protection. For more detailed steps, follow the given instructions below.

Option 1 – Try to run the CHKDSK utility from Recovery

The first thing you can do to resolve the error in CHKDSK is to run the CHKDSK utility from Recovery. How? Follow these steps:

• First, boot into the installation environment for Windows 10 from a Windows installation media.
• Next, click on the “Repair your computer” option.
• After that, select Troubleshoot > Advanced options > Command Prompt.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /r /f
• Wait until the disk error checking process is completed.
• Once it’s done, exit the Command Prompt window and restart your computer and then see if the error is fixed.

Option 2 – Try running the CHKDSK utility on Boot

On the other hand, you can also try to run the CHKDSK utility on Boot so you can fix the error and recover any damaged segments of the drive.

• Open an elevated Command Prompt and enter this command: chkdsk /r
• After that, you will a message that says, “Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”
• Type Y and tap Enter to schedule a CHKDSK scan once your computer reboots next time.

Option 3 – Try to remove the Write Protection from the drive

As mentioned, removing the Write-Protection on the concerned drive could also help you fix the problem and there are two ways to get rid of the write protection – you can either use the Diskpart utility or the Registry Editor. How? Refer to the following steps.

Via Diskpart utility:

• Open Command Prompt with admin privileges and then type the “diskpart” command and tap Enter to execute it.
• Next, type “list disk” and tap Enter to get the list of all the Disk connects or all the partitions that are formed on those disks.
• After that, you need to choose one command depending on the list of commands you entered. Type “select disk #” and tap Enter to select the disk or partition you want to select.
• Then type “attribute disk clear readonly” and tap Enter to Disable the Write Protection on the selected disk or partition.

Via Registry Editor:

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to the following registry key:

ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlStorageDevicePolicies

• After that, look for the DWORD named “WriteProtect” and double click on it, and then set its Value Data to “0”.
• Now restart your computer and see if the problem is now fixed or not.

Repair Outlook PST Mailbox Errors

Outlook PST Mailbox Errors Malfunctions

Can you use an MS-Outlook e-mail account to send and get workplace e-mails on a daily basis? Are you using the exact same Outlook e-mail account for a long time? Are you getting PST Mailbox Errors? Then you have developed awareness and knowledge about Outlook PST Errors. Ms-outlook essentially stores the email items in a PST record. This includes all attachments, contacts, calendar items, your e-mails and records. You might encounter various kinds of Outlook Inbox error messages exhibited on the display in extended formats eg. 0x80040600 0x8004060c or 0x80040116. All all these are Outlook mailbox malfunctions that stop the Outlook program from executing jobs correctly and thus restricting your capacity to gain access to your e-mail account, see attachments, contacts, and calendar items that are significant.

Error Causes

There's not a single particular trigger for Outlook email malfunctions. A few causes can trigger these, but, the most frequent are virus contamination, 2 GB limit is exceeded by PST file and broken. There are no specific signals which will help help you identify but some pointers to look at include the following:-

• You cannot access certain parts of your Outlook interface
• Obscure error messages start popping on your screen
• You can’t add new contacts or change entry data in your calendar

Further Information and Manual Repair

When you experience these signs related to PST Inbox errors, it is advisable to repair the problem immediately to ensure it does not cause inconvenience for you and hampers your communication via Outlook emails. Remember this error not only inconveniences you but also hinders proper communication between various business partners. Determining the ultimate reason for distinct Outlook email malfunctions could be tricky, time-consuming, and might need specialized knowledge to nail it down with regards to fixing the Outlook mailbox malfunctions. In case you are not a specialist, working out and fixing this problem is an uphill process. To simplify this process, obtain and install an Outlook PST Repair Tool! This is an intelligent solution to fix all kinds of Outlook errors. You do not have to go deeper into the technical details of the problem. The Outlook PST Repair tool does it for you. An inbox repair tool identifies and also repairs all sorts of MS Outlook errors in seconds. It is easy to use, highly functional, safe and efficient. By installing an Outlook repair tool, Outlook errors can be easily removed from your computer and keep the errors from happening again. It also fixes damaged PST files and damaged e-mails can help regain data. Whatever you should do is to begin:

1. Click here to download the inbox repair tool
2. Install the software on your system
3. Run it and click restore to resolve Inbox errors

[vc_row][vc_column][vc_column_text]

Business Email Etiquette

Hello and welcome to our Business Email Etiquette. Most people have experience in writing emails at some point before in their lives. However, the emails an average person writes are probably personal emails and not mails for work purposes. Emails you send to friends are incredibly different in content and context to business emails you would send to customers or employers or even other colleagues in your workforce. So, if you have a job that involves you writing emails to people in business style, learning business email etiquette is an absolute must for you.

 1. Heading layouts

When you are sending emails to friends, you generally lay them out like a memo. This means there is very little detail in the layout besides basic greetings and paragraphs, usually starting with the greetings. However, with a business email, it is best to lay it out exactly like you would lay out a formal letter. You need to put the company’s address in the right-hand corner and the date as well. Only then must you go on to the greetings. This will make your email look more formal, making you seem like a professional who knows what they are doing as opposed to someone who just couldn’t be bothered spending the extra time to get the layout right.

 2. Proper greetings

 When you are sending an email to a friend, you usually greet them informally. If their name was Mary Johnson, you’d probably start your letter with a ‘Hey Mary’ or a ‘Hello Mary.’ However, this is not considered a professional way to write an email to a customer or other important person in your business. Again, you must use the proper method that you would greet someone with were you writing them a formal letter instead. If your customer is Mary Johnson again, you should greet her with respect. ‘Dear Ms. Johnson’ would be the most appropriate way to start off your letter’s actual body in this case. If you do not know the recipient’s name, then you should start with a simple ‘Dear Sir or Madam.’ Politeness will always get you incredibly far, no matter what line of work you are in.

 3. Informal language

 You should get straight to the point with your email. Don’t dawdle on with it like you would if chatting to a friend and don’t write it how you would speak either. You use language that sounds impressive and smart while not using such obscure language that your recipient doesn’t know what you are saying. All the time, you must keep it informal where possible, possible even impersonal as well. It will make you seem very professional in the long run.

 4. Signing off

When you are ending your email, you must end it as you would with a letter also. Don’t just say ‘Bye’ and your first name; that is too personal. You need to say ‘yours sincerely if you know the name of the recipient and ‘yours faithfully’ if you do not. Then you should end with your full name and whatever position you have at the company. (CEO, technical staff etc.) So there you have it! All you need to do now is to show your boss that you can handle the emails from now on![/vc_column_text][/vc_column][/vc_row]

Quick Solution to Error Code 40

Error Code 40 – What is it?

Error Code 40 is a device driver error that users encounter on any Windows 2000 and later operating systems. It occurs when the peripheral device that you connect to your PC cannot be accessed due to a change in the system registry.

This is due to the presence of invalid sub-keys of the device driver in the system registry. It is a common error that users come across and appears on your PC with either of the following messages:

“Information in the registry entry for this driver is invalid”

OR

"Windows cannot access this hardware because its service key information in the registry is missing or recorded incorrectly. (Code 40)"

Solution

Error Causes

As mentioned above, the error code is triggered when the device driver’s invalid sub-keys appear in the registry, effectively changing it. This happens when the windows system files get damaged due to the following factors:

• An incomplete program uninstallation
• An incomplete program installation
• Hardware is not removed properly
• System recovery from viruses
• An improper system shut down

Factors such as incomplete installations or uninstallations or an improper system shut down can cause files to become damaged that threaten the health of your computer.

Removing viruses from the computer is also another factor as it removes the entries in the Windows system files which contain the viruses including spyware or malware

Further Information and Manual Repair

Fixing Error Code 40 is similar to fixing other device manager error codes. Here are a few methods you can try.

Method 1 – Use System Restore

You can use system restore to eliminate the problem. Here is how you can use it:

• Log in using an Administrator account
• Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
• Click ‘Restore my computer to an earlier time’ and click ‘Next’
• Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
• Click ‘Next’ on the confirmation window to proceed
• Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system registry files that can help avert the error code.

Method 2 – Manually uninstall then reinstall the device driver

If using system restore also does not work in removing the error code, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.

This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what contributes to the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files.

You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC. Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’.

Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 3 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick, however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.

It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 40.

It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage.

Thus, registry damage can be averted by letting the software roll back the system files to an earlier healthy checkpoint. Driver Assist is the answer to fixing your PC error codes accurately and quickly.

Click here to download DriverFIX to fix Error Code 40 quickly and effectively!

In case you don’t know, Windows 10 now allows users to check the Bluetooth battery level of devices. More often than not, the accessories or peripherals users use for their Windows 10 devices are connected to it using Bluetooth technology. This high-speed low-powered wireless technology is designed to link mobile devices, computers, and other network devices over a short distance wirelessly. Monitoring the battery level of a device where Bluetooth is enabled isn’t an easy task as most of these devices do not support the Bluetooth battery monitor or the battery level display. And even when on devices that do, you still have to install additional software to find it. However, Windows 10 eliminates this requirement and all you have to do is add a Bluetooth device and connect that Bluetooth device. How? Follow the instructions provided below. Step 1: Adding a Bluetooth Device The easiest way to get your Bluetooth device battery to be displayed on your Windows 10 screen is to simply add a Bluetooth device. To do so, follow these sub-steps:

• First, turn on the Bluetooth mode on your device.
• Next, go to Windows Settings > Devices > Bluetooth & other devices.
• From there, click on the “+” button next to the ‘Add Bluetooth or other devices” option and select the type of device you want to add.

Step 2: Connecting the Bluetooth Device Once you’ve added the device, it will be visible under the “Add a device” screen.

• Now select the newly added Bluetooth device and click the “Done” button.
• After that, it will now be connected. Go back to the “Bluetooth & other devices” window and scroll down to the section of “Mouse, Keyboard, and Pen”.
• From there, move the cursor alongside the connected device to display its battery level.

Keep in mind that there are several ways in which you can display the battery information of the Bluetooth device. However, Windows 10 understands only one of them per se. So if your device is not a Bluetooth Low Energy device, Windows 10 won’t be able to show its battery information and won’t display its battery level.

If you are using a Windows 10 PC that has different processors clubbed together, chances are you might encounter an error saying, “MULTIPROCESSOR CONFIGURATION NOT SUPPORTED” during a Windows upgrade or software installation. This error is actually caused by a bug check with a value of 0x0000003E. This error also indicates that the processors in your computer are asymmetric in relation to one another. So if you want to upgrade you need to have all the processors of the same type and level. But worry not for this guide will help you in fixing this error. The MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED error can occur in several cases such as during an installation of Windows 10, or when the driver is loaded, or when Windows Start or Shutdown and the chances of you getting a blue screen is very much high. To fix this error, refer to the options given below and make sure to follow them carefully.

Option 1 – Try to disable the Hyper-Threading in your BIOS

Hyper-Threading in the BIOS lets a processor (multi-threaded) run various tasks in a simultaneous manner. To disable this, here’s what you have to do:

• Restart your computer and boot into it right after. To do that, tap the F2 key.
• Once you’re in the BIOS, locate the Hyper-Threading option which should be located under the Performance section along with other options like Multi-core support, Rapid Start technology, and many more.
• Disable Hyper-Threading and then make sure to save the changes and exit BIOS.

Note: Although Hyper-Threading is only used when necessary, there are some OEMS that don’t have the option to disable it and if that’s the case, you need to try other options given below.

Option 2 – Try to disable the Virtualization in the BIOS

Virtualization in the BIOS allows users to run a single physical resource such as the server or storage device to appear that it is running as multiple logical resources. It is also properly termed as “HYPER-V”.  To disable it, refer to these steps:

• Boot into the BIOS as you did earlier.
• Then look for the Security options.
• After that, from Security options, look for Virtualization Technology or VTX among the options given.
• Then turn it off and restart your computer.

Note: Although Windows 10 offers features such as the Device Security for Core Isolation and Memory Integrity, if you turn them off at the software level, it will not help at all. If you’re able to resolve the error, you can do some further research and see what software or hardware you can use to further help you.

Option 3 – Try checking if there are any BIOS updates available for your PC

Updating the BIOS may help you resolve the MULTIPROCESSOR CONFIGURATION NOT SUPPORTED error. You can just go to the OEM’s website as they offer utility software that can download BIOS firmware and update it without any problem. BIOS updates usually offer enhancements and fixes to some issues like this one.

In this post, you will be guided on how you can fix error 0x80070013 while executing various operations in your Windows 10 computer like System Restore, Windows Backup, or Windows Updates. When you encounter error 0x80070013, you will see the following error messages. For System Restore, it states:

“System Restore did not complete successfully. Your computer’s system files and settings were not changed. Details: System Restore failed while scanning the file system on the drive <Partition Letter> The drive might be corrupt. You might want to retry System Restore after running chkdsk /R on this disk. An unspecified error occurred during System Restore. (0x80070013) You can try System Restore again and choose a different restore point. If you continue to see this error, you can try an advanced recovery method.”

Whereas in Windows Backup, it states:

“Check your backup, Windows Backup failed while trying to read from this shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. The backup failed, The media is write protected (0x80070013).”

On the other hand, you will see the following error message in Windows Update:

“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact the support for information, this may help: (0x80070013).”

There are several suggestions you can check out to fix the error depending on where you encountered it. If you encountered it while running Windows Updates, then you can try to reset the Windows Update components or run the Windows Update Troubleshooter. And if you got the error when running System Restore, you can try to run a System File Checker scan or the DISM tool as well as the CHKDSK utility. Lastly, if you got this error when running the Windows Backup service, you can try to check its status in the Services Manager. Error 0x80070013 in Windows Updates:

Option 1 – Try to reset the Windows Update components

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:/Windows/SoftwareDistribution/SoftwareDistribution.old
  • ren C:/Windows/System32/catroot2/Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 2 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing error 0x80070013. 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. Error 0x80070013 in System Restore:

Option 3 – Try to run both Systems File Checker scan and DISM tool

Running the System File Checker scan as well as the DISM tool can help you resolve error 0x80070013 while performing System Restore. Refer to these steps to do so.

• Open the Command Prompt with admin privileges.
• After opening Command Prompt, execute this command to run a System File Checker scan: sfc /scannow
• Once the scan is completed, restart your computer and then see if the error is now fixed. If not, you can run the DISM tool.
• Open Command Prompt with admin privileges again.
• Then type in the following commands and make sure to hit Enter right after you type each one of them in order to properly run the DISM tool:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /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.

Option 4 – Run the CHKDSK utility

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f /r /x /b
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Error 0x80070013 in Windows Backup:

Option 5 – Try checking the status of the Windows Backup Service

• 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.
• After that, you will see a list of services and from there, look for the Windows Backup Service and double click on it to open its Properties.
• Then check if its Startup type is set to Disabled. If it is, then change it to “Manual”. Note that this service is essential as it provides backup and restores capabilities.
• Now click on the Apply and OK buttons to save the changes made and then restart your computer. Check if the error is now gone.