Fix Chrome ERR_SOCKET_NOT_CONNECTED

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

TPM or Trusted Platform Module version 2.0 is a must-have if you plan on upgrading your system to Windows 11. So what exactly is TPM and do you have it?

What exactly is TPM?

TPM is a tamper-resistant hardware technology tasked with generating and storing encryption keys inside it for better PC security. It can be remotely used to authenticate hardware and software by utilizing a unique endorsement key placed into the hardware itself. This technology can be used for example in BitLocker inside Windows in order to have data on a hard drive encrypted so if the mentioned drive is connected to another computer it would not be able to be accessed since the encryption key is stored in the TPM module. Microsoft is pushing its agenda that Windows 11 must be and must feel like safety first OS which will protect user data and user information and requiring TPM means that each Windows 11 will be secure so no additional software patches will be required for an extra layer of security. Windows 11 will assume that each user has TPM encryption enabled and will be built upon that.

Do you have TPM on your computer?

If your computer or hardware has been purchased in 2016 or later there are very high chances that you already have the required technology to run Windows 11. Unfortunately, many gaming motherboards have not been placing TPM in their boards and you might not have it. Also, there is the option of you having it but it is turned off in motherboard settings making Windows unable to detect it. As you can clearly see there are a lot of scenarios around required tech and honestly it is a complete mess. But lucky for you there are ways to find out do you possess the needed module in order to make an upgrade. On your current computer on which you would like to make an upgrade in your current Windows OS press ⊞ WINDOWS + R to open the run dialog. Inside run dialog type in TPM.msc and press ENTER to open Trusted Platform Module Management on Local Computer. You will immediately receive information do you have the required module. If everything is fine, you are good to go, however, if it says that compatible TPM cannot be found there is a chance that either you do not have needed hardware or it might be turned off inside motherboard settings.

Check motherboard UEFI

If you have a newer motherboard but Windows utility cannot detect TPM there is a chance that it might be turned off directly on your board. In order to check this, you will have to boot up your PC into UEFI either by pressing the corresponding key when it is turned ON or from Windows reboot options. Once you are inside UEFI you need to find security options and see if there is an option to turn ON or enable TPM. Since every motherboard is different and has different UEFI software we cannot cover all of the permutations and the best we can do is hope that provided information is enough. You can also visit your motherboard manufacturer to see instructions for your specific case.

Conclusion

TPM itself is generally an OK idea and I can surely see good sides of it but there is this lurking feeling that generally, Microsoft is not really concerned about the security of our data and that the real requirement for this is trying to battle software piracy. I simply cannot trust company which introduced tons of telemetry tracking through ages and which has done everything in their power to battle non-legal use of their software. I do not promote piracy but I support free choice and besides, who can tell me what will happen if TPM malfunctions, will I lose all of my data forever? It is not so uncommon that TPM has malfunctioned in the past and it is only logical to presume it can do it again in the future but this time we will not have the choice not to use it, we will be forced into it.

Spring is almost here and with spring comes work, nature wakes up, people wake up, no more heating bills, time to start working, and time to start cleaning your PC. Good day everyone and welcome to another tip & trick for your PC. This time we are talking about cleaning your PC and keeping it up to software tight so you are ready for the upcoming spring season. Thank you for being with us and let's start:

Uninstall applications that you are not using

The unused applications can cause many issues for PC, from taking unnecessary disk space to even causing slower boot times if they have active services that require to be all-time up and running. They could slow down other applications like file explorer if they have extensions installed into them and can take RAM space with their background processes. If you are not using a particular application anymore or do not plan to use it soon it is always best practice to delete it from the system and thus removing all services and processes that go with it freeing so much-needed RAM and disc space.

Remove browser extensions you do not need

Browser extensions like applications can cause some issues with PC performance. if you spend a lot of time on the internet browser extensions can slow down browser and page loadings, they can make browsers take up more RAM memory and if they are outdated they could even present a serious security threat. Best practices are to keep only the extensions that you need all time, maybe some password managers or similar, extensions that you use on a daily basis, the rest should be uninstalled.

Remove things from the startup

