Diablo 2 is trending after launch looking good

New Apple's upscaling technology called MetalFX will place iOS and macOS devices back into the gaming world. Apple had great games back in the old days and some all-time hits like the prince of Persia have been made first for apple but along the way, it just lost it.

Same as NVIDIA's DLSS and Intel's XeSS systems, Apple MetalFX also uses AI algorithms to upscale the resolution of output game frames. So, for example, the GPU inside your MAC might render the game at 1080p, but through MetalFX and AI upscaling it will look like a 4K image but have a good frame rate since it is rendered in base resolution.

The ability to make AI strike a good balance between performance and image quality is a key to technology in today's modern gaming and having this technology will help developers a ton to be able to achieve great results on Apple hardware.

The First MetalFX Games

So far three official games that will use this technology and be released natively for Appl hardware are Resident Evil 8 Village, GRID legends, and No Man's Sky. All three games have been confirmed and Resident Evil 8 Village is already sent for review people are impressed since the game can run smoothly on all Apple devices, even ones with an M1 CPU.

Apple is back into gaming

When you say Apple gaming is probably the last thing that comes to your mind but truth be told Apple makes more money from games than Microsoft, Nintendo and Sony combined. Also, Apple itself was a big player once regarding computer games as well, Myst and Prince of Persia are games that were made and have been released for Apple first. Bungie was also founded by Apple developers and Halo was originally announced as a Mac game.

Apple has been trying and pushing gaming on its platform since it kind of died down. Today all Sony, Nintendo, and Microsoft controllers work without any issues with all Apple products. Apple also has its own gaming subscription service, Apple Arcade, and its Apple TV is packed with GPU that can rival Xbox ones.

MetalFX API ties and brings it all together, it is designed to get the most performance from the hardware by minimizing overhead.

Now, computers and laptops do not hold any large numbers if we look at the user base, and that could deter developers but if we look at iPad and iPhone things are different there, much different. How same CPU power these devices and how MetalFX is available across all products it is clear that there is a market for games there. No Man's Sky is coming to iPad using these technologies and bringing full computer experience to tablets.

If you connected your Hard Disk, USB, or SD card to your Windows 10 computer and you suddenly encounter an error that says, “Windows was unable to repair the drive”, read on as this post will help you fix the problem. This kind of error indicates that the file system on the drive has become corrupted and that ChkDsk was not able to repair the problem. You can also encounter this error when you try to run the ChkDsk utility to repair the system. This kind of error is most likely due to the general corruption of the contents in the drive. It is also possible that you removed the external drive without using the “Safely remove hardware” option or it could be that the drive is still in use. To fix the problem, the obvious thing to do is to safely remove the external drive by using the “Safely remove hardware” option. If it didn’t work, you can try to run the CHKDSK utility from the command line or you could also restart your computer in a Clean Boot State and then run the scan. Before you proceed with the potential fixes provided below, make sure that you create a system restore point first or you could also create a backup copy of the data to an external drive.

Option 1 – Run the CHKDSK utility from the command line

Although some users reported getting the “Windows was unable to repair the drive” when they run a CHKDSK scan, other users reported that running it also fixed the error. Thus, you can try to run it and see if it works or not.

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

Option 2 – Restart your computer in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that triggers the “Windows was unable to repair the drive” error to appear when you connect your external drive or run the CHKDSK utility. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

If you are familiar with the Dynamic Lock feature in Windows 10, then it has probably made it easier for you to lock your computer the instant you move away from it. This interesting feature does not need any special software like IR Cameras to use this feature as long as your Windows 10 computer supports Bluetooth which it most likely does. However there are times when the Dynamic lock feature is either missing or not working. When that happens, here are some suggestions that could help you. But before anything else, you need to create a System Restore point first since you will be modifying some critical system settings as well as registry files. After you’ve created a System Restore point, refer to the following options below to fix the issue with Dynamic Lock.

Option 1 – Try using the Settings app

• Tap the Win + I keys to open the Settings app and then navigate to Accounts > Sing-in options.
• After that, scroll down until you see the Dynamic Lock section.
• Next, make sure that the checkbox for “Allow Windows to automatically lock your device when you are away” is checked.
• Now that you’re all set, exit the Settings app.

Note: If for some reason the above-given solution didn’t work, you can try the next options below.

Option 2 – Try to pair your Bluetooth Device

