How to Fix the Socket Error 10060

As you already know, the Windows Sandbox is one of the new features in Windows 10. However, just like other new features, it also throws up errors and one of them is the error that states,

“Windows Sandbox failed to start, Error 0x80070057, The parameter is incorrect”.

This particular error in Windows Sandbox occurs due to its dependence on numerous components of Windows 10 that are related to Hyper-V and Virtualization mainly. To fix this error, there are several options you can check out. You can try to install any pending updates on your Windows 10 computer, as well as make sure that all the services related to Windows Sandbox are enabled.

Option 1 – Try to run the Windows Updates to install pending updates

The first thing you can do to resolve the “Windows Sandbox failed to start, Error 0x80070057” is to check Windows Updates in 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.

Option 2 – Ensure that all the supporting processes and services 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
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Computer Service
  • Container Manager Services
• After you find the aforementioned services, make sure to check if they are enabled or not and then restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

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.

The File Explorer in Windows 10 provides several ways to organize the contents of folders and files in the system. Windows users can utilize some efficient styles to view the contents of the file system as per the user’s requirement. A user may opt to display the file picture in large size thumbnails while the other one could opt to set the icons of folder and files in a small or medium size list. On the other hand, while setting up several styles for the folder and file icons, some Windows 10 users have experienced some unusual issues where there is the Black background showing up behind folder icons. They tried refreshing the File Explorer a couple of times but it didn’t help in fixing the problem and the black squares are still visible on some folder icons. The black squares behind the folder icons might look disturbing though it’s not really a big problem and is merely a graphical glitch that does not cause any damage or whatsoever to the content of the folder and files. The most likely cause of this glitch might have something to do with the corrupted system files or it could also be caused by outdated thumbnail caches. In addition, graphical glitches like this one could also occur if you are using out outdated graphics drivers. To fix this problem, you need to follow the options laid out below.

Option 1 – Try using the Disk Cleanup to remove Thumbnail files

The Disk Cleanup tool is one of the options you can try to fix the black squares behind the folder icons. Through this tool, you can delete all the Thumbnail files on your disk. To use it, refer to these steps:

• Open the Search bar and type “disk cleanup” in the field.
• After opening Disk Cleanup from the search results, then from the drop-down menu select the C: drive to clean up and click OK.
• Wait for the scanning process to complete. Once it’s done, select the files you want to delete.
• Ensure that you select the box labeled “Thumbnails” under the Files to Delete section then click on OK.
• After that, a confirmation box will appear, just click on Delete files to delete the files permanently.
• Restart your PC.

Option 2 – Try resetting the Thumbnail cache

You have the option to manually delete the Thumbnail Cache to resolve the black square background behind the folder icons issue. Follow the steps given below to reset the Thumbnail cache.

• Open the File Explorer.
• Next, navigate to the View tab and select the option with Hidden items to display all the hidden folders and files.
• Next, go to this path: C:Users<username>AppDataLocal
• In the given path, make sure that you put your actual username in the username field. Then look for a file named “IconCache.db”. Right-click on this file and click on Delete.
• After that, go to this path: C:Users<username>AppDataLocalMicrosoftWindowsExplorer
• From there, select all the files and delete them.

Note: If a prompt appears saying, “The files are in use and cannot be deleted”, simply select the “Do this for all current items” option and then click on Try Again. If you get an error message, click on Cancel to close the window and restart your computer.

Option 3 – Try updating or reinstalling the Graphics driver

• Tap the Win + R keys to open the Run dialog box and then type in devmgmt.msc and tap Enter or click OK to open the Device Manager.
• Expand the section for the outdated device drivers.
• And then select the outdated driver(s) and right-click on it/them.
• From the drop-down menu, select the Update Driver option if you wish to update the driver or select the Uninstall device if you want to uninstall the driver and then follow the on-screen instructions to install the latest version of the driver.
• Restart your PC after the installation to allow the system to reinstall the driver.

