Windows 11 different sounds for dark theme

The Windows 10 operating system supports the logging in of multiple users at the same time. Aside from that, it also allows administrators to create a Guest Account that has limited rights. However, there are some instances when you could encounter an error when you use the Guest Account. The error may state:

“Shell Infrastructure Host has stopped working. A problem caused the program to stop working correctly. Please close the program”.

This error indicates that the Shell Infrastructure Host or SiHost.exe process that is used for handling graphical elements, has crashed. And to fix this error, there are several options you can check out. You can try to reinstall the Microsoft Redistributable Packages or run a System File Checker scan. In addition, you can also use a new Guest Account or troubleshoot the problem in a Clean Boot State.

Option 1 – Try to install or repair Microsoft Visual C++ Redistributable 2013

A corrupted Microsoft Visual C++ Redistributable package or the absence of it can trigger the “Shell Infrastructure Host has stopped working” error – so if you do not have this package yet, you have to install it but if you already have it, follow the steps below to repair it.

• Open Control Panel and proceed to Program and Features.
• Under Programs and Features, look for Microsoft Visual C++ Redistributable package among the list.
• Then right-click on it and click the Change button.
• Next, you should see the Repair option – click on it to repair the installation of the Microsoft Visual C++ Redistributable package.
• The process may take a couple of minutes before it finishes so once it does, you have to restart your PC.

After doing all these steps and you still encounter the problem, you might have to uninstall this package and download it directly from Microsoft’s website. However, if you are using Windows 10, you might not be able to do so since it only supports Windows versions up to Windows 8.1 so just proceed to the next option below.

Option 2 – Try to run a System File Checker scan

• In the Windows Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, type the “sfc /scannow” and tap Enter to execute it.
• Once the scan is finished, restart your computer and see if the Windows Script Host error.

Option 3 – Try using a new Guest Account

You might want to use a new Guest Account as it could help get rid of the error. All you have to do is have your admin delete the old Guest Account and create a new one and see if it helps in fixing the error.

Option 4 – Try troubleshooting the problem in a Clean Boot State

Setting your computer in a Clean Boot State can help you diagnose and later troubleshoot the problems in your computer. During this state, the system will start with a minimal number of drivers and startup programs that help in isolating the problem with the interfering software. To put your computer in a Clean Boot State, follow the given steps below.

• Log onto your computer 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.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

If you encounter a blank page with an error message saying, “Origin Error” when you try to load a webpage, then this post will surely help you resolve this error. As you can see, this error is a very uncommon one and it is not about the popular game known as Origin where all you have to do is reinstall the client. Although this error message is a very uncommon one, you will see a blank page with a message saying, “Origin Error” when you attempt to load a webpage. To fix this error, this post will provide you some potential fixes that might help. Follow the fixes given below carefully and see which one fixes the problem.

Option 1 – Use Ctrl + F5 keys to clear browser cache

The first thing you can try is to “Hard Refresh” to clear the cache of your browsers. You can do that by using the Ctrl + F5 keys on your keyboard. On the other hand, you can also clear the cache manually for Chrome, Edge, and Firefox.

Option 2 – Remove the Proxy

You might also want to try removing the Proxy as it could also help you in fixing the Origin error. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Try to flush the DNS, reset Winsock and the TCP/IP

You might also want to flush the DNS and reset Winsock as well as reset TCP/IP as it could help in fixing the Origin error. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

• Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.

Option 4 – Try using Google Public DNS

You might want to try changing your current DNS to the Google Public DNS. All you have to do is change the DNS settings explicitly on your operating system by using the DNS IP addresses. Here’s are the steps to do that:

• 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” and “8.8.4.4” and click OK and exit.

Recently, some users reported not being able to boot up their Windows 10 computers. And during the startup phase, at some time, the bootup sequence is halted with a Recovery error along with an error message saying, “Your PC/Device needs to be repaired” with an error code of 0x0000605. This kind of error message indicates that Windows was not able to verify the digital signature for the file as the signing certificate or it could be that it has expired. To resolve this error, you can follow the potential fixes given below and see if you stumble upon a fix that might work out for you.