Many services are booted along with Windows itself, some of them are crucial to the system even working, some not so. By eliminating not-needed services from the startup menu you will make sure that your boot times and overall performance of the system are in healthy form and that your PC is more responsive.

Organize files, folders, and desktop

The speeding of computer is not the only thing that you need to take care of, in order to be prepared and have maximum efficiency you will need to organize your files and folders as well. In a working environment, we often tend to save and place files all over the place, and in time they clog up desktop and hard drives. If the files are not well organized we will lose precious time trying to find anything that we need and require, so instead of wasting your time in locating files, why not organize them for easy and logical search so you can access them easily when needed.

Clean taskbar and start menu

Taskbar and start menu as well can be clogged with icons and non-organized application shortcuts and document shortcuts. Remove everything you do not need for that tidy and easily accessible access.

Sort bookmarks

It is very likely that you have plenty of bookmarks saved in our browser. It is also very likely that these bookmarks are not sorted and organized and now would be a great time to do it. Like files bookmarks also can cause you a lot of time loss if you need to find a specific one in a sea of many.

Run disc cleanup

Built-in disc cleanup utility will find temporary files, unused ones, and plenty of other junk on your hard drive. Now would be a great time to run it and get rid of junk files from your system.

Physically clean your computer

Now when we have taken care of the software part of our computer and system, it is time to clean up the computer itself. Unplug your computer and clean it, we will not go into details of this procedure, there is already an article on our site which deals with this part in detail so look it up if you need assistance with this part.

Clean your peripherals

Besides the computer for effective and pleasant work take care of your screen, keyboard, mouse, printer, etc. All of these devices need to be dust-free and clean if you expect them to behave on top of their game. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

There are times when it is really inevitable to delete your hard drive partitions especially if you are already running low on disk space in your Windows 10 computer. Users typically delete the volume which is not being used in such cases in order to free up some space for the volume that’s running low on disk space. To resolve the problem, users tend to use the Disk Management utility to delete hard drive partitions. However, some users reported that the “Delete volume” option is not available as it is grayed out. Thus, users aren’t able to delete hard drive partitions and aren’t able to free up disk space. This kind of problem usually occurs when there is a Page file on the volume that you are trying to delete and so on. Oftentimes, this issue is mistaken for the problem where you are unable to delete an EFI-protected partition. However, in this case, not only you are unable to delete EFI-protected partition but also NTFS file systems. This is really hard to deal with but worries not for there are some potential fixes you can check out to resolve this problem.

Option 1 – Try to manage the Page file in the Partition

As mentioned earlier, if a Page file exists in a partition, you won’t be able to delete it. The page file is what stores your data when the system’s random access memory fills up. To resolve this, follow these steps:

• Go to the Start menu and type “View advanced system settings” in the field and open it from the search results.
• Next, click on Settings in the Advanced tab.
• On the new window that pops up, go to the Advanced tab and select Change.
• Next, uncheck the checkbox of “Automatically manage paging file size for all drives” and highlight the drive you want to delete.
• Then select “No paging file” and click on Set.
• Now click on the Apply and OK buttons on all the windows and restart your computer.

Option 2 – Delete storage partition via Command Prompt

• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also type in “cmd” in the Cortana search box and right-click on the Command Prompt icon and then select the “Run as Administrator” option from the context menu.
• Once you have Command Prompt pulled up as admin, type in and enter this command – diskpart
• After entering this command, the Diskpart Utility will start. Diskpart Utility is a command-line-based utility just like Command Prompt but it will get a UAC Prompt after you invoke it so you have to click Yes for the UAC Prompt.
• After that, type in list volume and tap Enter to see the list of all the partitions created on your PC. This includes both types of partitions that are visible to the normal users in the File Explorer as well as the ones that are created by Windows 10 by default which helps it in storing the boot files and other essential system files.
• You should see a list of all the partitions made on your computer. Select the partition you want to delete by its Unique Identification number as Volume X where X denotes the Unique Identification Number.
• Next, type in the select volume number command and hit Enter to select the desired volume.
• Then delete the volume you’ve selected and type in the delete volume command and hit Enter to delete the volume you just selected and convert it into unallocated space.

Option 3 – Delete storage partition via Windows PowerShell