If you get a message saying, “Allow Windows to automatically lock your device when you are away” in the Notifications Center or in the Settings app, then you need to pair your Bluetooth device. To do so, follow the steps below.

• Go to Settings > Devices > Bluetooth & other devices.
• From there, make sure that Bluetooth is turned On and then pair your Bluetooth device.
• And if you open the Windows Defender Security Center, you will see the following message as well.
• Simply click on the Add Bluetooth device button and it will open the Bluetooth settings where you can also pair the device.

Option 3 – Try to reinstall or update the Bluetooth driver

The issue might have something to do with the Bluetooth drivers. It could be that it is outdated and needs to be updated or that you recently updated it and since then you have trouble removing the Bluetooth device and so to fix the issue, you can update, roll back or uninstall the Bluetooth drivers. How? Follow the steps below.

• Tap the Win + X keys to open the Device Manager.
• Next, look for the Bluetooth device and right-click on it.
• Select the option “Update driver”.
• After that, a new popup window will appear. In there, select the option, “Search automatically for updated driver software”.

Note: Checking the update may take a few minutes so you’ll have to wait until it finishes. If it is able to find an update, you must install it. And if you want to reinstall the Bluetooth driver, just select the “Uninstall driver” option and follow the next on-screen instructions that follow.

Option 4 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run dialog box and then type “Regedit” in the field and hit Enter to open the Registry Editor.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• After that, navigate to the following registry key:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWinlogon

• Next, look for a DWORD named “EnableGoodbye” located on the right-side panel and then make sure that its value is set to 1 which means that it is enabled while 0 indicates disabled.
• Now close the Registry Editor and restart your computer to apply the changes made successfully.

Option 5 – Try checking the Group Policy setting

If your Windows 10 version has the Group Policy Editor, you can use it to fix the Dynamic Lock issue as well. Simply follow the steps below to use it.

• Tap the Win + R keys to open the Run dialog box.
• Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to the following path:

Computer ConfigurationAdministrative TemplatesWindows ComponentsWindows Hello for Business

• After that, look for an entry named “Configure dynamic lock factors” and double click on it to open a new window.
• Once you enable this Group Policy setting, the signal rules will be evaluated to detect the absence of a user and will lock the device automatically. On the other hand, if you disable or don’t configure this setting, you can continue locking your computer with existing locking options. Take note that it may be Not configured or Enabled but shouldn’t be set to Disabled.
• Now select the radio button for Enabled and set the Signal rules then click OK.
• Then exit the Group Policy Editor and restart your computer.

If you encounter the “We couldn’t install some updates because the PC was turned off” while trying to run Windows Update on your Windows 10 computer, then read on as this post will give you a couple of suggestions you can use as a reference to fix this error. Make sure to follow the options given below carefully.

Option 1 – Perform basic computer troubleshooting

If you get the “We couldn’t install some updates because the PC was turned off” error on your laptop, then it’s recommended that you connect your laptop to a power source and then try clicking the Update button again. In addition, you also have to make sure that your computer stays awake until the Windows Update process is completed. This will ensure that your computer does not go into an idle state and interfere with the process.

Option 2 – 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 and then try to run Windows Update once more.

Option 3 – Try restarting the Windows Update Services

• Open the Services Manager.
• From there, make sure that you set the following services and Startup types:
  • Background Intelligent Transfer Service: Manual
  • Cryptographic Service: Automatic
  • Windows Update Service: Manual (Triggered)

Option 4 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. 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 5 – Try to install the Windows Updates manually

As mentioned, the error might be because Windows missed installing a particular update which is why you are not able to proceed with the current update. So to resolve the issue, you need to install the update that wasn’t installed by downloading it from the Microsoft Update Catalog website. You also have to make sure that you didn’t turn off the Windows update or have it delayed.

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error. 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.

A general rule of thumb, which is followed by most users, is to download the specific missing DLL file and place it within the software’s installation directory. However, this can be harmful to your system as hackers often upload popular malicious DLL files to target systems. Thus, you should avoid downloading DLLs from the internet. And follow these steps to fix the DLL error:

• Restart your computer
• System restore to an earlier state
• Run a malware/virus scan
• Update all the hardware drivers
• Running SFC /scannow command in command prompt
• Then do as the error suggests, reinstall the program if it’s feasible. Game files can take several hours to install and therefore, reinstallation can be a cumbersome job. Also, frustrating if the error appears after reinstallation.
• Update device drivers manually, such as graphics drivers, DirectX software if you see DLL missing error while running game