Option 1 – Change the Date & Time settings in the BIOS

Some users reported that they were able to fix the error by changing the Date & Time settings in the BIOS. Upon checking, they saw that in their BIOS settings, the date was off several years. As a result, the incorrect date and time settings end up ticking the system into believing that the Windows build has expired long before the actual expiration date. You can check if the error pops up due to the same reasons by accessing the BIOS settings. To do so, you have to tap the Boot key that’s associated with your motherboard manufacturer during the initial startup phase. After that, you can search for a particular boot key online or you can also tap keys like F2, F4, F8, F10, F12, and the Delete key. Once you’re able to access the BIOS settings, locate the Date & time or anything similar, and then check if the date is correct or not. If not, you need to change the date to the actual date and then save the changes made and restart your computer and then check if the issue is now fixed or not. Just remember that if the actual date is past the expiration date of the build you have, you need to change it to an older date. If your Windows 10 PC is able to boot back up, you have to update it to a stable Windows build and then go back to the BIOS settings and change the date to the current one else you will definitely encounter Windows update errors in the future as well as security alerts.

Option 2 – Perform a clean install of a stable Windows 10 build

If every system boot fails accompanied by a BSOD error with error code 0x0000605 “A component of the operating system has expired” and you’ve already followed every instruction on option 1, then it’s most likely that your current Windows build has already expired. Remember that almost all the Windows 10 Insider Preview builds (98xx) are created along with an expiration date and when your computer reaches the expiration date, you won’t be able to boot your computer up. Note that the exact expiration date varies based on the build number. And prior to the expiration date, the operating system will start to display some error warnings telling you that the build will expire and urge you to update the most recent build available. And so once the computer reaches its expiration date, it will begin to reboot every three hours until it no longer boots up which is about 2 weeks approximately after the license has expired. Once the expiration date is up and your computer no longer boots up, you need to perform a clean install and then install the latest Windows 10 build to resolve the issue once and for all.

169 IP address error can stop your computer from connecting to the internet which could be a very frustrating experience. In this guide, we will cover simple but effective tips on how to fix this error so you can continue with internet use.

1. Reconnect your Modem or Router

   Simple and sometimes effective solution, unplug and plug back in modem or router so IP is fetched again, it is very likely that computer will pick right IP address with this stunt.

2. Use built-in Windows Network troubleshooter

   Press ⊞ WINDOWS + X top open secret menu Go to settings Go to Network & Internet Inside click on Network troubleshooter Follow onscreen instructions After the troubleshooter ends reboot your PC

3. Reconfigure IP address

   Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type ncpa.clp and press ENTER Right-click on your network adapter and select properties Uncheck Internet Protocol Version 6 (TCP/IPv6) and click on OK Now press ⊞ WINDOWS + X and click on Command prompt (admin) In command prompt type and after each line press ENTER netsh winsock reset catalog netsh int ip reset reset.log ipconfig /release ipconfig /renew Reboot your computer

4. Restart DHCP client

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type services.msc and click on OK Find DHCP client Right-click on it and choose Restart Reboot PC

5. Reinstall Network Adapter

   Press ⊞ WINDOWS + X to open the windows menu Click on Device Manager Expand Network Adapter and right-click on wireless or ethernet adapter, click on Uninstall device Reboot the computer to automatically reinstall the device driver

6. Reset IP and subnet mask

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type in ncpa.cpl and press OK Right-click on your network adapter and select properties Uncheck Internet Protocol Version 6 (TCP/IPv6) Double click on Internet Protocol Version 4 (TCP/IPv4) Select Use the following IP address and change it to 192.168.0.1 Change Subnet mask to 255.255.255.0 Leave default gateway blank Click OK to save changes

5 Windows 10 Upgrade Errors

The recently released Windows 10 captivated the mass but its rollout, polished as it might have been, proved everything but seamless. Surf the Internet and you’ll get the gist. People are complaining and they need assistance. Assistance with what you might ask? Many have attempted to make an upgrade but failed after encountering various strange combinations of letters and numbers. These are none other than error codes. If you’ve tried and failed, feast your visuals below as you might encounter one of these 5 Windows 10 Upgrade errors.