The latest security vulnerability was discovered inside both Windows 10 and Windows 11 letting any user access admin privileges inside the operating system. This can, of course, be used by a potential attacker to get full control of the system. The problem lies in Microsoft's security rules assigned to the Windows Registry and the Security Account Manager. Both for some reason have reduced restrictions allowing any local user to fully access the files without administrator privileges. The problem is even more amplified if we think about Security Account Manager which includes all account data including the passwords of all users using the same PC. This can provide a potential attacker with all information and let them log on into the administrator account for full control. Microsoft is aware of the matter and is tracking it with code CVE-2021-36934, and includes a complete workaround for the issue, which includes restricting access to  %windir%\system32\config and deleting any restore points or Shadow volumes that were created before that point until the hole is plugged with an official security patch.

Code 39 - What is it?

Code 39 is a device driver error code that pops up when the Windows operating system cannot load the driver for the hardware you want to use.

This hampers your ability to use the hardware properly. The error code is almost always presented in the following format:

“Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.” Code 39

Error Causes

A device driver is a software program that tells the operating system how to control a particular hardware device. Each hardware device has a different driver.

There are separate device drivers for printers, CD-ROM readers, and keyboards, to name a few.

Many device drivers are already built into the operating system. But sometimes you will need to install a new device driver when you want to use a new piece of hardware device that the operating system is not familiar with, or does not anticipate.

Regardless of whether or not the drivers are already integrated into the operating system, you may still experience code 39, typically because of the corrupted or outdated drivers.

Outdated and corrupted drivers cause hardware malfunction and failure, which trigger device driver error codes like code 39. Other causes include incorrect registry values.

Further Information and Manual Repair

Below are some of the easiest and most effective methods to resolve Device Manager error code 39 on your PC.

To follow and implement these methods, you don’t require any technical knowledge or expertise. Simply follow these instructions to fix the error right away.

Method 1 - Fix with a Simple Reboot

There is a possibility that the error code 39 is caused by some fluke within the Device Manager or your BIOS.

If that’s the reason, then a simple PC reboot can resolve the issue immediately. Therefore, before you try anything, it is advisable to restart your system.

If it works, then that is great, but if it doesn’t, then don’t worry, try other methods given below to fix this problem successfully.

Method 2 - Uninstall and Reinstall Drivers

If the error code 39 is generated due to faulty or outdated drivers, then simply uninstall and remove them and then reinstall new driver versions. There are two ways to remove faulty drivers.

Method One

• One is, to go to the start menu, click on Control Panel, and then Add/Remove Programs.
• Remove the program and the driver you think is causing problems. This will thoroughly remove all traces of the faulty driver.
• To reinstall, follow the same steps but this time install the new device driver version.

Method Two

• The other way is to go to the start menu, type Device Manager in the search bar, and then press enter to continue.
• In the Device Manager, find and locate the problematic device.
• After that, double-click the category of device that you wish to uninstall. Let’s say, Windows is unable to load the graphics card driver.
• This means you will have to click on the Display Adapter category in the Device Manager to uninstall the graphics card.
• After you have successfully uninstalled, Windows will prompt you to confirm device removal.
• Simply click OK to confirm and proceed. To activate the changes, restart your PC.
• To reinstall, go to the Device Manager, click on the Action tab and then select the option ‘Scan for Hardware Changes.’

This method, although effective in resolving error code 39,  can be time-consuming. To avoid the hassle and save time, try method 3.

Method 3 - Update Drivers Automatically with DRIVERFIX

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

One of the essential parts of the Windows 10 operating system is the Microsoft Store as it is the distribution hub of numerous applications such as Netflix, Facebook, and many more. In fact, Microsoft is planning to make it a hub not just for UWP applications but also Windows Classic applications. Microsoft has already built a bridge with the power of Project Centennial which allows developers to migrate and upload their Windows Classic applications to the Microsoft Store. Although the Microsoft Store has been constantly improving, there are still times when you might face an error while using it. One of these errors is error 0x80131500. When you encounter this error, you will get the following error message on your screen:

“Try that again, Something happened at our end, Waiting a bit might help, The error code is 0x80131500 in case you need it.”

To fix this error, you can try changing your internet connection, toggle the date & time settings, change DNS, create a new user account, run the Microsoft Store Apps troubleshooter or reset the Microsoft Store as well re-register it using Windows PowerShell.

Option 1 – Try changing your internet connection

The first thing you can do is to change your internet connection. If you are using Ethernet, you can try to connect to a Wi-Fi connection instead and see if it helps.

Option 2 – Try to toggle the Date and Time settings

The first thing you can try is to sync the Date and Time of your computer as the wrong Date and Time settings are one of the most common causes of connection problems like the error 0x80131500. This is because of the incompatibility between the SSL Certificate validation date and the System Clock. Thus, you have to sync your System Clock. Refer to the steps below to do so.

• Start by tapping the Win + I keys to open the Windows Settings.
• Next, go to Time & Language > Date & time.
• From there, turn the toggle on for the “Set time automatically and Set time zone automatically” option on the right-side panel.
• After that, click on Region & language located on the left side panel and make sure that the Country or region on the right-side panel is set to the country you live in.
• Now close the Settings app and restart your computer and see if it fixes the problem or not.

Option 3 – Try to change the DNS Server

In this option, you can try changing your current DNS settings to the Google Public DNS as it could also help in fixing error 0x80131500. To do so, follow the steps below.

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

Option 4 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if the error is fixed or not. Note that you have to sign in with your main account before you can create an admin account.

Option 5 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x80131500. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 6 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 7 – Try to re-register the Microsoft Store app via PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

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

Google's Pixel smartphone is one if not the best Android smartphone on the market. It regularly gets updates and Google is really trying to keep it as a top choice for Android smartphone users. One of the new things that Google has released for its smartphone series is a new emergency dialer.

With an emergency dialer, you will be able to quickly access local contact information for police, fire, and medical services. This dialer is able to contact before mentioned services even when the phone is locked and when you are traveling.

The idea is to quickly access the default emergency number no matter in which country you are currently in, service will find the appropriate number and set it as default so if you need it there is no delay in searching for the appropriate number and dialing it.

Once the service is enabled on the device you can swipe up and tap Emergency call without unlocking your phone or you can press and hold the power button for five seconds and tap Emergency.

If you have a Pixel smartphone go to the Google support page and follow instructions on how to enable this service. It costs nothing and it could potentially even save your life.

What is Active History? A new feature has been introduced in Windows 10 that allows users to stay connected to their tasks across their devices. This new feature is called “Windows Timeline” and using this feature, users could continue their tasks all over their Windows 10 computers as well as on devices that run Android and iOS as well. This new feature was included in Microsoft Launcher and Microsoft Edge on Android devices as well as in Microsoft Edge for iOS devices. In order for the feature to work, you have to send either Basic or Full data and diagnostics of your computer to Microsoft which would sync it all over your devices with the help of the cloud. And now since all your data is stored on your Windows 10 computer and with Microsoft under your account, it is easier for you to access the back and start where you left off. This kind of option is called Active History. In this post, you will be guided on how you can permanently disable Active History using either the Windows Registry or Group Policy. Before you go on further, it is recommended that you create a System Restore Point first in case anything goes wrong. This is a precautionary measure you must take so that you can easily undo the changes you’ve made. After creating a System Restore Point, proceed to the given instructions below.

Option 1 – Disable Active History via Registry Editor

• Tap the Win + R keys to open the Run dialog box and type in “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSystem
• From there, check if you can find a DWORD named “PublishUserActivities”. If you can’t find this DWORD, just create one with the same name and make sure that the base is selected to Hexadecimal.
• After that, double-click on the DWORD and change its value from 1 to 0 to disable Active History.
• Restart your computer to apply the changes you’ve made successfully.