• Start by tapping the Win + X keys or simply right click on the Start button and select Windows PowerShell (Admin) or you could also type in “Windows PowerShell” in the Cortana search box and right-click on the Windows PowerShell icon and select the “Run as administrator” option.
• Once you’ve opened the Windows PowerShell, type in the Get-Volume command and hit Enter to get a list of all the partitions on your PC.
• Next, select the drive letter you want to delete and then type in the Remove-Partition –DriveLetter command and hit Enter to delete the selected partition. Note that you need to replace the drive letter with the letter of the partition you want to get rid of.
• After that, it will ask you for confirmation. Just hit the Y key for Yes or hit the A key to say Yes to All. This will delete all the partition you’ve selected and will move them in as unallocated space.

Corefoundation.dll Error - What is it?

Corefoundation.dll error is a DLL error code associated with Apple software such as iTunes, MobileMe, QuickTime and etc. To understand this error better, first you need to understand what corefoundation.dll file is. Corefoundation.dll is a Dynamic Link Library file that is used by Apple software products. This file is created by Apple computer Inc and is designed to help open up some of the media files that you might have on your PC. DLLs help promote modularization of code, efficient memory usage, code reuse and reduced disk space allowing the operating system and the programs to load and run faster and take less disk space on the computer.

Error Messages

This error pops on the screen when there is an issue related to Apple software products on your system. Corefoundation.dll error is displayed on the computer screen in any one of the following formats:

“The program can not start because corefoundation.dll is missing from your computer. Try reinstalling the program to fix this problem”. "This application has failed to start because CoreFoundation.dll was not found. Re-installing the application may fix this problem." “The procedure entry point_CFBundleCopyFileTypeForFileData could not be located in the dynamic link library corefoundation.dll.” "MobileMe Control Panel cannot continue as Apple Application Support is missing or outdated. Please uninstall and reinstall the latest version of iTunes and MobileMe Control Panel to fix this issue.”

Though this error code is not fatal but if it is not fixed immediately it will hamper your ability to load and run Apple programs on your system.

Solution

Error Causes

Corefoundation.dll error can be triggered due to several reasons. Here are some of the most common corefoundation.dll error causes:

• Outdated PC drivers
• Viral infection
• Damaged Windows registry files
• Corrupted corefoundation.dll file
• Missing corefoundation.dll file
• Incorrectly installed third-party software

Further Information and Manual Repair

To fix this issue on your computer here are some of the best, easy and quick do it yourself methods that you can try:

Method 1: Download the Original Corefoundation.dll File

If the underlying reason for corefoundation.dll error is file corruption or it goes missing, then the best way to resolve is to download the original corefoundation.dll file. Once you download it, paste it to its exact location. DLL files are normally located in the following location C:\Windows\System32. Once you paste it, register the file by typing ‘regsvr corefoundation.dll’ at the command prompt. When the process is complete, restart your PC to activate changes. Alternatively, you can uninstall and re-install any Apple Software you may have on your Windows Computer. To do that, Open the Control Panel, navigate to "Install/Uninstall a Program", search for Apple software, and uninstall them.

Method 2: Update Window Drivers

If the error code is related to outdated drivers, then it is recommended that you update them promptly to resolve the corefoundation.dll error on your PC. This can be done by using a driver update wizard from within Device Manager. The driver update wizard walks you through the entire drive update process, making updating a hassle-free process.

Method 3: Download Restoro

If the error still persists, then try method 3. Sometimes the cause of corefoundation.dll can be viral infection or registry issues.  Viruses may enter your PC unknowingly through phishing emails and downloads which can corrupt and damage your dll files. Also, if you don’t clean your registry frequently, unnecessary and obsolete files may accumulate in the registry like cookies, junk files, internet history and temporary files. These files take up a lot of disk space corrupt DLL files and lead to disk fragmentation. Regardless of what the issue is, Restoro is your one-stop PC Fixer. It is a multi-functional and user-friendly repair tool embedded with 6 different scanners including a registry cleaner and an antivirus. It scans and removes all types of viruses and cleans and restores the registry too. Click here to download Restoro and resolve the corefoundation.dll error today!

A lot of users lately reported getting an error that says, “The application has failed to start because its side-by-side configuration is incorrect”. This kind of error can pop up when you try to open a number of programs, regardless of their origin, the developer, and compatibility. Here’s the full context of the error message:

“<PATH OF THE EXECUTABLE FILE>, This application has failed to start because its side-by0side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail”.

This kind of problem has something to do with the C++ runtime package in the background. It could also be related to an error for a registry value. Whatever the cause is, you can fix this error with the help of some suggestions provided in this post. You can try to reinstall the application or check the registry setting or reinstall the suitable Visual C++ Runtimes or re-enable the Microsoft .NET Framework. For more details, refer to the instructions given below.

Option 1 – Try to reinstall the application

There are times when some supporting module for your application under the hood could have messed up the application. And so to fix that, you need to uninstall the concerned application and then try reinstalling it again. Once you’re done, check if it fixed the problem or not.

Option 2 – Try to change the Registry setting

• Tap the Win + R key combination to open the Run dialog box.
• Then type “Regedit” in the fields and tap Enter to open the Registry Editor.
• Next, navigate to this registry key: Computer HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion SideBySide Winners x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_none_02d0010672fd8219 9.0
• From there, look for a String value named “default” and double click on it.
• After that, change its Value data to match the one as the third value in BINARY.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try reinstalling the appropriate Visual C++ Runtime

• You need to open the Event Viewer first by searching for it in the Windows Search box.
• After opening Event Viewer, look for the error events that are sourced by SideBySide.
• Next, look for the actual Visual C++ Runtime module that’s causing the error.
• Now download the module from the official website of Microsoft Support and then install it and see if it fixed the problem.

Option 4 – Re-enable the Microsoft .NET Framework

You could also try to disable the Microsoft .NET Framework then enable the latest version of the .NET Framework on your PC and check if the error is fixed.

If you suddenly encountered a Windows Error Code 0x80070017 during an Update, Installation or System Restore then it’s probably due to some missing or corrupted system files. This kind of error code can occur during an update, installation, or system restore and the only way out of it is to download the file once again and re-run the installation from the top. Before you start to troubleshoot the problem, you need to create a System Restore Point first. After you create a System Restore point, you can follow the troubleshooting options laid out below to fix the Windows Error Code 0x80070017. You just have to follow the troubleshooting option that applies to your situation and whether you got the error during an update, installation, or during System Restore. Whether you got the error 0x80070017 while updating Windows 10 or installing it or during a system restore, the first thing you must do is run the System File Checker. As pointed out early on, the Windows Error Code 0x80070017 might be caused by corrupted or missing system files so the first thing you can try is to run the System File Checker scan.

• 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.

If you have encountered Windows Error Code 0x80070017 during an Update, then here are some options you need to try:

Option 1 – Delete the files/contents in the SoftwareDistribution Folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow 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 stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• 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.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error Code 0x80070017. 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. On the other hand, if you got the error code 0x80070017 during a Windows 10 installation, then it’s because of bad media or corruption in ISO. Here are some troubleshooting steps for this kind of situation:

Option a – Try to create Windows 10 ISO media again

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. Most users reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seem to create issues such as the error 0x80070017. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with the option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option b – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x80070017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically. If you got the error during System Restore then this means that the files that are being copied from the disk are not making it to the hard drive. To resolve it, here’s what you can do:

Option 1 – Run System Restore in Safe Mode

You might want to run System Restore in Safe Mode and see if it works. Just reboot your PC into Safe Mode and then run System Restore.

Option 2 – Reset Repository

• Boot your PC into Safe Mode.
• Then open Command Prompt as admin.
• Next, type the “net stop winmgmt” command and hit Enter to stop the Windows Management Instrumentation Service.
• After that, go to C:/Windows/System32/wbem. From there, rename the repository folder to “repository-old”.
• Restart your computer.
• After your computer has restarted, open Command Prompt as admin again and then type the “net stop winmgmt” command and hit Enter.
• Next, type the “winmgmt /resetRepository” and hit Enter to reset Repository.
• Restart PC and check if System Restore now works.

Option 3 – Try resetting Windows 10

To fix the error 0x80070017, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, it only resets all the system settings and files. Simply go to Settings > Recovery. From there click the Get started button under the Reset This PC section.