Error Code 0x80073712

Encountering error code 0x80073712 in no way implies that you need to throw out your computer system and acquire a new one. Not at all! This error code simply means that a very important file to Windows might have gone missing or corrupted. This file is crucial to Windows update so without obtaining this file, you won’t be able to proceed with the update.

Error Code 0x800F0923

Likely, there are many programs and drivers installed on your computer. They all play a vital role. However, if you’ve received error code 0x800F0923, it might be time to consider or turn your eyes to installed drivers on your system. Why? Error code 0x800F0923 means that there’s a driver or driver on your current Operating System that’s not compatible with Windows 10. There’s clearly a dilemma here.

“We couldn't complete the updates. Undoing changes. Don't turn off your computer.” Or “Failure configuring Windows Updates. Reverting changes”

That’s a pretty odd error but I will say it's slick… That Windows 10 upgrade error is straightforward. Microsoft is just letting you know that they won’t be able to complete the update to Windows 10 and so they are putting your computer back to where it was. How nice of them.

The error messages above are pretty generic and will manifest when the upgrade fails for one reason or the other. To resolve this issue, you’ll most definitely have to decipher what error code was presented. Identifying that will provide a glimpse into exactly what steps you need to take.

The Update Isn't Applicable to Your Computer

I don’t know about you but I strongly believe Microsoft is subtly letting you know that your computer system is old and needs to be thrown out. Also, this update could imply that your PC needs to install important updates to rev you up to the requirements. All relevant updates to your computer must be installed before you can get past this stage.

Error… “Something Happened”

This Windows 10 upgrade error has been the talk of the Internet. In fact, users of Windows OS have been making it a mockery. Clearly, not many have had success after encountering this error. Obviously, “something happened” but it’s just not easy to decipher what went wrong. Microsoft is still trying to figure it out.

Solution

One of the most critical processes in the Windows 10 operating system is the Explorer.exe. And there are times when you might encounter an error that says, “System call failed”. You can encounter this error when you try to launch File Explorer, and in such case when the File Explorer does not work, it could cause issues in accessing folders and files on your computer. This kind of error pops up when the explorer.exe system file has become corrupted or if there is some process that interferes with its smooth functioning. To fix this error, you can try to restart the explorer.exe process, run both the System File Checker scan and DISM tool. You could also put your computer in a Clean Boot State or uninstall any programs you’ve installed recently. For more details, follow each one of the given suggestions below.

Option 1 – Try to restart the Explorer.exe process

The first thing you can do is try to restart the Explorer.exe process. To do so, refer to these steps:

• First, right-click on the Taskbar and select the Task Manager.
• Next, expand the Task Manager window to see all the active processes.
• From there, look for the Windows Explorer process, right-click on it and select Restart.
• After that, check if the error is now fixed.

Option 2 – Run System File Checker scan

If restarting the explorer.exe process didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in this command: sfc /SCANFILE=c:windowsexplorer.exe

Note: If you are using a 64-bit Windows operating system, enter the “sfc /SCANFILE=C:WindowsSysWow64explorer.exe” command instead.

• Wait until the process is completed and then restart your computer.

Option 3 – Run the DISM tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “System call failed” 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 problem is now fixed.

Option 4 – Try running the Check Disk 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 c: /f /r
• 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.

Option 5 – Put your computer in a Clean Boot State

As pointed out, there are some instances that some conflicting programs installed in your computer might be the one that triggers the “System call failed” error to appear when you try to open File Explorer. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• 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.)
• Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try to uninstall the programs you’ve installed recently

In case you don’t know, freeware software packages aren’t always free as some of them could contain malicious software that can cause serious damage to your computer. Thus, if you have installed a program recently prior to getting the “System call failed” error, then you have to uninstall that program.

