Capture screen with Windows 10

In case you don’t know, Windows 10 comes with a native ability to project to another screen, be it wireless or wired. All it takes to do that is by tapping the Win + P key combination to display options to manage the extended display. However, there are times when you might encounter errors when you do that like the “Your PC can’t project to another screen” error. This kind of error stops you from projecting your computer to the other screen. Here’s the full content of the error message:

“Your PC can’t project to another screen, Try reinstalling the driver or using a different video card.”

This error could be due to loosely connected hardware or the display adapter. It is also possible that a recent Windows Update has messed up its settings. To resolve this issue, you can try several suggestions that will be given in this post. You can try to check the hardware cable connections or run the Hardware and Devices troubleshooter. You could also update or reinstall the display adapters or replace the graphics card.

Option 1 – Try checking the hardware connections

The first thing you have to do before you further troubleshoot the problem is to check the hardware connections of your computer and see if there are damaged ones, just like with the ports as it would also affect the overall connectivity of the device with the computer. You also have to make sure that no pin is missing from the ports. So if you notice some irregularities in the connecting cable physically, you might have to buy another one and replace it and then see if it fixes the problem or not.

Option 2 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Try to update or reinstall the display adapters

You might also want to update the drivers for Display adapters and Monitors or you might also have to update or reinstall your NVIDIA driver if you’re using one. To update or reinstall the display adapters, follow these steps:

• Tap the Win + R keys to open the Run dialog box and then type in MSC and tap Enter or click OK to open the Device Manager.
• Expand the section for Display Adapters.
• And then select the Display Driver and right-click on it.
• From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the Display Driver.
• Restart your PC after the installation.

If you find that updating the drivers does not help, you can try to reinstall them. How? Simply follow the steps below.

• Tap the Win + X keys and select the Device Manager.
• After that, look for the affected driver in the Device Manager window. And if you see a yellow exclamation mark beside it, right-click on it and select the option “Rollback” to roll back the driver.
• And if the Rollback option is not available, just select Uninstall and then restart your PC.
• Finally, open the Devices Manager once again and select the option “Scan for hardware changes” to install the driver.

Option 4 – Consider replacing the graphics card

You might also want to consider replacing the graphics card of your computer to resolve the problem if the options provided above didn’t work.

As of late, users have been reporting about getting an error saying, SAFE_OS phase error during Replicate_OC operation when they tried to upgrade their Windows 7 or Windows 8.1 computers to Windows 10. Although the error code in this problem could vary, in this situation, it states:

0xC1900101 – 0x20017, The installation failed in the SAFE_OS phase error during Replicate_OC operation

To fix this issue, you need to follow the given options below. But before you do, you need to create a System Restore point first so that if anything goes wrong, you can always undo the changes you’ve made.

Option 1 – Try to change the Windows 10 installation

According to security experts, one of the main causes of this error is the KB3064209Windows Update. This particular update is the one responsible for updating the CPU Microcode for processors made by Intel. Thus, if you don’t use an Intel processor, you can skip this option and proceed to the next one. However, if you use Intel, make sure to follow the instructions in this option carefully. Take note that in this solution, C: partition is referred to as the OS Partition while H: partition is referred to as the USB Pen Drive.