If you suddenly encounter a Blue Screen error that points out to either the mfewfpk.sys and epfwwfp.sys files, then this post might help. Both of these files are created by third-party software. The mfewfpk.sys file is created by the McAfee security software while the epfwwfp.sys is created by the ESET Antivirus. These files are residual files and sometimes it blocks upgrading Windows 10. Aside from blocking Windows 10 upgrade/update, these files can also cause a Blue Screen error after an upgrade which leaves your Windows 10 computer useless. When you get a Blue Screen error caused by any of these files, you will see an accompanying error message that states, “DRIVER IRQL NOT LESS OR EQUAL”. To fix this Blue Screen error, you can check out the suggestions laid out below but before you do that, you need to create a System Restore point first as it can help you undo any unwanted changes. In addition, make sure to also boot your computer into Safe Mode with Networking before you troubleshoot.

Option 1 – Try to remove the epfwwfp.sys file

You can try to remove the epfwwfp.sys file using Command Prompt. To do so, refer to the following steps:

• Right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
• Next, type the following command and hit Enter to delete the epfwwfp.sys file:

DEL /F /S /Q /A “%systemroot%System32driversepfwwfp.sys”

• After the scan is completed, restart your computer and see if it fixed the Blue Screen error.

Note: You can also use the ESET AV Remover tool to uninstall Eset security software to remove the epfwwfp.sys file.

Option 2 – Try to remove the mfewfpk.sys file

The same with the first option, you can remove the mfewfpk.sys file using CMD.

• First, right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
• After, type the following command and hit Enter to delete the epfwwfp.sys file:

DEL /F /S /Q /A “%systemroot%System32driversmfewfpk.sys”

• Once the scan is completed, restart your computer and see if it fixed the Stop error.

Note: You also have the option to remove the mfewfpk.sys file using McAfee Product Removal tool to uninstall the McAfee security software. All you have to do is download the McAfee Product Removal tool and run it and then follow the onscreen instructions to install it. Once it is installed, click on Next. After you select the radio button to agree to the terms of use, click on Next once again. Finally, restart your computer and check if it is able to resolve the problem or not.

Option 3 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors. It can be found on 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.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Blue Screen error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • 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.

Windows Update Error 0x80071a91, what it is? As you know, Windows Updates are very essential to the operating system since they push with them the important security updates that are crucial to the system. And if a Windows Update is delayed, it can the system vulnerable to potential threats. Thus, this kind of issue must be resolved right away. One of the errors that you can encounter while updating your computer is the Windows Update Error 0x80071a91. The error code 0x80071a91 occurs when the “Transaction support within the specified file system resource manager is not started or was shut down due to an error”. This happens when a service called “File System Resource Manager” or FSRM does not function due to some reason. To fix the Windows Update Error 0x80071a91, here are some suggestions that could help.

Option 1 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error 0x80071a91. 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 2 – Disable the antivirus program temporarily

There are times when the antivirus program installed in your computer blocks file access and even disk access. Thus, 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 3 – Try resetting the File System Resource Manager

As pointed out earlier, the error 0x80071a91 pops up when the FSRM service suddenly stops working and so resetting this service via Command Prompt might resolve the problem. To do so, follow the steps below.

• In the Windows Search box, type “command prompt” and hit Enter.
• Then right-click on Command Prompt from the related search results and click the “Run as administrator” option.
• After opening Command Prompt as admin, type the following command and hit Enter:

resource setautoreset true C:

• After that, exit Command Prompt and restart your computer and then check if the problem’s fixed by running Windows Update again.

Option 4 – Flush the contents of the SoftwareDistribution folder

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the 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. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

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

Option 5 – Delete the Common Log File System transaction logs

You might also want to delete the Common Log File System or CLFS transaction logs to fix the Windows Update Error 0x80071a91.

• Open an elevated Command Prompt.
• Then type each of the commands listed below and press Enter after you type each one of them.
  • cd /d %SystemRoot%System32SMIStoreMachine
  • attrib -s -h *
  • del *.blf
  • del *.regtrans-ms
• After you’ve executed the commands given above, restart your computer and try to update Windows 10 again.

Error 0X800F080C is tied to corrupted system files and .NET framework issues. In this article, we will focus on how to fix it starting first with .NET fixes and then moving to system-related ones. Follow the guide step by step so you can fix this error fast and easily.

.NET issues