Recently, a number of users reported seeing plain white icons on their “.docx” files instead of the Word icon. This kind of issue is mostly caused by a conflict with the default program settings in Windows which is why you may not see any Microsoft Word icon on your .docx files. So if you suddenly find that the Microsoft Word icon is either blank or missing and does not show properly on .doc and .docx document files of Office on your Windows 10 computer, then you can check out the potential solutions outlined below. Before you proceed, you can try to restart your computer as there are instances when a simple system restart can resolve some issues like this one. However, if it does not help, create a System Restore point first. This is to ensure that you can always undo the changes you are about to make in case something goes wrong. Once you have that covered, proceed to the following options.

Option 1 – Try to configure .docx files to open with “winword.exe”

You can try configuring the .docx files to open with the winword.exe in order to fix the problem.

• Right-click on a .docx file and select the “Open with…” option.
• After that, if a prompt appears with a message saying, “How do you want to open this file”, select the “More apps” option to proceed.
• Next, scroll down and check the checkbox that says, “Always use this app to open .docx files” option.
• Then click on the “Look for another app on this PC” link and choose the WINWORD.exe application from one of the following paths based on the installed Office version in your computer and click Open:
  • Word 2016 (64-bit): C:/Program Files/Microsoft Office/root/Office16
  • Word 2016 (32-bit): C:/Program Files (x86)/Microsoft Office/root/Office16

• Now check if you can now see the Word icon on the .doc or .docx files.

Option 2 – Try changing the default Word icon via Registry Editor

• Tap the Win + R keys to open the Run utility.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this path located in the left pane: HKEY_CLASSES_ROOTWord.Document.12DefaultIcon
• From there, double click on the default value at the right pane and based on the Word version you are using as well as the architecture (32 bit or 64 bit) and then copy-paste the corresponding value in the Value data box:
  • For Word 2016 (64-bit) keep it as C:/Program Files/Microsoft Office/root/Office16/wordicon.exe,13
  • For Word 2016 (32-bit) Keep it as C:/Program Files (x86)/Microsoft Office/root/Office16/wordicon.exe,13

• Once you’re done, tap Enter and then close the Registry Editor.
• Restart your computer and see if the problem’s fixed.

Option 3 – Try to rebuild the Icon cache

You may want to rebuild the Icon cache as it could also help fix the issue.

• Tap Win + E to open File Explorer and then click Folder Options and click Views to show Hidden System Files.
• After that, go to C:Users%username%AppDataLocal folder and look for a file named Iconcache.db and delete it.
• Next, go to C:Users%username%AppDataLocalMicrosoftWindowsExplorer.
• From there, look for the following files and delete them.
  • iconcache_32.db
  • iconcache_48.db
  • iconcache_96.db
  • iconcache_256.db
  • iconcache_1024.db
  • iconcache_1280.db
  • iconcache_1600.db
  • iconcache_1920.db
  • iconcache_2560.db
  • iconcache_exif.db
  • iconcache_idx.db
  • iconcache_sr.db
  • iconcache_wide.dd
  • iconcache_wide_alternate.db
• Restart your computer. This will purge and rebuild the icon cache.

Option 4 – Try fixing Office apps

Fixing the Office apps can help you resolve the Word icon issue. All you have to do is open Settings > Apps. From the app list, look for the Microsoft Office Desktop apps and select it and then click on the Advanced options and click Fix. After that, wait until the process is completed and restart your PC. However, if the problem still persists, repeat the steps again but this time, click on Reset instead of Fix.

Option 5 – Try to repair Office Installation

If the options given above didn’t work, you can try to repair the Office installation and see if it can fix the problem.

• Open Control Panel and click on Programs and Features.
• Next, right-click on the Office program that you want to repair which in this case is, Word.
• Select Change and click Repair > Continue. After that, Office will start to repair Microsoft Word.
• Wait until the process is done and then reboot your computer.