• Tap the Win + R keys to open the Run dialog box.
• Then type “appwiz.cpl” in the field and tap Enter to open the Programs and Features in Control Panel.
• Next, arrange the list of installed programs in the order of the installation date.
• After that, look for the problematic program and right-click on it, and then select Uninstall.
• Once the process is done, restart your computer and see if the error is fixed.

Error Code 0x8024002e - What is it?

Windows 10 error code 0x8024002e is related to the Windows update service. When you see the error code displayed on your screen, it means that the Windows update service has been blocked or not working. As a result of this error code, your computer might lag and the system may freeze while performing normal operations. The error may read as follows:

“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 support for information this may help: (0x8024002e)”.

Common symptoms include:

• Slow computer performance
• System freezes while performing normal operations or freezes while multitasking
• BSOD error is showing
• Some unwanted files get opened automatically
• Updating is not possible

Solution

Error Causes

This error code appears because of the following reasons:

• Incomplete installation of the Windows operating system
• Incorrect registry entry
• Corrupt or damaged system files
• The computer has come under a virus attack
• Miscommunication between the computer and the Windows Automatic Update service

The decline in RAM or outdated Hard Disk Drive

Further Information and Manual Repair

Method 1:

• Remove any external media connected to the computer
• Crash reboot your PC 2 to 3 times.
• Now check if you are still having the problem.

If the problem still persists, try the following methods if you are able to boot to the desktop and check for the problem.

Method 2:

Changing Windows Update property to automatic: You might see this error if your Windows update property is set to manual. Follow the steps below to change it to automatic. Open Task Manager.

1. Click on the Services tab. Find “Open Services” at the bottom of the window.
2. A new window will pop up. Scroll down and find “Windows Update” from the list. Double click on the Windows Update. It will open its properties.
3. Select Automatic for ‘Startup Type.’ Click Apply, Start, and OK.

Now, try the Windows Update and check if you are still getting the error message. If the problem isn’t resolved, reboot your PC for the changes to take effect and then try again.

Method 3:

Disable Antivirus program: If you have any antivirus installed on your PC, you might need to disable it first and see if that helps. Although, most of the antivirus makers have made changes to work smoothly with Windows 10, it is a new Operating System and some antivirus may cause conflict. Disable the antivirus and check for updates to see if it is preventing you from updating your system and displaying the error code 0x8024002e.

Method 4:

Run inbuilt Windows update troubleshooter. Follow the steps given below:

1. Press Windows + W keys on your keyboard to enable the search option.
2. In the Search box type Troubleshooting.
3. Click on View all
4. Click on Windows update and follow the prompts to run the troubleshooter.

If the issue persists, try Method 5

Method 5:

Run the System File Checker tool (sfc.exe):

1. Open Command prompt.
2. Type sfc /scannow and hit Enter.
3. The sfc /scannow will scan all protected system files and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%System32dllcache. The %WinDir% has the Windows Operating System folder. For example, C:\Windows.

Do not close the Command prompt window until the verification is 100% complete. The command prompt will show the scan results when it is done. After it is done, you may receive one of the following messages:

“Windows Resource Protection did not find any integrity violations.” This means you do not have any missing or damaged system files.

OR you may receive a message saying:

“Windows Resource Protection could not perform the requested operation.”

To resolve this problem, run the System File Checker in safe mode and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%WinSxSTemp.

OR you may also receive a message saying, “Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log%WinDir%LogsCBSCBS.log.” OR you may receive a message saying, “Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log%WinDir%LogsCBSCBS.log.”

One of the common causes of Blue Screen of Death or BSOD errors is system driver files due to varying reasons. So if you encounter a Stop error caused by some system driver files such as isapnp.sys, gv3.sys, storahci.sys, or myfault.sys, on your Windows 10 PC, then this post should help you fix the problem. These system driver files are associated with different error codes. The isapnp.sys file is related to the following error codes:

• SYSTEM SERVICE EXCEPTION
• PAGE FAULT IN A NONPAGED AREA
• KERNEL DATA INPAGE
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED.

While the gv3.sys file is related to the following BSOD error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

On the other hand, the storahci.sys file is related to these error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