As previously stated 0X800F080C error can occur due to issues with .NET framework, 3.5 framework to be more precise and there are two ways we can fix this error. Follow the guide below as presented:

1. Install .NET 3.5 framework from Windows features

   First thing is to try and install the framework from Window features itself. Sometimes installation and activation of .NET 3.5 in other ways can result in this error. To install it do the following: Press ⊞ WINDOWS + R to open the run dialog Inside run type in appwiz.cpl and press ENTER to open up the Programs and Features menu Inside the Programs and Features menu click on Turn Windows features on or off. Check the box associated with .NET Framework 3.5 (this package includes .NET 2.0 and 3.0) Press OK Click on YES and wait for the package to be installed then reboot your PC

2. Run the .NET Repair Tool

   If the previous step was not successful or you already had .NET 3.5 installed then run the troubleshooter in order to fix issues. Go to the official Microsoft .NET framework repair tool website here and download it. Once downloaded install the tool and follow onscreen instructions.

Corrupted system files

If the previous solution has 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 files 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

Blue Yeti has gained popularity among streamers and users that want a high-quality mic for their setup. Without going into details of the hardware itself I will say it is a pretty good mic. Now the issues that have been reported with it are that Windows 11 can have issues with it resulting in the microphone not being recognized by the operating system. If you are one of the unfortunate Blue Yeti users and have this issue, do not despair because we have a solution for you, several to be more precise so you can easily fix the issue and get back to talking.

Check cables

Sometimes it is not a software problem at all. First thing is to check if by any chance cable of the mic is disconnected, damaged, or similar. If the cable seems fine next step is to plug in the mic into another port in order to eliminate faulty jack on the computer. If nothing happened the last thing to try is to connect the mic to another computer so we can be sure that the mic itself is in working order so we can focus on software. If by any chance mic is not working on another computer that some hardware inspection of it will be required.

Set Blue Yeti as a default device

There is a chance that Windows 11 has not set Blue Yeti as a default audio device for recording and therefore you can not use it. In order to eliminate and fix this issue, right-click on the speaker icon on the taskbar in the far-right part of it and choose sound settings. Go down to the input section and pick Blue Yeti beside Choose device for speaking or recording.

Update driver

More often than not device not working is tied to malfunctioning or a bad driver. In order to eliminate and resolve this issue right click on the Start icon and choose device manager. Inside device manager expand the Sound, video and game controllers section. Right-click on each device in the section and choose update driver. Wait for the update to complete and restart your system.

Run the troubleshooter

Press ⊞ WINDOWS + I to open Windows settings. Go to System in the left pane and click on it. In the right panel choose and click on troubleshoot. Inside troubleshoot click on Other. Scroll down and locate the Recording Audio troubleshooter and then click on Run next to it. Wait for the troubleshooter to finish and follow on-screen instructions to resolve the issue.

Check Blue Yeti microphone privacy setting

Not very often, but sometimes privacy settings can be the issue even when everything else is working perfectly. In order to check privacy settings press ⊞ WINDOWS + I to open Windows settings and go to Privacy & Security on the left panel and click on it. On the right panel click on the microphone. Make sure that toggle next to Let apps access your microphone is ON.

Some Windows users are encountering the 0x800705b3 error code after failing to install a pending update on Windows 10. Most commonly this particular issue is reported to occur with Integrated webcam drivers updates and Bluetooth adapter driver updates. Follow the guide below in order to fix the issue and update your Windows successfully

Running the Windows Update Troubleshooter

The majority of users that were dealing with this issue reported that the issue was fixed after they ran the Windows Update Troubleshooter and applied the recommended fix.

1. Open a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘ms-settings:troubleshoot’ and press ENTER to open up the Troubleshooting menu. Opening the Troubleshooting tab on Windows 10
2. Once you’re inside the Troubleshooting tab, move over to the right-hand section of the screen and click on Windows Update (under Get up and Running). Next, from the context menu that just appeared, click on Run the Troubleshooter.
3. Once you’re inside the Windows Update troubleshooter, wait until the initial scan is complete and see if a viable repair strategy is found.
4. If the scan has identified a strategy with the potential to fix your ongoing issue, click on Apply this fix and wait until the procedure is complete. Applying the fix Note: Depending on the type of fix that was recommended, you might need to follow an additional set of instructions before the fix will be properly imposed.
5. After you’ve done this, reboot your computer and wait for the next startup to complete.
6. Open Windows Update once again and see if the installation of this pending update is now successful.