A number of users reported lately that their Windows 10 PCs automatically boots into the BIOS whenever they start their computers. And when they tried to exit the BIOS and restart their computers, it still boots into the BIOS. If you are one of the users who experience the same problem, worry not for this post will walk you through what you can do to resolve the problem. Each time a Windows 10 computer boots, it goes through a lot of processes and one of them is where it checks the computer for any hardware issue such as hard drives, peripherals, as well as external devices. So if it finds some issue, the computer will halt the boot process and will boot into the BIOS. To fix this, there are several suggestions you can try. You have to check if you’ve pressed any key, especially the F2 or F12, or Del keys. You also have to check the peripherals and external devices in your computer or update the BIOS or reset it. For more information, make sure to follow each one of the options laid out below.

Option 1 – Try to check for any pressed key

The first thing you can do is to check for any pressed key. This might not make any sense but a pressed key can actually cause this problem. So you have to check if you have the F2 or F12 or Del buttons pressed since these are hardware keys that are usually set by the OEM to boot into the BIOS.

Option 2 – Try checking the physical device connections

You might also want to try checking if there are other devices that are connected to your PC. This is because the configuration of the BIOS or UEFI might be configured in a way that any external device connected to the computer has a higher boot priority compared to the hard disk.  And if it’s really the case, the externally attached disk might be the drive your computer is trying to boot into and not the hard disk. In such cases, Pen Drives, USB storage devices, CDs, DVDs, and so on, are included in this category of physical device connections.

Option 3 – Try to set a proper boot device

If the Boot Manager wasn’t able to locate a proper boot device, then it could be the reason why your computer boots into the BIOS when you turn it on. Thus, you have to check if there is an available proper boot device. You can usually find it under the Boot priority section. However, if you’re unable to locate your hard drive or SSD under the Boot device, then you have to change the hard drive but you have to check first if it is properly plugged in and that it works on other computers. If it works on other PCs, then the problem lies in the motherboard of your computer, and in that case, you have to consult its manufacturer.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the issue but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 5 – Try resetting the BIOS/UEFI configuration

You might also want to reset the BIOS configuration which will lead to arranging the boot configuration since it is intended by the manufacturer. Note that this will get rid of any blockage in the boot process. All you have to do is take out the CMOS battery for a couple of seconds and then put it back again. After that restart, your computer and will be booted directly into Windows. Resetting the BIOS would also get rid of any password set for BIOS and you need to change your CMOS battery in case it didn’t work.

There are instances when the Windows 10 installation needs interaction before it reaches the file process. And so if you suddenly encounter the Windows Update Installation Failure 0x80240020 error under the Windows Update History, then you need to get it fixed. When you encounter this kind of Windows Update Error, you will see an error message that says, “The operation did not complete because there is no logged-on interactive user”. This error also indicates the “WU_E_NO_INTERACTIVE_USER” code. To resolve this issue, in this post we’ll walk you through a couple of steps but before you get started, know that you don’t have to run any troubleshooter or delete any file just to fix this error since all you have to do is enable one option that can automatically login with your account and complete the installation for you. With that said, just make sure to only try running Windows Update once you’re told to do so. There are two ways you can enable the option that could resolve the Windows Update Installation Failure 0x80240020 error. One is via Settings while the second one is via Registry Editor.

Option 1 – via Settings

Step 1: Go to Settings > Accounts > Sign-in Options. Step 2: From there, toggle on the “Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart” option. Step 3: After that, it will make sure that the interaction part is removed from the Windows Update process. Note: If your device is joined in a domain or if some work or email policies are applied to your device by your company or organization, then you wouldn’t be able to see this option in Settings and that’s where the Registry Editor comes in. Just make sure that you’re logged in as an administrator and that you create a System Restore Point first since registry hacks are sensitive and could highly impact how your computer behaves or functions. Once you have that covered, follow the steps below.

Option 2 – via Registry Editor

Step 1: In the Start search, type “Regedit” and hit Enter to open the Registry Editor. Step 2: Navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateOSUpgrade

Note: If the above-given registry key does not exist, you can simply create it. All you have to do is right-click on the WindowsUpdate key and then select the New Key option and type “OSUpgrade” as its name. Afterward, create a new DWORD (32-bit) Value and name it “AllowOSUpgrade” and set its value to 0x00000001. Step 3: Restart your computer and check if the error is now fixed. And then try to update your Windows 10 computer again and while you’re at it, make sure that you’re around your computer to interact with the prompts needed to complete the installation process.