• First, you need to download the Windows 10 ISO from the Windows 10 Media Creation tool and then copy its contents to the Pen Drive H.
• Next, tap the Win + X keys and click on the Command Prompt (Admin0 option. If a User Account Control appears, simply click Yes.
• After opening Command Prompt, type the following command:

dism /Mount-Image /ImageFile:H:sourcesboot.wim /index:1 /MountDir:C:UsersUserDesktopmount

• Now navigate to the following path in the Windows File Explorer:

C:UsersUserDesktopmountWindowsSystem32mcupdate_GenuineIntel.dll

• From there, right-click on the file named “mcupdate_GenuineIntel.dll and click on Properties.
• Next, go to the Security tab and click on Advanced. In the Advanced section, change the Owner to your User Account and click OK.
• And then back to the Security tab, click on the Edit button and check on Full control to make sure that your User Account has all the privileges.
• Now click on Apply and then OK.
• After that, delete the file you saw earlier which is named mcupdate_Genuine.dll.
• Then close all the Windows File Explorer instances and go back to the Command Prompt window and unmounts the image you mounted before by typing the following command:

dism /Unmount-Image /MountDir:C:UsersUserDesktopmount /commit

• Afterward, repeat the steps from mounting up until here for these files:
  • wim /index:2
  • wim /index:1
  • wim /index:2
• Now delete the mount folder and remove the USB Pen Drive and then boot with the installer.

Option 2 – Try to perform a Disk Cleanup

Chances are, some unnecessary files in your computer might be interrupting the installation process which explains why you’re getting SAFE_OS phase error during Replicate_OC operation instead so you need to perform a Disk Cleanup in order to fix the problem.

Option 3 – Try updating all your drivers

Every now and then, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the SAFE_OS phase error during the Replicate_OC operation. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 4 – Try to update your system’s BIOS

Aside from outdated drivers, outdated BIOS could also be the reason why you’re getting the SAFE_OS phase error during Replicate_OC operation which is why you need to update your system’s BIOS in order to resolve the issue.

Option 5 – Try checking the Windows Services status

• In the Cortana search box, search for “Services” and then click on the Services icon.
• After that, the Services utility will be opened in a new window.
• Next, look for the following services:
  • BITS (Background Intelligent Transfer Service)
  • Windows Update Service
  • Cryptographic Service
• Then right-click on each one of the services and click on Properties. From there, select Automatic from the drop-down of the Startup Type menu.
• Now click on OK for each one of them and restart your PC to apply the changes made.

Option 6 – Try to check the RAM modules

There are many times when all the components of the RAM weren’t able to be used by the computer so you need to check the RAM modules.

• You need to first turn off your PC and then take out your RAM physically.
• Next, clean it with a soft cloth and blow some air into the RAM slot in the motherboard.
• After that, put your RAM back in the same slot.
• Then try updating your computer system again.

If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.

Option 1 – Try to rollback, update, or disable the Graphics card drivers

Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Run System File Checker at boot time

• Once you get to the Welcome Screen part, click on Next.
• Afterward, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
• Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. It can be found in 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.
• After that, 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 5 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.

Option 6 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:

• Tap the Win + R keys to launch the Run dialog box.
• Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
• Now click on the entries of every faulty driver and click on the Uninstall option.
• Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

When you receive Error 0x800704C8 when trying to move a file inside Windows 10 operation is stopped and it can not continue leaving you with the file in its original location without a copy. Several issues can be the cause of this type of behavior and error and after some digging and analyzing we are bringing you various solutions for this error and how to fix it.

Ownership issues

It turns out that not having ownership of fie can cause this error and prevent you from copying it. For some reason, Windows can assume that file is owned or used by another application or process and thus prevents you from making a copy since you do not have ownership of it. Resolving this particular issue will require you to install a third-party application that is tailored for this kind of task. After some talk and research, we found out that there is a freeware application that can solve this issue quite fastly. Unlocker is the name and the download link is here. Once downloaded, install it and run it. Once inside the application browse to the location where you need to change the ownership, click on it to select it, and click OK. Use the No Action drop drown menu to select Move, then click OK

Antivirus Issue

As with other file and application issues, this error could also be a product of antivirus marking it inaccessible to Windows and thus preventing copy or move operation on it. note: Do not turn off Windows defender since it was proven that it is not the cause of this kind of error, so if you are using only Windows defender you can skip this solution. How temporary turning off each security suite is different and it depends on the application itself we can not cover in detail the procedure here. Go to your security suite manufacturer's website and get information there or if you want, go directly to applications and features inside Windows and uninstall the software.

Visual Studio issue

• If the file you are trying to move is part of a Visual Studio project then the issue can be linked directly to Visual Studio itself, luckily the solution is quite easy. All you have to do it to exit Visual Studio and then run it with administrator privileges.
• In order to run Visual Studio with elevated privileges locate its executable file and right-click on it.
• Choose properties and go to the compatibility tab
• Inside compatibility tab check box that says run this program as an administrator

Corrupted system files

If the previous solutions have not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system file issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

If you are trying to install a Windows 10 upgrade but was interrupted with an error saying, “0x80070003 – 0x2000D, The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation”, then you’ve come to the right place as this post will help you sort this problem out. When you get this kind of error while trying to upgrade your computer, although there could be various reasons for this, the primary one is that when you upgrade from one update to another, something stopped the upgrade process to migrate the user data. To fix this error, you can try to run both the DISM tool and the System File Checker to automatically repair any corrupted system files. You could also try checking the free storage space of your primary drive and if you have any file lock apps like BitLocker, consider disabling them for they could also be the reason why you’re getting the error.

Option 1 – Run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10 which might be the reason behind the Windows Upgrade error 0x80070003 – 0x2000D. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.
• Once it’s done, restart your computer and then check if the issue is resolved or not on the next startup.

Option 2 – Run the SFC scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Windows Upgrade error to appear. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

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.

• Reboot your PC.

Option 3 – Try checking the free storage space on your primary drive

The next option you can try to resolve the error is to see if you have enough free storage space on the primary drive because if you don’t then it’s probably the reason why you’re getting this error. To fix it, you need to free up some storage space by following these steps:

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• System created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again.

Option 4 – Try disabling BitLocker and other file lock apps

If you are using BitLocker or other file lock apps, then it could be the reason why you’re getting the error. Usually, file lock apps don’t cause any kind of issue, however, if you have something that works on file level like BitLocker, you can try to disable it. Once you’ve disabled it, try to install the Windows 10 Upgrade again and after you do, enable BitLocker again. This should fix the problem.

What is TrayApp Error 1706? A TrayApp Error 1706 is not something you want to see. It is generally caused by an error in hexadecimal formatting, which is a common format employed by software programmers for Windows OS-compatible hardware drivers, Windows system files, and software apps. Developers and manufacturers of hardware drivers and software apps employ different codes in order to indicate different types of errors. The TrayApp error 1706 occurs in a long numeric code with a technical explanation of the cause. In many cases, the TrayApp error 1706 can have different TrayApp error 1706 parameters. It will usually sport a message like:

• Install Error 1706 Trayapp
• Reinstall Error 1706 Trayapp
• Error 1706 Trayapp crash
• Error 1706 Trayapp is missing
• Remove Error 1706 Trayapp
• Download Error 1706 Trayapp
• Error 1706 Trayapp virus

Solution

Error Causes

More often than not, the TrayApp error will occur because there are damaged files in your operating system. When the Windows system file entry gets corrupt, it means that there malfunctioning in your system and it can be exposed to major security threats. And if it’s not resolved, it can potentially result in complete and permanent data loss and can make your storage media or your system as a whole inoperable. There can be other triggers for the TrayApp error, the common of which include:

• Incomplete installation of software
• Incomplete un-installation of software
• Improper deleting of hardware drivers
• Improper deleting of software applications

If you have the TrayApp error, you realize how common it is when restarting your system followed an improper shutdown or a recent malware or virus recovery. These situations result in corruption or deletion of essential system files. When Windows system files get corrupted or go missing, the data that is needed to run software won’t be linked properly.

Further Information and Manual Repair

There are two common manual ways of fixing TrayApp error 1706. The manual solution is:

Boot Your System and Log in As Administrator.

• Click on Start and select All Programs.
• Go to Accessories, then System Tools, and select System Restore.
• In the dialog box, select, ‘Restore computer to an earlier date’ and then click on Next.

Click next twice on the dialog boxes and then the Automatic System Restore will start and restart your device.

Reimage Plus Fix for Trayapp Error 1706

This is the easiest way to resolve TrayApp Error 1706. However, there are cases when the manual process may not really work, and this can be caused by improper maintenance of your system. For that, Restoro is your short and comprehensive answer. Restoro is a multi-functional PC Fixer that works as an antivirus, registry cleaner, system optimizer, and much more. It can not only help resolve TrayApp Error 1706, but can also resolve other errors that can hinder the performance of your system, programs, and applications. It can also clean your registry and optimize your system to make it faster and quick loading. The software is compatible with all Windows versions. Just click here and download Restoro and get rid of any issues in your system!

Valve has officially announced that Steam Deck will be compatible with Windows 11 despite TPM 2.0 Microsoft requirements. From the beginning, Deck was announced like a mini handheld PC device. Powered with new Steam OS 3.0 based on Linux. However, besides out-of-the-box OS it was also stated that Deck will be a personal device meaning that other PC-based operating systems could be installed on it and even run your typical applications in it. Since Microsoft announced Windows 11 hardware requirements, specifically the TPM 2.0 requirement many users voiced concern that Steam Deck will not be able to connect to Windows 11 TPM 2.0 is something that Microsoft requires for every internal and hardware component that is to connect on a Windows 11 device. This is to ensure that only trusted devices would be included in the array of a PC setup and avoid any problems like malicious hardware injecting software into a system. This would also minimize the compromise Windows would have, as unverified or untrusted devices connect to a Windows PC. However, Valve and AMD are ensuring us that Deck will not have any issue connecting to a PC running Windows 11 or even if you wish to transform Deck itself into a Device running Windows 11.

Updating your Windows 10 computer does not always go smoothly as there are some errors you can encounter along the way. One of these Windows Update errors is the error code of 0x80246008. This kind of error can occur during different phases of an update that’s being downloaded or installed and even when an update is being initialized. If you narrow down the cause of this Windows Update error, you’ll most likely see that it is related to the deliverability of a file to a computer from the servers of Microsoft. In other words, the error might be due to conflicts from programs like Firewall as well as third party programs like Antivirus or it could also be due to corrupted disk image or system files or it could be that any of the supporting Windows Update components and services are not working properly. Whatever the cause may be, the potential fixes provided in this post can be applicable to Windows Updates as well as the Microsoft Store. Refer to the suggestions provided below to resolve the Windows Update Error 0x80246008 but before you proceed, make sure that you create a System Restore point first.

Option 1 – Apply some tweak in the Windows Registry from Command Prompt

• Tap the Win + X keys and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• Next, navigate to the root location of the bootable device inside the Command Prompt command line.
• Once you’re in the root location, type the following command and tap Enter to execute it:

reg add HKLMSYSTEMCurrentControlSetControlBackupRestoreFilesNotToBackup

• After that, close the Command Prompt command line and then tap the Win + R keys to open Run utility.
• In the field, type “services.msc” and click OK or tap Enter to open the Windows Services Manager.
• From there, look for the following services:
  • Windows Update – Manual (Triggered)
  • Background Intelligent Transfer Service – Manual
• Now open their Properties and make sure that their Startup type is as mentioned above and that they are running. If they are not running, just click on the Start button.

Option 2 – Run the System File Checker Scan

If the registry tweak didn’t work, you can run a System File Checker scan instead. It is a built-in command-line utility that replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you try updating your computer. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer.

Option 3 – Run the Windows Update Troubleshooter

If the System File Checker wasn’t able to resolve the Windows Update error, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including this one. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to disable your antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 5 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Error Code 12 - What is it?

Error code 12 is a typical Device Manager error code. It usually pops on the computer screen when the computer experiences device driver problems or system resource conflicts.

Error code 12 is mostly displayed on the computer screen in the following format:

‘This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system.’

Solution

Error Causes

The error code 12 occurs when 2 devices installed on your PC are accidentally assigned the same I/O (input/output) ports or the same direct memory access channel.

This assignment is known to be made either by BIOS (Basic Input/output system) or by the operating system. It can sometimes be assigned by a combination of the two. Also, code 12 can also appear on your monitor screen if the BIOS didn’t allocate enough resources to the device.

Although this error code is not fatal, it is nonetheless advisable to fix it immediately to avoid inconvenience and hassle. This error is most likely to lower and hamper the performance of your system.

Further Information and Manual Repair

Here are some of the easiest and most effective do-it-yourself methods to resolve error code 12 on your PC. To perform these fixes, you don’t have to be technically sound or a computer programmer for that matter. Simply follow the steps to fix the problem right away.

Method 1 - Use the Troubleshooting Wizard to identify the Conflict

To repair error code 12, simply go to the start menu and type Device Manager in the search box. Now go to the Device Properties dialog box. After that click on the ‘General Tab’ and now access Troubleshoot to start the Troubleshooting Wizard.

The Wizard will ask you some questions and provide you a solution accordingly. Follow the instructions and resolution steps provided by the troubleshooting wizard to repair error code 12 on your PC.

Method 2 - Disable the Device to Resolve

By disabling the problematic device in the Device Manager, Windows will ignore that piece of hardware. Once disabled, Windows will then no longer assign system resources to that device and no driver/software will be able to use that device.

To disable, go to the Device Properties in the Device Manager and then click the Driver tab. Click disable located at the bottom of the window. Then you will be prompted with a message stating ‘Disabling this device will cause it to stop functioning. Do you wish to disable it?’ Click yes to continue and then click OK to save changes.

Method 3 - Restore Your PC to its Previous State

Another method to resolve error code 12 is to restore your PC to its previous state when it was working properly.

For this, it is important to backup all your data first to avoid data loss issues that are likely to occur during this process. Creating backups manually can be a time-consuming and tedious task. To save time and quicken the process, it is best to install a program like DriverFIX.

DriverFIX is a user-friendly and intuitive device driver management software that helps backup all your data automatically and efficiently, while simultaneously restores your PC back to its previous state before you encountered problems.

Click here to download DriverFIX on your system to resolve error code 12

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.