Installing the pending Update Manually

Whether you’re experiencing this issue with an integrated webcam driver or with anything else, chances are you’ll be able to circumvent the apparition of the 0x800705b3 error by using the Microsoft Update Catalog to find, download and install the pending update manually.

1. Open your default browser and navigate to the root web page of the Microsoft Update Catalog.
2. Once you’re inside the Microsoft Update Catalog, use the search function (top-right corner of the screen) to search for the update that is failing.
3. After the search is completed and you get the list of results, look for an updated driver version that is compatible with your Windows version and CPU architecture.
4. Once you manage to identify the correct Windows Update, click on the hyperlink associated with the update that you want to install, then click the Download button and wait for the process to complete.
5. After the download is complete, use File Explorer to navigate to the location where you previously downloaded the update.
6. When you get to the correct location, right-click on the .inf file and choose Install from the context menu that just appeared. Note: If you have multiple failing updates with the same 0x800705b3, repeat the instructions above with every Windows Update that you’re having trouble installing.
7. At the end of this operation, reboot your computer and see if the problem is fixed at the next computer startup.

Enabling the Windows Installer Service

The Windows installer service is responsible for installing pending updates that get downloaded by the Windows Update component. If this service is disabled on your configuration, none of the updates waiting to get installed will get completed.

1. Press ⊞ WINDOWS + R to open up a Run dialog box. Inside the text box, type ‘services.msc’ and press ENTER to open up the Services utility.
2. Once you’re inside the Services screen, move over to the right-hand tab of the screen, scroll down through the list of services and locate the Windows Installer service. When you find it, right-click on it and choose Properties from the context menu that just appeared.
3. Once you are inside the Properties screen of the Windows Installer services, access the General tab, click on the Start button to force-start the service. Note: If you can, also change the Startup type to Automatic via the associated drop-down menu. However, depending on your administrator settings, this might not be possible.
4. Restart your computer and wait for the next startup to complete. Once your PC boots back up, attempt to reinstall the driver that was previously triggering the 0x800705b3 error and see if the issue is now fixed.

Performing a Winsock Reset

In case the 0x800705b3 error is related to some kind of network inconsistency (TCP or IP related), you might see Windows Updates failing due to bad data that forces the Windows to abort the installation of new pending updates. In this case, you should proceed by doing a complete Winsock reset procedure to fix the majority of the socket and temporary data-related issues that might cause this behavior. Several affected users have confirmed that this method was the only thing that allowed them to finally fix the Windows Update issue and install pending updates normally. Here are some step-by-step instructions that will walk you through the process of performing Winsock Reset:

1. Open up a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘cmd’, then press CTRL + SHIFT + ENTER to open up an elevated Command Prompt. Accessing an elevated CMD prompt Note: When prompted by the UAC (User Account Control) prompt, click Yes to grant admin access.
2. Inside the elevated CMD prompt, type and taste the following commands in order and press ENTER after each one to effectively reset the TCP and IP data that might be responsible for the apparition of the 0x800705b3 error code:

   nbtstat -R
   nbtstat -RR
   netsh int reset all
   netsh int ip reset
   netsh winsock reset

3. Once every command above is processed successfully, you can go ahead and close the elevated Command Prompt and reboot your computer.
4. After the next startup is complete, repeat the installation of the Windows Update that was previously failing and see if the issue is now fixed.

Performing SFC and DISM Scans

If none of the ‘superficial’ causes have worked in your case, you should start considering some type of system corruption that might affect your computer’s ability to complete pending updates that are currently waiting to be installed. In case you find yourself in this particular scenario, you should run a couple of built-in utilities capable of fixing corrupted instances that might be currently affecting the Windows Update component. Our recommendation is to start with a simple System File Checker scan. An SFC scan will cross-check every Windows File against a local archive that maintains healthy copies. In case corrupted instances are found, this utility will swap the corrupted instance with the healthy equivalent.

Performing an SFC scan

Once the SFC scan is complete, reboot your computer and wait for the next startup to complete. After your computer boots back up, initiate a DISM scan. This utility works differently in the sense that it relies on a sub-component of Windows Update to download healthy copies for the corrupted Windows files that need to be replaced. Because of this, it’s important to make sure that you have a reliable Internet connection before initiating this operation.

Doing a DISM scan

After the DISM scan is complete, reboot your computer one final time and see if the issue is fixed once the next startup is complete.