And the myfault.sys file is associated with this error code: SYSTEM SERVICE EXCEPTION. Although this system driver file causes different kinds of Blue Screen errors, some of their potential fixes are quite the same so you need not carry out tons of troubleshooting steps. But before you troubleshoot the problem, you might want to check out System Restore first, especially if you create a System Restore point from time to time. To perform 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 and boot your computer into Safe Mode.

Option 1 – Use the System Configuration utility

Note that this first fix is only applicable for Blue Screen errors associated with the myfault.sys file.

• In the Cortana Search box, type “MSConfig” and click on the “System Configuration” entry to open it.
• After opening System Configuration, go to the Processes tab.
• Then scroll down and look for the “Digital Line Detection” process and disable it.
• Now restart your computer and check if the Stop error is fixed or not.

Option 2 – Try to update, rollback or disable related device drivers

Incompatible and outdated drivers can also cause computer malfunctioning or crashing as well as Blue Screen errors. To fix that, you can update, roll back or disable the device drivers in your computer.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• After opening the Device Manager, from the list of device drivers, look for the “WIN ISA Bus Driver” if you are facing a Stop error related to the isapnp.sys file. While you have to look for the Sony Recovery CDs PCG-Z1RAP Series device drivers if you face a Stop error concerning the gv3.sys file. For the storahci.sys, on the other hand, look for any outdated drivers and update them.
• To update or roll back or disable these drivers, just right-click on each one of them, and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the Blue Screen error.

Option 3 – Use System File Checker

One of the built-in tools in Windows that you can use to fix Blue Screen errors is the System File Checker. This built-in command utility can help you restore corrupted or missing files as well as replace bad and corrupted system files. Chances are, any of the aforementioned system driver files might be corrupted so to fix them, use System File Checker.

• First, right-click on the Start button and click on the “Command Prompt (Admin) option.
• Next, type in the sfc /scannow command and hit Enter to execute it.

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.

• Now restart your computer.

Option 4 – 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. You can find it in Settings, under the 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.

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.

There are several kinds of errors you could encounter when you are running Windows 10 on a virtual machine. The Windows OS knows the difference between booting up in a standalone computer or in a virtual machine. This is why some specific drivers and system capabilities are used while emulating the Windows OS on software and during this phase, there are times when the System Preparation may throw up an error that says, “A fatal error occurred while trying to sysprep the machine”. This kind of error arises due to a race condition wherein the Sysprep command tries to stop the Microsoft Distributed Transaction Coordinator or MSDTC service and the VMware tool tries to start the MSDTC service. You may also see the following messages logged in the Setuperr.log file:

• [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing ‘C:Windowssystem32msdtcprx.dll,SysPrepDtcCleanup’, returned error code -2146434815[gle=0x000000b7]
• [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2146434815[gle=0x000000b7]
• [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80100101[gle=0x000000b7]

To fix the 0x0f0082, 0x0f0070, 0x0f00a8 Sysprep errors, you can check out two potential fixes. First, you have to check the status of the MSDTC service and the second one is to check the settings in the Windows Registry. Note that these fixes are proven to be effective on many users and apply to several versions of Windows, including Windows 10.

Option 1 – Check the status of the MSDTC service via Command Prompt

As mentioned, the error could be caused by the malfunctioning of the MSDTC service or it. Thus, you have to uninstall and reinstall the MSDTC service to resolve the problem and you can do that using Command Prompt. Follow the steps below.

• In the Start Search, type “command prompt” and from the results, right-click on Command Prompt and then select the “Run as administrator” option to open it with admin privileges.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Once you’ve opened Command Prompt, execute this command: msdtc –uninstall
• The command you just entered will uninstall the MSDTC service. After that, you need to execute this second command to reinstall the service: msdtc –install
• Now exit Command Prompt and check if the error is now fixed.

Option 2 – Check the Registry settings

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and click OK or hit Enter to open the Registry Editor.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
• From there, look for a DWORD value that’s named “SkipRearm” and double click on it.
• Then change its value data to “1”.
• Restart your computer to apply successfully apply the changes made and check if it was able to fix the error.