Option 2 – Disable Active History via Group Policy Editor

Note that this second option won’t work if you are using the Home edition of Windows 10. This is because the Group Policy Editor does not come with Windows 10 Home. So if you are not using Windows 10 Home, follow the given steps below.

• Tap the Win + R keys to open the Run box.
• Then type in “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer ConfigurationAdministrative TemplatesSystemOS Policies
• After that, double click on the configuration listing named “Allow publishing of User Activities” to open the configuration page which has the following description:

“This policy setting determines whether User Activities can be published. If you enable this policy setting, activities of type User Activity are allowed to be published. If you disable this policy setting, activities of type User Activity are not allowed to be published. Policy change takes effect immediately.”

• Now you have to select Disabled or Not Configured if you want to disable Publishing of User Activities or Enabled to Enable Publishing of User Activities depending on your preferences.
• Next, click OK and exit the Group Policy Editor and then restart your computer to successfully apply the changes made.

When you encounter an error message that says, Chassis Intruded…Fatal Error…System Halted on your monitor then it indicates that the Chassis or the cabinet that holds the CPU, GPU, motherboard, and many more is open. It is a security feature offered by OEMs wherein a connector that is found in the motherboard can detect if the chassis component has been replaced or removed. There are a few OEMs that offer onboard speaker or PC chassis speaker which goes off in this kind of situation. Obviously, the problem has something to do with the hardware and in most cases, you have to put the jumper back on the motherboard with the pin-labeled chassis signal and ground. There are times when some OEMs offer a simple switch that is armed automatically when you properly close the chassis. Thus, you need to check if this switch has something to do with the error. If there is no switch or if it doesn’t resolve the issue, although you may be able to get into Windows with a warm boot, the normal Windows boot won’t really work unless you fix the problem. It is rather false positive and has something to do with the RTC RAM state or the BIOS. You might need to completely disable the Chassis intrusion feature to fix the error. Refer to the suggestions given below to try and fix the “Chassis Intruded, Fatal Error … System Halted” error.

Option 1 – Try to clear CMOS

You can easily clear CMOS by shorting two pins which can be found side by side on the motherboard. Keep in mind that it may vary from OEM to OEM although the basics are still the same to clear CMOS. In addition, you might also have to download the manual from the OEM’s website so that you’ll know its exact location.

Option 2 – Try booting into the BIOS

You can also try booting into the BIOS. All you have to do is tap either the DEL or F2 keys to get there. Note that everything will be set back to their default setting after you reset the CMOS.

Option 3 – Try disabling Chassis intrusion

In this option, you have to look for the Chassis intrusion feature in your BIOS. It might be located under security. From there, disable it and check if the problem’s fixed.

Option 4 – Try to reconfigure the BIOS

Once you have disabled the Chassis feature, you need to reconfigure the BIOS the way you expect it to be or to what it was before the reset.

Stumbling upon downloader.dll not found error is not pleasant to experience, usually, it means that desired application can not be started. There could be several reasons why this error happens from user mistakes, corrupted files, bad installation, and even bad RAM memory. Whatever the reason might be solutions provided are the same for all and offer a fix to this issue. it is advisable to follow provided solutions from start to finish not skipping any one of them since they are tailored to address the simplest solutions and issues and move toward more complicated ones.

1. Reinstall application

   If you are receiving Downloader.dll not found when trying to run just a single certain application, reinstall the application, there is the possibility that the application has somehow corrupted downloader.dll during the installation process. Reinstalling might fix the problem.

2. Run SFC scan

   SFC scan is the tool meant to scan all files and fix any corrupted ones. To run this tool, open the command prompt in administrator mode by right-clicking on the windows start button and then left-clicking on the command prompt (admin). When you are in command prompt type in SFC /scannow and let the whole process finish.

3. Update device driver

   If previous steps have not provided results, go to device manager and visually check is there a device with an exclamation or other sign next to it, if there is, right-click on it and choose update driver.